This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
Hey @Keith_Winand,
We apologize for closing your thread! We wanted to check in and see how things were performing over the last few days?
Have you recently reinstalled RoonOS via the webUI? Iâd give that a try next if youâre still having issues.
Weâll be on standby for your reply!
Welp, I would say the system is performing much better now that the background analysis is complete. While the system was still doing the analysis on the 84,000+ track I did experience periodic resets of the server every couple of hours. As I said, now that the analysis is done the system is performing well. Everything seems to me loading snappily and playback has been good.
My concern and something for the dev team to look into is why this is happening. I canât believe I am the only one having this issue. Also, if I ever have to reload my library I will have to go through this again and will basically keep the app out of commission for a few day. I donât think that is acceptable for $500 device.
Right now the background analysis is set to throttled but not sure what the optimal setting is for the One. Please let me know.
Thanks for the follow-up.
Keith
You need to leave at least one core process free for Roons other activities. Not sure how many cores are available on the One as itâs not a powerhouse safe bet is one or two or just leave it throttled as new albums will just get done when idle.
You should not need to analyse the whole library again. Once done itâs done. If youâre restoring a database from a previous backup or machine itâs best to turn it off and on old machine do a backup, then on new machine turn it off, start restore and wait until itâs fully restored then it wonât start the analysis process again, as it will restore the previous analysis that was backed up with the database. But Roon being Roon if you donât do it this way, it always triggers a reanalysis as soon as storage is seen and backup is adding files.
Thank you for the suggestions. I did change it to one core (out of four) as you are correct it really wonât need to do heavy work again.
To you second point, this issues started when I tried to restore a backup from my mac mini to the Nucleus One and there must been some issue with the backup because it triggered the Roon server to constantly restart. That lead to all the steps I went through as described above.
Good news it that after all that everything seems to be performing normally, for now.
Thanks,
Keith
1 Like
When you do a restore it does a full metadata update after adding the files back and if you didnât have the background analysis speed to off it will also analyse them again. The metadata update takes all of one cores resources and this can cause the interface to be inaccessible, I and others have had this often recently during its regular metadata updates, this should not happen and we have a ticket in being investigated, part of what happened feels related to this as it exhibits similar symptoms, combine this with analysis which if you had set prior to a higher core count likely caused it to run out of juice.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
Hi @benjamin and hello Roon technical team - Kevin has reopened this thread after I emailed him on 6/8 about the ongoing issues I am having with the Nucleus One. I tried, I really did but the unitâs server software continues to restart every day or so. When starting Roon on my mac or ipad it is always searching for the server and I am waiting several minutes to connect to it. ARC never works and I have to continually tell it to reconnect to the Nucleus One and wait while it refreshes all the information - several minutes.
It seems returning it is out since it has been 7 months since purchase but we need to do some more digging and either get it RMAâd or I will just stop using it and buy a NUC or reinstall the Roon server on my Mac Mini.
Please advise on how to proceed.
Thank you - Keith
Hi @Keith_Winand,
We very much appreciate your patience and communication thus far! Weâre seeing errors and reboots occurring due to a lack of available RAM on your Nucleus, for example:
user.err kernel: [2059663.194328] Out of memory: Killed process 24211 (RoonAppliance) However, your library size is within the scope of what the Nucleus One should be able to handle, so our team is continuing to investigate potential reasons for this.
While itâs certainly less than ideal, running a smaller portion of your library will likely allow for smoother performance. If you cut your library in half, how do things perform?
Hi @benjamin and thank you getting back to me. How do you suggest I cut my library in half? My library is on my Synology NAS in a folder labeled Music. Do I need to move some of my library outside this folder?
Also, if my library is within acceptable limits for the unit and the unit is not performing properly I would suggest that the unit has a problem and that replacement should be discussed. I have had this issue since I first purchased the unit as this thread shows. Shouldnât this be a possible solution?
Thank you.