Errors like the one you’ve seen now are signs of low level corruption in the database. This means that the records Roon is reading from your database are different from what was originally written. This can happen for a number of reasons, like failing hard drives or an unstable power source (frequent outages, hard power cuts, etc).
We’re sorry you’re experiencing this extremely rare error: not only is our database infrastructure designed specifically to prevent this type of corruption, but starting with Build 880, Roon detects database corruption “on the fly”. So if corruption is detected during a backup or during normal use of Roon, you’ll be immediately prompted to restore from a backup.
What’s Next?
Install Roon fresh on your Roon Server machine and roll back to one of your older backups. You can use these instructions to do so:
Rename the “RoonServer” folder to “RoonServer_old”
Restart the RoonServer in the WebUI to generate a new Database
On the Roon Remotes, press “Use another Roon Server” and connect to the new database
(Optional) - Restore your database from a Backup prior to the issue starting
If the database loads properly, your edits, playlists, tags, etc should be intact, and we can confirm everything is performing properly once it’s been restored.
If you do not have any backups, unfortunately the only other solution is to start with a fresh database.
One thing worth doing now that things are stable: please check that scheduled backups are enabled and pointing somewhere other than the Nucleus itself, such as a network share or a USB drive. That is under Settings, then Backups. Corruption like this is rare, but having a current backup is what turned this into an afternoon rather than a rebuild from scratch.
If you have had power cuts, or the Nucleus has been switched off at the wall at any point, that is worth addressing as well. Abrupt power loss is one of the more common causes of what you ran into, and a small UPS is inexpensive insurance for a device that keeps a database open around the clock.
We will close the thread here. If anything looks wrong as you get back into your library, please reply and it will reopen.