Any idea why, overnight while Roon is essentially idle, I got the “There was an issue loading your library” error?
It’s happened twice now (once more than a month ago). Reloading the Roon app on my main client (Mac Studio) solved it that time.
This time restarting didn’t help, and I’m restoring from backup.
Just wondering what could be causing it and if there is anything I could to do avoid it from happening in the future… Otherwise Roon is very stable for me.
Assuming no overnight power failures, then a failing solid-state drive is the most likely cause.
I’d recommend replacing it before it goes pop completely.
Roon accesses the tracks over CIFS to my Mac Studio with an NVME storage array run by Softraid. So signs of any issues there. Network looks to be stable as well as is the Mac, so not sure any of that could be causing the issue.
For example if I reboot the Mac, the Roon server recovers fine with no library issues…
Hi @Peter_Galvin1,
Thank you for your patience while we worked through the queue. SSD issues can cause you problems with your library. When this error occurs again let us know the date, time, and track playing (if applicable) and we will activate diagnostics on your account to identify the source of your issue.
Every few days, while I’m not using Roon, I guess this error that tells me to restore from backup. So far, each time, just rebooting the system solves the problem.
I replaced the NVME M.2 card in the NUC with a new, well reviewed one (WD Black), but the problem persists. I find it hard to believe the problem is the internal NUC storage as replacing it didn’t solve the problem.
Any other thoughts on what could be going on?
Thanks.
–Peter
Well, it sounds like DB corruption, but a reboot solves the problem and Roon seems to function fine, so I would think not.
Perhaps there is a DRAM issue causing the DB to be corrupt when in memory and a reboot cleans it up.
Looks like the DRAM is not ECC protected in the NUC 12 (https://www.amazon.com/gp/product/B0BJDRK51K?ie=UTF8&th=1)
And this doesn’t seem to be a common Roon problem - so maybe it is the DRAM.
I’ll try to replace it and see if that solves unless folks have other ideas.
Backup your current Roon database. Delete the current Roon database. Bring up Roon. It will create a new database. If the problem is solved then the old database was corrupted and memory is probably OK. If the problem isn’t solved then the old database was probably OK and the problem lies elsewhere, in memory perhaps.
My money is on a database that has latent corruption, i.e. corruption that manifests eventually, but not always.
Hi xxx,
Hmm, I have put a lot of time into my Roon db (identifying albums, merging them etc). Would hate to start from scratch and have to do that all again.
I guess I could start new, have it scan, and see if the problem reoccurs. If not then it was in the DB and I would have to do all that work again. If so then it’s likely memory as you say…
First, backup your current database. That way, if the problem isn’t there then you can just Restore it. If the problem is there, then that database is no good and your edits, etc. are lost anyway (unless you have a good Backup).
Have you ever done a Roon Backup?
Supposedly, latent corruption should be caught (but not fixed) when you try to Backup Roon’s database.
Ok, since you have Backups then I suggested a way to be more sure about what the problem is before you (potentially) waste time and money installing new memory.
Have you seen this thread? It talks, not about failing memory, but about too little memory. Since you have over 200,000 tracks it may also apply to your case.