· None of the above quite fits
· None of these quite match
· Issue loading library, also can't create a new database
· LAN with Netgear switches and a Synology NAS
Hey @Music4Metrostations,
Thanks for the report!
From a fresh Roon Server diagnostic report, your database is almost certainly not corrupt. Roon Server is reporting it that way, but every one of those errors in your logs is actually the same underlying problem, the NAS is running out of available file handles:
IO error: …/broker_4.db: Too many open files
There are no genuine corruption signatures anywhere in the logs. Roon Server reports any low-level database read failure as corruption, which is why you’re seeing that message.
The reason you can’t create a new database is separate, and it explains the dead end you’ve hit. When the database was flagged, Roon Server halted its background threads mid-way through a scheduled backup, and that backup job was left marked as still running. Every restore attempt since has been refused with “another backup or restore is already in progress”, so the corrupt-database screen won’t let you move in either direction. That flag only clears when the process restarts, which hasn’t happened since September 10th.
Here’s what we’d suggest, in this order:
/data/Roonbackups/RoonBackups on your DS213+. Your logs show your scheduled backup location (/RoonBackups) listing zero restorable backups, while /data/Roonbackups/RoonBackups has a valid one. Worth correcting the scheduled backup path afterwards so future backups land somewhere restorable.One thing to be aware of: the file-handle ceiling will come back. Your logs show it being hit within a few minutes of every startup, on every restart going back to late August, so this isn’t a one-off. Could you tell us which Synology model Roon Server is installed on and how much RAM it has? With a library this size it may be running past what that unit can support, and we’d like to confirm before you rebuild.
Hi Benjamin,
After some time and some extra help I managed to do steps 1 and 2.
Then when trying to backup (I bought a new NUC and want to install Roon server there based on a backup) it gives the corruption error again.
Specs of my NAS are:
Could you please explain how I can make a backup and not have Roon giving the corruption error? I assume copying files to the new machine won’t do the trick.
Best regards, Hans
Stopping the package and rebooting the NAS should have cleared the stuck backup job that was preventing restores. Those steps resolved the stuck state, but not the file-handle limit, which is why the error came back. This isn’t actually corruption, fortunately, just a lingering space issue on the NAS.
Instead of making a new backup, install Roon Server on your NUC and restore from the valid backup the logs already found at /data/Roonbackups/RoonBackups, keeping the RoonServer package on the NAS stopped. Running Roon Server on the NUC takes the NAS out of that role, which should stop the file-handle errors entirely.
We’ll watch for your reply.
Hi Connor, Thanks for your information. The point is that I was unable to create a valid backup. For that reason, I bought a new NUC 15 PRO with lots of RAM to install ROON Server on it, instead of ROON On NAS. Is there another workaround for creating a backup before for this move..
