· I am experiencing persistent Roon database corruption and would like to know whether Roon Support can examine my database and determine whether it can be repaired or recovered before I abandon it and create a new library.
My original Roon Server is ROCK running on an Intel NUC6i3SYH. The music library is stored on a separate internal 2 TB SSD.
Roon began reporting: “There was an issue loading your library”
I am currently migrating to a newer Intel NUC10FNHH with a new NVMe system/database SSD. I installed ROCK cleanly on the new NUC and attempted to restore my existing Roon backups.
I have tried the following:
• Roon backup on DropBox dated 20 March 2026 — restore completes successfully, but Roon then reports “There was an issue loading your library.” • Roon backup on DropBox dated 13 March 2026 — same result.
I therefore returned to the original NUC6. ROCK itself boots normally and the Web Administration Interface reports the Operating System, Roon Server Software, Roon Database & Settings, and internal music storage as OK.
With Roon Server stopped, I accessed \ROCK\Data and found three RoonServer database directories:
• the current RoonServer • RoonServer_old, dated approximately 16 May 2026 • RoonServer_old_old, dated approximately 29 July 2024
Before doing anything further, I copied all three complete directories to another computer. I then tested the two older databases individually by stopping Roon Server, renaming the candidate directory to RoonServer, and restarting Roon Server.
Unfortunately, both RoonServer_old and RoonServer_old_old also ultimately produce the same “There was an issue loading your library.”
I have therefore stopped further experimentation and have retained untouched copies of all three database directories, as well as the original Dropbox Roon backups.
My music files themselves are safe and I have additional copies of them. My concern is recovering the Roon database information, particularly DSP presets, tags and manual metadata edits.
Before I create a completely new Roon database, could you please advise whether you can examine one or more of these preserved RoonServer databases and determine whether any of the library data can be recovered?
I am happy to upload the complete RoonServer database and/or Logs folders if required. Please let me know which version you would like me to upload and provide the appropriate upload instructions/link.
Tell us about your home network
· My router is a Vodafone Gigacube and my Roon server is directly connected to it via a short ethernet cable. No VPN.
mjw
(You want nice, supportive? Call a damn helpline.)
2
Roon checks the database for issues before creating a backup, so you should be reasonably confident that the backup is sound, especially since the restore completed successfully.
So, I would look at other culprits, e.g. SSD, and temporarily run Roon Server on another machine using the backup to see if the issue persists.
I did actually install Rock on a new NUC, and tried to restore the databases from my backups before inserting a new SSD into the new NUC and copying my music to it. I had the same error messages.
Thanks,
Christian
mjw
(You want nice, supportive? Call a damn helpline.)
4
How did you restore the database from Dropbox? Did you restore directly from the cloud, or restore all files to a local machine first?
I downloaded the folders to the hard drive of a Windows desktop, copied them to a USB stick, verified that the number of files and folders was the same as on DropBox, and restored from the USB stick (I had 2 backups) both on my old NUC and on my new NUC with the fresh Rock install. Both gave the same error. Thanks.
Thanks for laying out the restore path you tried on both NUCs, and for confirming that both backups produced the same error.
Can you please access your Roon Logs on the device that had the corruption error and upload a set to our Secure Uploader? That will let us take a closer look at what is happening during the restore.
If the backup folder is of a reasonable size, you can also upload a compressed version to our uploader and we can look over it on our end. Let us know!
Better news than it looked. This is not database corruption.
The restore completes. What fails is the library load: Roon starts loading your 39,656 tracks, runs for about a minute, then hits a single unreadable image reference on one artist record and abandons the whole load. That is the “There was an issue loading your library” message. All three database folders and both backups carry that same record, which is why they all behave identically.
It is a known fault and it was fixed in Roon 2.70, released in July. The logs you sent are from the old NUC, which is still on 2.66 build 1658, from before the fix.
On the new NUC please:
Check Settings > About and update to the current release.
Then restore the Dropbox backup dated 20 March.
That backup specifically: there was real database damage on the old NUC, but it starts at 01:21 on 21 March, and your 20 March backup completed at 03:27 that morning, before it.
If it still will not open, please send logs from the new NUC rather than the old one.
Until then, please do not create a new library, and keep the three database folders and both backups as they are.
Thanks. I followed your instructions on the new NUC. I confirmed before restoring that Roon Server was running Version 2.71 (build 1683) production.
I restored the 20 March 2026 backup. The restore completed successfully and I relaunched Roon and logged in. However, after allowing the library time to load, I again received “There was an issue loading your library.”
As requested, I have now uploaded the complete Logs folder from the new NUC, collected immediately after this failed load.
I have not attempted any further restores or created a new library, and the original database folders and backups remain preserved.
Thank you for working through the restore on the new NUC. We looked at the diagnostics, and the result is not the one we hoped for.
The image reference problem we described earlier is fixed in 2.70 and does not appear in the new logs. What they show instead is that after each restore (the 20 March backup twice and the 13 March backup once), the restored database reports damaged records as soon as Roon reads it, and the library stops loading. The system log shows no disk or storage errors on the new NUC.
To put it simply, database corruption means the records Roon reads back are different from what was originally written. It can happen for a number of reasons, such as a failing drive or an unstable power source, and it is hard to tell which one applies here. Sometimes corrupt records go unnoticed for a long time and only show up when Roon has to read every record in the database. That is likely the case here: the damage was already in the database before those backups were made, so the backups carry it too.
This is hard news when so much careful work is in that database: your DSP presets, tags, and manual edits. We wish the answer were different.
If you have any backup older than the two you tried, please try the oldest one you have. If there is none, the remaining option is a new library. Your music files are safe, and your TIDAL library returns when you log in with your account. A new library starts from a clean database, and Roon now checks for corruption during backups and normal use, so if damage ever appears you are prompted to restore from a backup right away.
I appreciate your help. Unfortunately, I can’t think of a location where I would have older backups. So it looks like I will have to create a new library, with the hours of manual edits that this entails. It is sometimes frustrating to see that an album is recognized in Tidal, but Roon doesn’t seem to find it so matter how hard I try. It would also be nice to have a way to recover independently DSP presets from a backup.
Thanks for letting us know, and we’re sorry it came to this. Before you start a new library, there’s one last thing you could try, if you’re comfortable with a bit of technical work. Another community member recovered a damaged Roon database using a LevelDB repair tool; Roon’s database is built on LevelDB. His steps are here: community post by tudupka.
Please treat this as an unofficial, at-your-own-risk attempt that we can’t support or guarantee. The repair can drop damaged records rather than fix them, so the library may load with some edits missing, or not at all. If you try it:
Work only on a copy of one of your preserved database folders, and keep the originals and backups untouched.
Make sure Roon Server is fully stopped while the repair runs.
If it doesn’t help, a new library is the way forward, and your music files and TIDAL library are not affected. And thank you for the feedback about restoring DSP presets separately from a backup, we’ll pass it on to the team.
It has been a few months now. I had not experienced a recurrence of corruption since.
My approach had worked for me.
Vadim, thank you for keeping an open mind, even if it wasn’t " an unofficial, at-your-own-risk approach.