· roon device: nuc running rock with 1 tb sdd. regular backup on external drive. streamer: PS audio airlens
Since the start of the year I get the message when starting the roon app. “unable to load library” and then it ends. I have followed the adviced procedure multiple times. Each time shifting further back in time in the backups. But every time with the same result.
I can get roon working again by not restoring. But as soon as I load a backup I immediately get the error message again.
Tell us about your home network
· router kpn experia box 10v linksys velop mesh network directly from router to living room. switch connected to velop in living room. nuc connected to switch as well as streamer.
running qobuz connect directly from streamer works without issues
To put it simply, database corruption means that the records Roon is reading from your database are different from what was originally written.
This isn’t common and can happen for a number of reasons, like failing harddrives or an unstable power source (frequent outages, hard power cuts, etc).
In some cases, corrupt database records can go completely undetected. And it’s only when we release an update that requires Roon to re-scan every record that the corruption shows itself.
These updates don’t happen frequently, which increases the risk of data loss. For example, if you only have a few weeks of backups, the chances that you have a usable backup drop significantly if the “latent” corruption isn’t detected for many months.
If you restore from a backup and still see “There was an issue loading your database”, try restoring from your oldest backup.
If you’re not having any luck with your oldest backup, then the only alternative is to start with a fresh database.
We know that many of us have a carefully curated database: our settings, album covers, metadata, tags, playlists and favorites are exactly as we want them to be. Having to start fresh sounds like a nightmare and we do hope it won’t come to it. But, if it does, please know this is so it will never happen again.
Vadim thanks so much! I had been retrying the procedure and moving further back the (backup)timeline. A backup from 3 weeks ago looks to have stuck. Consistent with your proposed approach. Luckeily not all the way back to the oldest backup.
