· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices
Describe the issue
I have a brand new Nucleus 1. I attempted to load a database saved from my former Roon server (a PC) and after several minutes it responded that it couldn't connect to the database. Now when I reboot the Nucleus, it simply keeps taking me back to the same "unable to load database" message.
Errors like the one you’ve seen now are signs of low level corruption in the database. This means that the records Roon is reading from your database are different from what was originally written. This can happen for a number of reasons, like failing hard drives or an unstable power source (frequent outages, hard power cuts, etc).
We’re sorry you’re experiencing this extremely rare error: not only is our database infrastructure designed specifically to prevent this type of corruption, but starting with Build 880, Roon detects database corruption “on the fly”. So if corruption is detected during a backup or during normal use of Roon, you’ll be immediately prompted to restore from a backup.
What’s Next?
Install Roon fresh on your Roon Server machine and roll back to one of your older backups. You can use these instructions to do so:
Rename the “RoonServer” folder to “RoonServer_old”
Restart the RoonServer in the WebUI to generate a new Database
On the Roon Remotes, press “Use another Roon Server” and connect to the new database
(Optional) - Restore your database from a Backup prior to the issue starting
If the database loads properly, your edits, playlists, tags, etc should be intact, and we can confirm everything is performing properly once it’s been restored.
If you do not have any backups, unfortunately the only other solution is to start with a fresh database.
You mention that the database is corrupted, but when I removed my brand new nucleus from the system and re-installed my PC as the server, the database opened perfectly. From this, and since you were certain that the DB is corrupted, it seems that the Nucleus might not be compatible with PC files?
You say that I should reinstall Roon Server, but you seem to have not noticed that I purchased a Roon Nucleus, the basis of this ticket – I don’t know how you would expect me to reload the software.
As previously mentioned, each time I attempted to reboot the Nucleus, it always began with attempting to load the DB, and, consequently, ending up in an error. This made it impossible to move to any of the further steps you suggested.
Not addressed was my mention that the Nucleus was unable to see several of my Squeezebox endpoints (I was able to load the Nucleus interface prior to loading the DB).
For the above reasons, I wish to return the Nucleus. It’s apparent that the “plug and play” notions ascribed in the marketing don’t really apply when attempted to replace an existing PC-based system. Over the several years that I’ve used Roon (lifetime member), I’ve gone through several iterations of updates that have caused some extremely frustrating networking issues, and now that all is running smoothly, please don’t blame me for wanting to opt out of any more issues, especially when the PC based system is running perfectly.
I’ve already sent in a request to return the product and I appreciate your help, but I’m going back to my existing setup that works perfectly.
Thanks for the honest reply! I completely understand not wanting to spend any additional time troubleshooting gear, let alone new gear!
That said, I did notice from your recent account information that the Nucleus you recently bought and set up was running an extremely outdated version of RoonOS, version 1359/production.
The current version of Roon is 1667. If I were to check my gut feeling on this whole situation, it would point to this. If you still have your Nucleus, performing an update is really easy, and could potentially rid you of all your issues.
I’m sorry I didn’t get to your thread and send off a response sooner. Either way, I hope you’re able to enjoy smooth listening, we’ll be here to help in case you run into any other issues along the way!
Thanks for your reply. Unfortunately, I did return the unit today. Wondering, though, why a brand new Nucleus would be operating with an out-of-date OS. Also noticed that I never received the (included) quick-start guide. Is it possible that this was a returned unit?
Well, it’s all academic at this point, but I do appreciate your response and I plan to continue using Roon (I have a lifetime license).
BTW, if you’re ever chatting with any of the dev folks, it would be really nice if the search engine would response similar to Google’s search engine in the way that if retains the dropdown’s list after reopening.
Sorry to hear that there was no Quick-start guide included with your Nucleus. That would have pointed to the online Nucleus manual with its all-important step 2:
2. Update Nucleus firmware
Before using Roon with Nucleus for the first time, it’s important to make sure your firmware is up to date.
Note: Not updating Nucleus firmware could lead to data loss or a failed migration.
It’s almost certain that the Roon software would have later releases available following the date of the factory assembly and initial software installation.
Sorry to hear you returned the unit. @Geoff_Coupe is correct, the firmware needs to be updated before the first use. Since you returned the Nucleus unit, we won’t be able to continue troubleshooting, but if you need assistance with anything else Roon-related, please let us know.
