· 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
Roon on Mac, and Roon on QNAP server restrore from my backup OK. When my Nucleus One restores from the same backup, it continually re-boots and spins on startup and cannot settle and connect so I cannot use my Nucleus One for my system on Nucleus One with my backup - I can only use my backup on my Mac, or my NAS.... help! Same backup restore, same location, three different Roon servers, only the Nucleus One won't boot from it.
Thanks for reaching out. According to our diagnostics system, your Nucleus One was online recently. We’ve already tried to activate diagnostics on it so we can review the error logging, and at this point we just need it back online again. Please bring it back online and let us know here once it is up, then we can check for a log package.
Hi there, thanks - it’s constantly online, just been rebooting all the time - still doing it now this am - it’s like it’s in a loop. Should I reset it back to factory settings? I’m just wondering if I do that, you won’t be able to see the potential issue; that’s all. Thanks for reaching out!
Thanks for writing in and for sharing these additional details. We were able to review a fresh diagnostic report from your Nucleus and see the reason it’s stuck in a reboot loop: the nucleus is continually running out of available RAM.
This is interesting, as your library appears to only be around ~50k tracks, this is correct?
If so, then to answer you question - yes, I think resetting your database would be a good next step here. Your current database could be caught in some sort of corrupt state.
Before this though, it would be crucial to have a few available saved Roon backups, otherwise you’d essentially be wiping the slate clean and starting Roon like you did on day 1.
Do you have any backups available that predate the issues you’ve been having?
If so, then proceed with the reset, and see how things perform. You can restore a backup afterward and continue to monitor.
We’ll be awaiting your reply and results, thank you!
Just checking in on this. Were you able to confirm whether your library is still around 50k tracks, and did you find any Roon backups from before the reboot loop started? If you have those older backups, the next step we discussed was resetting the database and then restoring one to see whether the Nucleus stays stable. Let us know what you found, thanks.
Anooyingly I thought I sent this a week ago and it was still in drafts
Done that, I’m afraid - still the same. This identical backup loads and restores perfectly on my 14-year-old NAS and a little MacBook Air, but not on this? Are you telling me, for all that money, it’s a really limited device? If it is, I’ll just send it back as not really fit for purpose if RAM is an issue! It’s supposed to be the cream of the crop - no?
I have a lot of TIDAL tracks (which shouldn’t take up space) and yes, some physical which were on my NAS, but the database won’t even restore without the physical drives connected - please confirm it’s not fit for purpoase as I will return it and go back to the NAS from 14 years ago!
Sorry, but your assumption is incorrect. Tracks from a streaming service (i.e. Tidal, Qobuz and KKBOX) that are added to your library do count towards the size of your library because their information, metadata and hyperlinks are added to Roon’s database.
So, with this in mind, what is the real size of your library (i.e. how many tracks does it contain in total)?
Thanks for the update, and sorry the reset didn’t resolve it.
Geoff is correct - streaming tracks (Tidal, Qobuz, KKBOX) that are added to your library do count toward database size, as all their metadata is stored locally. So the total track count matters here, not just local files.
The Nucleus One is well-suited for most libraries, but to confirm whether RAM is genuinely a limiting factor in your case, we’d need to know the full library size. Streaming and local.
That number will tell us whether this is a library size issue or something else going on with the restore process.
It’s the weekend - Tech Support don’t work 24/7. They will respond next week.
PS - I notice from your screenshot that you are very close to the 100,000 track limit for a Nucleus One. I suspect that with the 4GB RAM in a Nucleus One that you are running out of memory, which causes Roon to crash and the Nucleus One to reboot. It’s possible to upgrade the RAM, but be aware that Tech Support need to give approval for this. See:
Funny - a company selling boxes for thousands works office hours… I’m in the wrong industry
Thanks for the info - I’ll await permission, as that could solve it - wasn’t aware of the 100k track limit, as I assumed streaming didn’t count - my bad.
Thanks for your patience here, and for digging up the RAM module too.
You’re on the right track. With your library sitting close to the 100,000 track limit, the 4GB of RAM in the Nucleus One is the bottleneck causing the reboot loop, so a RAM upgrade should resolve it. The good news is your backup itself is fine, as you’ve seen it restore cleanly on your other Roon Servers.
You can access this information within the Product Specs on the Nucleus One page here:
One thing before you order: RAM upgrades on the Nucleus One do require approval from our team first, and that approval is still being finalized on our end, but we should be good to go soon. I’d hold off on purchasing the module until we can confirm the upgrade is approved and verify the correct spec for your unit, so you don’t end up with hardware you can’t use or that voids anything.
Sit tight and we’ll follow up here shortly with the green light and confirmation on the right RAM. Appreciate you bearing with us.
