Error loading vault: File System Timeout

Help
1

I looked at similar topics and tried things suggested in them, but nothing fixed my issue.

What I’m trying to do

I am trying to open a vault on my computer. I have never had issues opening the vault before. Obsidian suddenly just failed to load the vault.

Screenshot 2025-01-04 165318
Screenshot 2025-01-04 1653182048×1600 51.3 KB

This is what the window looked like originally.

After moving the vault folder, this is what the window looked like:

Screenshot 2025-01-04 171057
Screenshot 2025-01-04 1710572048×1600 51.2 KB

Finally, after deleting the .obsidian folder:

Screenshot 2025-01-04 171812
Screenshot 2025-01-04 1718122048×1600 54.7 KB

Things I have tried

  • Moving the vault to different locations on my PC and then choosing the vault folder to open it.
  • Deleting the .obsidian folder (because the restricted mode option disappeared after moving the vault)

Unfortunately, since I can’t even get into the vault, I can’t get the debug info for it.

I did go into the console and grab the log from it though.

This is what the log says:

app.js:1 Obsidian Developer Console
app.js:1 failed to read JSON .obsidian/core-plugins.json SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at t. (app.js:1:729140)
at app.js:1:237228
at Object.next (app.js:1:237333)
at a (app.js:1:236051)
(anonymous) @ app.js:1
app.js:1 Error: File system operation timed out.
at e.kill (app.js:1:545987)
at l (app.js:1:518105)
at c (app.js:1:518221)
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
s @ app.js:1
setTimeout
c @ app.js:1

2

UPDATE:
I also tried creating a new vault in the same directory (C:\Users\username\Documents\Obsidian) as my old vault and then copied the .obsidian folder from my old vault to the new one and the new vault loaded fine, so it isn’t any of my plugins or settings that is causing the issue.

3

I have exactly the same issue. I got it on MacOS and also on Windows.
The common factor was the the vault was located on a exFat external drive and the vault was about 80GB total size.

I’ve seen this same issue arise since 2021, but the users where using cloud servers and the cause was pointed in that direction in error.

4

Chat GPT advice

The error “File system operation timed out” generally occurs when an operation on the file system takes too long to complete. Here are some common reasons why this might happen:

1. Slow or Unresponsive Storage Device

  • If you’re working with a network drive (e.g., SMB, NFS), it might be experiencing latency or disconnection.
  • The disk may be under heavy load or failing (check with SMART tools for HDDs/SSDs).
  • External USB drives might have a poor connection or power issues.

2. File Locking Issues

  • Another process might be locking the file or directory, preventing access.
  • Antivirus software or backup tools could be scanning or processing the file.

3. Insufficient System Resources

  • Low memory (RAM) or CPU spikes could slow down file operations.
  • Too many I/O operations happening simultaneously.

4. Network Issues (for Remote Drives)

  • If the file system is mounted over a network (e.g., NFS, SMB), packet loss, congestion, or a disconnected network could be causing timeouts.
  • VPNs or firewalls might be interfering.

5. Corrupt File System

  • A damaged file system might be causing delays in reading/writing.
  • Run a file system check (chkdsk on Windows, fsck on Linux/macOS).

6. Software or OS Issues

  • Bugs in the application or OS might cause excessive delays.
  • Outdated drivers or kernel issues (especially for networked file systems like NFS or CIFS).