I have this problem, too. It spent ages updating the database (~six hours), and then I got the message. Restart hasn’t helped, will try suggested remedies tomorrow. Database is ~35GB.
Mac OS 10.14.6, DB is on hardware RAID 0 2xSSD; all drives check out fine. Mac Pro Trashcan, dual 700/32GB RAM. 12 TB of music or so. Music files are on 7200 RPM drives in an ARECA RAID enclosure attached via Thunderbolt 2. All drives online and reporting no problems.
So we can take a closer look, are you able to access your database and zip up the Logs folder for us?
If you can zip up that folder and send us a Dropbox link, we can get a sense of what’s gone wrong here. If you can’t access the database, or if you don’t have anywhere to upload the Zip file, just let us know. We’ll walk you through the next steps here so we can figure out what’s gone wrong.
Thanks in advance for your patience, and sorry again for the trouble here.
Tha path [RoonFolder/Database/Core/USERID/broker_2.db] shows up as a folder with 5792 items, such as “251063.db”. Most of them are 2MB. The total of the folder is 9.3GB.
Much appreciated, @Andrew_Webb. If you’re able, please keep this link available during the time we investigate. Right now the technical team is downloading this, but we will likely need to have our development team download it later as well.
I’ll be sure to reach out as soon as their investigation has concluded and I have received their feedback.
First, you have our apologies for the delay here. I checked with the team on this and requested an update. We are currently doing some internal investigations in our QA labs, but I don’t have any further updates at this time.
While we continue to investigate this issue you can use a new database with Roon. You can do this by doing the following:
The only way to recover the database would be to restore a backup. You can give this a try, but if the problem in the database that is causing this issue exists in the backup as well then you will be back in the same state.
However, the team is currently investigating this and is making progress in understanding the issue you are experiencing, so my suggestion is to hang tight with the fresh database temporarily until we hear back from the team.
I tried the backups. They don’t load, either. Current is full of errors (mostly breaking albums into single tracks, which is quite annoying, and Roon now fails when using Qobuz most of the time, so Radio doesn’t work at all. I’ve just gone to using the Qobuz app, and abandoning Roon for the moment.
We’ve recently released Roon 1.7 (Build 511) which includes changes that should improve this behavior. Please give it this a try and let us know how it goes!