There is a read/write error in a file in one of my databases. When obsidian starts, an error will be reported directly, and the workspace cannot be accessed. I can’t delete the wrong image file in the operating system, how can I get obsidian to ignore this error…
Why can’t you delete the file? And can you move it instead?
hi, because the network folder is mapped through Microsoft cloud, the unstable synchronization of this cloud service leads to the error of i/o reading and writing of one file. When trying to delete the local file, the system cannot execute, and re-synchronization to other folders, the same situation is true, because the entire workspace cannot be opened with obsidian. So I can’t pinpoint a specific file.
i’m sorry to add that because the Microsoft cloud service I use has encryption plug-ins, which automatically encrypt files into different encrypted directories, I cannot find out the specific file through the file i/o that obsidian reports an error in workspace. I wonder if there is any way that obsidian can ignore this error and enter workspace when opened??
I’m having a little trouble understanding your setup, but it sounds like one that might not be a good fit for Obsidian. Obsidian expects to be able to read the files in a vault so it can index them, and it expects them to always be there.
Let’s start here:
Is the error message from Obsidian? What does it say?