Skip to main content

Why does Rust say the save folder is read-only?

A Linux disk can have plenty of free space and still refuse every write. If the first save error says “Read-only file system”, find out how the volume containing the active world is mounted before changing any file permissions.

Check the filesystem under the save

Read the path in the error and locate its existing parent folder. In a terminal, run findmnt --target . --output TARGET,SOURCE,OPTIONS from that folder. For a game running inside a container, inspect the mount as the game sees it. A different mount may be visible to the host.

Look for ro as a complete option. For example, the system drive might be writable while the separate volume under the world folder is read-only. Changing the save folder’s owner cannot make that volume writable.

Use the exact error to choose the next check

Keep a copy of the error and its time. Avoid starting another world over the affected files while diagnosing the storage.

Use the exact error to choose the next check
First errorWhat to inspect
Read-only file systemCheck the mount options and kernel or hosting-provider storage messages around the failure.
No space left on deviceCheck capacity on that specific volume with df -h . and inode availability with df -i ..
Permission deniedCheck access for the account that runs the game, including its access to the parent folders.

Check that the existing world can save again

If a previously writable volume changed to read-only unexpectedly, ask whoever manages the disk to check its health before returning it to service. Once they confirm it is writable, watch a normal save of the existing world. Check its file timestamp advances and the original error is absent for that save.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details