I have been having consistant challenges with Roon going offline and requiring me to reboot my Nucleus. I think the database has been corrupted. I followed the instructions for rebuilding the database and it seemed to work for a week or two but then I saw the same issues again and I have now rebuilt the database 3 times and it is not working at all now.
I only have one backup file that was created last week after the most recent crash. Even that was complicated because it failed during the middle of creating it but it looks like it did create a complete backup on the 2nd attempt.
It seems that part of my issue is when we have had power outages (I did not have it connected to a UPS the Nucleus would shut down and eventually it caused a problem with the database.
A good friend that is in IT also uses Roon and has it loaded onto a NAS and he is going to help me migrate our system to the NAS next week. It will have the music files on the hard drive of the NAS and the database on a Solid State drive following other suggestions from this forum.
My question is does it make sense to use the existing backup if I keep experiencing issues as the database is trying to rebuild itself with the existing library or should I try to clean up the music files and start fresh. If I start fresh will the songs I have added to the library from Tidal appear in my library still or will those songs be missing?
Hi @Dave_Murphy,
Thanks for reaching out to us about this issue. @Jim_F’s answer is correct. I noticed you said you had experienced some corruption on your current Roon server. Would you like some help troubleshooting that as well? If so can you tell us what symptoms you noticed that pointed to corruption?
The primary issue that I have been having is that when we go to open up Roon using Roon Remote we get a message saying that the Roon is unable to find the Core. Our Nucleus is at our primary home but we spend a lot of time at a vacation home. We also have a vacation home that we spend a lot of time at. Based on looking through the forums I am thinking that what has been happening is that when there have been interruptions in power the Nucleus shuts down abruptly (I did not have it on a UPS) and that at some point those shutdowns have corrupted something.
Following the instructions for “Troubleshooting - Issues loading database” I renamed the “RoonServer” folder and it seemed like everything came back and reloaded correctly. But then a week later the same issue happened, and then I repeated the procedure and after another short period of time it could not connect again, I repeated it again with the same results. I currently have 4 older RoonServer Folders. It is working again now but I feel it is a matter of time before it crashes again.
In addition to that some of the actual music files seem to be incomplete. I think this is a seperate problem but it may be related. There are dozens of songs in my library that do not play the complete song. For example it might be a 6 minute song and the timer shows that it should be a 6 minute song but after 2:30 it stops and goes right to the next song. I did not have backups of the Roon database set up prior to this issue so I only have backups since the problem showed up so I do not think restoring from a backup will be helpful.
I have back ups of my music files from before this issue appeared so my thought was that I would try to clean up the music files and create a new folder of the files that I own and make that the folder that Roon uses as my library and start over. Would you advise that approach and should I also reinstall any system software on the Nucleus in case it is system files that are the problem instead of the music files causing the issues?
I’ve activated diagnostics for your Nucleus and have looked over the logs, but I don’t see any instances of database corruption or any signs of SSD issues.
Can you create .zip archives of the /RoonServer_old/Logs folders and upload them all to our logs uploader (linked below)? Once uploaded please let us know so that we can check if it was corruption or another cause.
If you only have one backup you’ve restored, it seems that your backup is also corrupt, unfortunately. Your best next step here would be to start fresh, and re-import your library.
I do wish we had more to offer here, I understand how tedious starting on a fresh database is. Let me know if you have any additional questions!
We can identify track files that RoonServer has identified as corrupt, but the mutations caused by corruption have accumulated to the extent that Roon can’t read back the database. It’s unlikely that surgically removing a corrupt library item will reliably isolate latent corruption in the long-term.
However, going back to the Nucleus logs from several days prior to your last post, we can see Roon’s audio analysis detecting corruption associated with these two tracks: John Legend/Evolver/[026960].m4a
And this one: Silvertide - Show and Tell - 06 - Mary Jane.m4a
Both appear to have been in Artist-level subdirectory folders housed in Internal Storage. You can inspect those files directly for evidence of damage.
However, this isn’t conclusive evidence that corrupt local track files are the source of corruption. It’s worth checking the integrity of the entire system - power outages, damaged cables, and failing hard drives can all play a part.
Thanks I removed them both from my library while I am reassembling my library in another folder to reinstall. Hopefully that will take care of everything.
Hi @daniel, I just had the system crash again this morning. I am still updating my music library so I have not replaced the old one yet. I have just done a few individual replacements to confirm that the files are the complete songs. I had to recreate the RoonServer file again. Should I upload the log from the crash today at the same link?
It has now crashed 3 times today and deleting the old Roon Server file is no longer working. It is now giving me a message that there was an issue loading my library. It told me to try to restore from a backup, so I used my last back up which was from a couple of weeks ago. I had turned them off thinking that my new library would be active sooner than I have been able to get it done. It is working again after restoring from the back up. Should I resubmit all of the logs from the crashes today?
It has now crashed again between 2:30 and 3:00 Central time today. It is behaving differently than the other times so I rebooted it but I have not deleted the server files yet. After rebooting it seems to be working again but can you look at the current log file to see if there is something you can see in that or do you need me to Zip the current file like the old ones?
HI @Dave_Murphy,
Sorry about the delayed response. You can send over the logs files again or turn on your Nucleus for a few minutes (that will allow our servers to collect the logs). Have there been any more crashes since you left your last comment?
The Nucleus should be turned on and visible now. It was offline becuase I was reloading the new library into it today and so far it seems like the files are all complete.
I will upload two of the log files from when it crashed before I updated the library so you can see if there are issues beyond the music files causing problems. I did go through the process again after I deleted the old library so the current log files should be from the library with the newly loaded music files.
I do have one other question. I loaded the files onto the Nucleus from a USB Hard Drive that I plugged directly into the Nucleus. I used my MacBook to copy the files onto the Internal Storage Folder. The Hard Drive showed up in my Finder as a folder so it is not giving me an option to eject it. How can I remove the hard drive from the Nucleus without just unplugging it?
I looked in some of the forums and somewhere someone said that I could eject it using the browser interface with the Nucleus but I did not see the drive folder anywhere or any options to eject anything. Screenshots are attached.
The setting is not in the Web Administration Interface, but in Roon’s > Storage screen. Choose “Disable” from the “3 dots” menu by the Internal Storage entry.
This is not an “Eject the drive” operation per se - that is not a function contained in Roon OS, so it may still show up in the Mac’s Finder.
Edit: just tested it on my ROCK system - disabling the Watched Folder does not “eject the drive”. It can still be seen and browsed in Windows File Explorer (and presumably in a Mac’s Finder).
Which leads me to ask: why are you trying to “Eject the drive using Mac’s Finder” in the first place?
I ended up just turning off the Nucleus and unplugging the drive while it was turned off. I wanted to “eject” it because I was concerned about corrupting any files on the drive by removing it while the Nucleus was trying to access it. I have had enough challenges with corrupted files that I am trying to be really safe with them now.
@daniel I got everything uploaded to the new library yesterday and tried to do a backup last night and the backup got hung up. It got stuck on the screen saying it was taking a snapshot and it might take up to an hour…it was on that screen for 7 hours and then I just closed the remote app and tried to restart it and it would not connect. I was able to see the Nucleus on the web interface to restart everything and reboot things but the Roon Remote was still not able to find the Nucleus. Powercycling the nucleus itself did not help either. I finally just unplugged it for 5 minutes and then plugged it back in and that seemed to get everything reset.
I manually ran a back up this morning and it looks like that worked as well so I think I am in good shape there but can you look at the logs from this morning/overnight and see what the problem was that caused everything to lock up.
the Nucleus would shut down and eventually it caused a problem with the database.
> Storage screen. Choose “Disable” from the “3 dots” menu by the Internal Storage entry.