I occasionally receive a message that my roon library on my brand new Nucleus One is unavailable, and the message indicates I should reload a backup. Power cycling the Nucleus One resolves the issue, but I'm concerned there may be a bigger issue that needs resolution. Perhaps a log file might provide more information - hence the inquiry.
Hi @Alan_Goldenberg,
Thanks for reaching out to us to ask about this issue. I’ve checked out your logs and I’m seeing traces indicating issues with RAM and internet connection. Can you connect your Nucleus to a computer monitor via HDMI and share a picture of what you see on the screen? That will help us see if there’s a hardware error.
I did. image is below. no error messages - it only contained the IP address of the Nucleus One and when I connect to it via a browser it appears “normal”:
I did notice the status page lists the Roon Labs Software is running version 1.0, while the other apps indicate they are running version 2.0 or higher? Is this expected?:
Based on a recent diagnostic report from your Nucleus, it appears that you’re experiencing database corruption due to being out of memory on the machine.
To confirm, is your total library size around 60k tracks? This should be within the limit of your Nucleus.
What happens if you temporarily slice your library in half, to 30k tracks, do you experience the same issues?
Hmmm… I understand what you’re saying. Seems like that’d be an extremely tedious process just to test this though.
If you have a suggestion on an easy / elegant way to identify “half” of my library, remove it (temporarily), test this, and then recover the “half” again, I can give it a go.
How would you suggest I accomplish that?
If it is a memory issue, doubling the available memory in the Nucleus One would likely resolve the problem, no? Sounds like a pretty simple fix.
Since most of your library is local tracks there is a simple way to do this. Let’s refer to your current watched folder as Folder A. Make a new folder (Folder B) and copy over half of your local tracks to that Folder B. Then disable Folder A as a watched folder, clean up your library from Roon settings → Library → Clean up Library, and make Folder B a new watched folder. Then when you are done testing you can remove Folder B from watched folders, run Library cleanup, and add Folder A back as the watched folder.
Hopefully that will be efficient enough to not be painful.
OK - will do that after work and report back. To my question, would more memory resolve the issue? If so, that seems like an easy win - also is the 60k track threshold a hard stop?
I presently have ~ 57k tracks in my library. Curious what options exist to address now and in the “near” future?
Right, but if 100k tracks is the limit, and I’m at 60% of that limit (~ 57k), and I’m encountering RAM issues…
Would that indicate some of the memory in the Nucleus is the issue or that it requires more?
I should point out some (many) of my tracks are substantially longer that the “average” 3-5 minute track, so maybe I’m closer to 80% of capacity if the physical size of the library (regardless of individual number of tracks) is also a variable in the calculus.
