Signs of possible corruption
- Startup stops while loading the world or a specific dimension.
- The console repeatedly names a chunk, region,
level.dat, or database file. - Entering one area crashes the server or disconnects every nearby player.
- A world loads as new, loses a dimension, or reports unreadable data after an interrupted write.
Recover safely
1
Stop automatic restarts
Leave the server offline so it does not keep writing to the damaged world or overwrite useful logs.
2
Preserve the current state
Download the world and relevant logs. Keep this diagnostic copy even when you plan to restore a backup.
3
Confirm the active world
Check the selected world name and folder structure. A wrong
level-name or an extra wrapper folder can look like missing or damaged world data.4
Restore a known-good backup
Choose the newest backup created before the first corruption symptom. Follow Create and restore backups.
5
Start and test carefully
Watch the full startup, then test the affected dimension or area before allowing normal play.
