· I have been using the Early Access version for a long time. Since around a few months ago (around November last year), I started encountering the message “There was an issue loading your library” every few days. Even so, restoring from a backup allowed me to continue using Roon for a few days at a time, so I kept operating it that way.
However, after the latest version introduced changes to the database structure, the issue now reappears within about five minutes even after restoring from a backup. It has become impossible to continue using Roon in this state.
I gave up and deleted /var/roon/RoonServer to start fresh. When running a clean instance without referencing any local music files—using only TIDAL/Qobuz—no issues occur. This makes me believe that some kind of inconsistency or corruption exists in the backed‑up database.
Is there any way to repair it? Rebuilding a library that I have maintained for nearly ten years would be extremely difficult.
We are so sorry to hear about the trouble you’re having loading the Roon database. Typically, problems loading the database mean that it may have been corrupted at some point. We have more information about what can cause corruption and steps that you can take to recover your database here:
If you’re having any issues after following the recovery steps above, please let me know!
As an aside, right now our team is working on some changes that will help our customers detect corruption when it’s happening. If you don’t mind, I’m hoping you could take two minutes to send us your corrupt database. That way our team can analyze the type of corruption and prevent similar cases in the future.
Even after following the steps you provided, the loading error continues to occur repeatedly. Is there any way you can use the backup data I sent to recover something from the corrupted database? Or should I assume that this damaged database can no longer be salvaged?
After deleting the data folder and reinstalling the application as instructed, the system ran for about half a day. However, when I restored the backup again in the evening, it failed with the same error by the next morning.
When I do not restore a backup and do not load any local music files—using only Qobuz/TIDAL—the system runs for several days without any issues.
If I give up on restoring the backup, I understand that the system will likely work again.
However, this database is something I have maintained for nearly ten years, so I would really like to know if there is any way to repair it.