
What should you check after replacing your Rust server disk?
Keep the restored server closed to players until you know which drive will receive its next save. A replacement with a different Windows drive letter or a missing Linux mount can leave a startup entry looking in the wrong place.
Match the launch path to the replacement disk
Keep existing copies intact. With Rust stopped, note its install path, identity folder and the backup destination from the startup and backup settings. On Windows compare the drive letter or folder mount with Disk Management. On Linux use findmnt --target with the directory path to see which mounted filesystem contains it. If a directory expected to be on the new disk resolves to the main system disk, arrange the intended mount before copying into it or starting Rust.
Restore from a separate readable copy to the confirmed location, using files and a Rust build suited to each other. If you installed the game fresh, compare its actual startup path with the path you restored. Verify that the account running Rust can read and write there.
Prove one write and one fresh copy
Start with private admission and pause unrelated automation while you check the restore. Join the intended world and find a known piece of progress. Observe a game save and check that the save file in the replacement location was updated and that the console recorded success. Also verify that any backup destination was mounted and reachable before running a new backup.
If a backup path points back to the replaced disk, select the separate storage you intended and open the first new copy there. Release access once the world and its new save and backup are in the right places.