Failed to save world / Failed to save chunk
When Minecraft can't write the world to disk it logs 'Failed to save world' or 'Failed to save chunk' and the world data starts diverging from what's on disk. Left unfixed, this leads to rollbacks (players lose progress on next restart) or corruption (chunks load half-written). The root cause is almost always disk, permissions, or filesystem health.
Fastest path: paste your crash report into the Crash Doctor — it identifies this pattern and 40+ others automatically. No signup.
How to fix it
- 1
Check disk space first
df -h on the host (or the Files tab usage indicator on a hosted server). If the disk is over 95% full, the save failed because there was nowhere to write. See our disk-full guide for cleanup steps.
- 2
Check file ownership in world/
If the disk has space but saves still fail, the world directory may have permissions wrong. ls -la world/ should show the Minecraft user as owner. If it shows root or another user, that's the fix — chown back to the Minecraft user. See our permission-denied guide.
- 3
Restore the latest clean backup if data is already inconsistent
If the server has been failing saves for a while, the on-disk world may have half-written chunks. The safest recovery is restoring the most recent backup from BEFORE the saves started failing — not just restarting, which will keep loading the corrupted world.
- 4
Verify the host's filesystem isn't degraded
Rare but happens: the underlying host had IO errors and the filesystem went read-only. dmesg shows the kernel-level cause. On hosted services this is the host's problem; open a ticket with the trace.
Alternative causes
These can produce the same error message — worth ruling out if the steps above don't resolve it.
Concurrent save from a misbehaving mod
Some mods (typically backup mods or world-edit-style tools) try to write to world/ while Minecraft is also saving. The race produces failed-save errors. Disable suspect mods one at a time to isolate.
Network filesystem latency (NFS, SMB)
If world/ is on a slow network share, the save can time out mid-write. The fix is moving world data to a local SSD. Network-attached storage is almost never appropriate for live MC world data — too latency-sensitive.
Frequently asked
Will players lose progress?
Maybe — anything since the last successful save is at risk. The previous successful save (still on disk) is intact. If you restore from backup, you lose everything between the backup and now.
Why does the same error happen right after a restart?
If the root cause (disk full, wrong permissions) isn't fixed, the next save fails immediately on the next chunk unload. Fix the cause before restarting.
Can backups themselves cause save failures?
Yes — some backup mods lock world/ during their copy. A scheduled MC save during the backup window collides. Stagger the backup schedule or use a backup mode that snapshots without locking.
Want this auto-fixed on your server?
CoalHosting's Minecraft hosting runs the same pattern database against every crash and applies the known fix before your players notice. Free crash diagnosis works on any server, hosted or not.
Related crashes
No space left on device (Minecraft IOException)
Fix the Minecraft server 'No space left on device' crash — the container ran out of disk. Find what's eating s…
Permission denied / AccessDeniedException
Fix Minecraft server 'Permission denied' crashes — the Java process can't write a file. Usually wrong file own…
Registry / world corruption (unregistered block or entity)
Fix Minecraft 'Encountered an unregistered' and 'ResourceLocation X not registered' crashes — the world refere…
Last reviewed 2026-06-05. If a step is wrong or out of date, tell us — we'll fix the article and the auto-pattern at the same time.