· I fixed my connectivity based on your response on 10 Feb. I got my Roon app working fine on my iPhone. After a few hours, I tried to access Roon from my iPad. The app crashed on my iPad and the previously working app on my phone also crashed. I was prompted an error message. I see this message from the picture. My library is precious and I did not press OK to format the storage
Thanks for writing in and for sharing your report!
Based on a fresh diagnostic report from your Nucleus, it looks like you’re suffering from database corruption:
Error: [broker/database] corruption detected: Corruption: bad block type
Your best next steps here would be to restore from a saved backup that pre-dates any issues you’ve been having. Once you do this, we can take another look at Roon Server logs to see if there are any corruption traces for you.
Let me know if you’re able to give the above a try, thank you!
There are several reasons a Roon database might grow corrupt over time. Common causes include failing storage hardware, unexpected power loss, or third-party sync and backup tools modifying the database files.
In essence, when Roon attempts to read the database, the data no longer matches what was originally written to disk. As corruption grows extreme, these differences are significant enough that Roon can’t load the database correctly.
This wouldn’t cause a crash of the GUI on a Roon Remote, but it would cause it to disconnect from your server. It could also cause freezes or hangs, which might lead you to force-close the app.
In some situations, the server corruption can be latent. This means part of the database is already damaged, but it can still load and appear to function normally. That’s what @benjamin identified in logs above.
The recommended next step is to restore from a significantly older backup that was made before the corruption began, if one is available. If not, the remaining option is to start with a fresh database.
Please let us know if we can answer any questions.
We’re going to allow this thread to close out due to inactivity, but you can reactivate the conversation by simply submitting a new tech support request here. Our team will merge topic threads accordingly. Thank you!
