No alternative other than restoring last backup, which succeeded, but needed updating since it was from last release.
Then core connection problems and constant cycle of refreshing āHomeā screen on remotes making usage impossible.
Closing/restarting remote and core applications didnāt fix behavior.
Reboot of core computer finally brought back functionality after some fiddling with not finding core etc.
So, Iām up and running again, but would like to understand what happened.
Iād appreciate some response, if you find any time at all, and thanks for reading through thisā¦
Thanks for your post and for your patience here while your case reached our queue. Are you still seeing this issue in the latest Roon release or has there been any improvement?
Yes, can you please upload the Roon Server and any relevant logs to the below link and let us know once uploaded? Thanks!
Logs uploaded.
Iām running standard Roon in parallel to Roon Server, so all respective logs are included.
It happened only that one time so far, but Iām no hard core search user anyway.
Restoring a backup remedied it that one time.
Hope, itāll be of use to further improve stability for everyone.
Iāve got the respective databases saved as well, if needed, but theyāre in the GB sizewise.
Apologies for the delayed response here, I missed your follow-up message. Are you still having issues with your Roon install or has the system been stable?
Have you by any chance run a disk check on your Coreās hard drive yet? Failing hard drives can sometimes cause corruption, I would check this aspect if you are still having issues:
Itās interesting that the hard drive passed the test, I would have suspected it wouldnāt. Is your residence prone to power surge issues? If the Roon Core is not powered off cleanly, this can also lead to corruption. Has the system been stable since you last restored?
Just rerun a disk test now to verify again, and it checks out 100% healthy.
No, never happened during the last three years, and the core is cleanly shut down every time, weāre done for the day or leaving the house.
There had been a 76 hour power outage in our quarter in May '21 due to a infrastructure fire attack at the new Munich Philharmonic construction site, but the core hadnāt been on as it happened.
Yep, itās been a one-off, luckily.
Iām keeping regular back-ups and fingers crossed.
Are you still seeing crashes at this time? Can you please let us know the exact local time + date of the next crash if so? Having this timestamp is very helpful when looking over your remote Roon logs for clues as to the cause of the crash.
Thanks for getting back to me!
Itās been the second time for me 21 days ago, and fortunately running smoothly since.
Iāll make sure to post the exact local time stamp, should there be another crash.
just happened again at about 18:55 11th of August while browsing Qobuzās new releases of the day, first adding āBlank & Jones The Best Of Relaxā, listening to it, then deciding against it, starting a live radio channel, then deleting the just added album - bang, issue loading library, asking for restoreā¦
But this time around, I decided to just reboot my ROON server PC, and you know what, all fine without database restore!
Thanks for the timestamp! Weāre not able to connect to your Core to review a fresh diagnostic, could you please use the directions found here and send over a set of logs to our File Uploader?
Hey @benjamin , thanks for getting back so swiftly!
Just turned my Roon Core Server back on for you to connect and review a fresh diagnostic, since Iām usually shutting it down over night.
Cheers, Marin
It appears that your current Roon database is corrupt, which could explain the crashing behavior you experience. To navigate around this, do you have a backup saved that predates this behavior?
You can also test out running a completely fresh database by following the steps below:
@noris found the same corruption back in May, analyzing logs from March.
And yes, I did revert to a backup predating the behavior back then.
But it happened again.
So that might likely indicate corrupted database backups all along.
It happens about once per quarter, seemingly triggered by some random pattern.
This time, even a mere server restart got me back to a working condition.
Also, I was able to take a database backup without any warnings or problems.
Before jumping through all those loops, let me ask just one question:
How can a corrupted data base slip through all those back-ups and restarts, while there were changes to the code to allegedly prevent that from happening?
