Thanks for letting me know the Nucleus has been rebooted, I can confirm that the diagnostics report has been received.
Sometimes, errors like the one you saw can be spurious, but unfortunately in this case there are signs of low level corruption in your database.
This type of error is extremely rare for us and not one that we see often. Our database infrastructure is designed specifically to prevent this type of corruption, and we don’t take this class of issue lightly.
We’ve traced a few reports like this in the past to hard drive integrity issues but generally speaking, this means that Roon is reading information from your hard drive that is different from what was originally written, and the database is now unable to load properly.
If you’ve been making regular backups, my advice would be to install Roon fresh on your Core machine, and roll back to one of your backups. You can use these instructions to do so:
- Stop RoonServer from running in Nucleus’s WebUI
- Navigate to your Roon’s Database Location
- Find the folder that says “RoonServer”
- Rename the “RoonServer” folder to “RoonServer_old”
- Restart the RoonServer in the WebUI to generate a new Database
- Restore from backup at least a week before issues started
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 you will need to start with a fresh database.
Again, this class of issue is extremely rare for us and you have our apologies for the trouble here.