My Roon database seems to be corrupt. I run weekly snapshots and all of them for the last 6 months fail when trying to restore. I've set up a new Roon server as well and restoring any backup to the new machine also fails.
The machines are all Ubuntu Server LTS x64.
This setup has been working great for years but at some point >6 months the backups became unreliable.
Describe your network setup
Server is a Ubuntu LTS x64 VM with 8 cores, 16 GB ram. All devices are connected via wired internet. Music storage is on a Synology NAS
The team has pulled diagnostic logging from the affected server instance and found some evidence of corrupt local media files within the Roon library. However, this database isn’t showing obvious signs of latent corruption - we want to explore alternatives exhaustively.
The mounted drive hosting the Backups fails to remain accessible to RoonServer for the duration of the Backup restoration. There are other logged failures with the mounted storage locations associated with this library.
If you attempt to restore a Backup from more than six months ago, does it successfully restore?
It seems worth a try to remove the corrupted media. Especially if it was added to your library after the backup that worked. Let us know the results of trying this. Thank you in advance for your cooperation!
Hi @daniel -
I removed the corrupted media, cleaned the library, and verified there were no more skipped/corrupt files listed. After a reboot, I took a backup and immediately tried to restore it and it failed again.
The corrupt files had been in my library for years before and never previously caused a problem with backup/restore.
I am reviewing your logs and I noticed a System.IO.IOException: No space left on device error. Can you please confirm how much space you have left on your Ubuntu device?
Thanks, @noris -
You solved it. I watched the machine run out of space during the restore process. I build a new one with more storage and the restore worked perfectly. Thank you!