Filesystem errors
Read-only filesystems, I/O errors, and instances that won't boot — how to check and repair.
On this page 3 sections
Signs#
- "Read-only file system" when writing — Linux switched the disk to read-only after finding a problem.
- "Input/output error" on files.
- The instance won't start: "the guest kernel panicked while booting".
- Check for disk errors on the Maintenance card finds something.
What to do#
- Save anything you can — copy important files out to
/mnt/macor with MSL Files. - Shut the instance down.
- Check Disk on the Maintenance card (needs e2fsprogs on your Mac).
- If it finds problems, Repair Disk…. A backup is taken first.
- Start the instance and see how it is. If things are worse, Restore… puts the old disk back.
- When all's well, Discard the backup.
No e2fsprogs? Try the maintenance boot.
Keeping it from happening#
- Shut Linux down properly —
sudo poweroffinside it, ormsl --shutdown— rather than the app's Shut Down, which stops it at once. See the note on Shut Down. - Don't restore snapshots after the disk has changed.
- Consider checking at every start.