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.
Hi @Keith_Winand,
You have a few options around slimming down your library - one of which could be to create a new folder within your NAS, and move half your library into this folder, and exclude it from your watched folders within Roon.
Before making any changes, Iād create a fresh backup just to be safe.
It isnāt that thereās a failure or hardware-related issue within the Nucleus, but more so a lack of available RAM on the machine, which is something you can pretty easily upgrade/replace manually, if youre interested. You also have the option to ship the Nucleus in and have our team increase the RAM amount as well, if youād rather not dive into the process of upgrading it yourself.
Let me know your thoughts @Keith_Winand and weāll get moving on next steps! 
Hi @benjamin - ok, this doesnāt make sense to me. You say that my library is not so large that it should cause a problem but then you say I donāt have enough RAM for my library. Well, seems to me the device should not need more RAM as it is designed to work with a library my size. Iām certainly not inclined to pay for more RAM but it you want to provide me with more RAM gratis I will be happy to install it and let you know if it fixed the problem.
The more we discuss this the more my conclusion is that the device is either underpowered or that there is something wrong with my device. If there are not others having these types of issues it looks to me as if there is something wrong with the unit and it should be replaced. If others are having this issue with libraries around the size of mine then it seems like a design flaw and you should provide more RAM or a refund.
At this point, if Roon is unwilling to increase my RAM or send me a new unit I will have to sell the unit and move to a different solution.
Thanks,
Keith
Keith
I am having the same issue. My library previously worked fine on my nucleus one. Not anymore. Constant crashes remotes always looking for server. I think this is from updates to software. I am seriously considering smashing this device into a thousand pieces and moving on with life. I read through this thread and am amazed at your willingness to comply with all the technical work around to help these guys troubleshoot your problem. The amount of time/money invested in this issue is absurd. This is a consumer device for music lovers not tech heads. Iām convinced these Ones are very cheap, underpowered devices not capable of handling large libraries and increasing software functionality You should have been offered a new device at this point, you havenāt. That is very telling about the company and the product.
Had some time to play with this today. No doubt this thing has memory issues. Server will run for a5 m minutes max and then stop. I can see in the remote that it is trying to scan the files. It will process through a few thousand files usually before it crashes. My library is around 130k currently itās added 112k Iāve deleted No files to keep it moving. just constantly restarting the server and rebooting to push it forward. Nothing works consistently other then brute force of just rebooting and hoping it will process more before crashing. At this pace may sometime this weekend the library will be added . As I stated earlier this was not previously an issue. something happened in the recent updates to cause this issue. I doubt they will acknowledge it, bit it is their software and poor testing, no doubt. There is no excuse for this sort of processing. I have worked in software development for the last 40 years and can tell you this is a complete joke of a product At least the library build components Hardware on nuclear One was poorly thought out and clearly isnāt able to handle what they are throwing eat it anymore they should upgrade everyone for free
Hi Jim - what you describe here is exactly what happened to me when I first purchased and tried to restore a backup. Finally I just gave up and re- added my whole music folder and it took forever with all the restarts. I only have 83,605 tracks. Now that I have added all my files it still restarts very frequently after running out of memory. It will restart even when Iām not using it.
I believe it is under powered for a medium sized library. if it is supposed to be able to handle 100k+ files this type of behavior is not acceptable and some remedy should be available. I too believe most of the issue lies in the software and while it might be fixed at some point, an acknowledgment of the issue would be appreciated. Honestly at this point I have turned it off and reinstalled the server on my Mac Mini M1 and it runs just fine. Although, the app on my iPhone was crashing constantly last night. Not sure what that is about either.
Best of luck. I hope we both get some kind of satisfactory resolution at some point. Not out of hope just yet.
I am going to upgrade to 16 gb RAM tomorrow 35 bucks. Ill let you know if this fixes anything
Iām running ROCK on a small NUC. By the looks of it, it has similar hardware compared to the Nucleus One. It came with 12 gb of RAM soldered on the mainboard.
It runs for weeks on end without crashing. With a 6.9k album and 101k track library. About 15k tracks are from Qobuz. The rest consists of my own local library. 
Hopefully the RAM upgrade will fix your issues as well.
1 Like
Yes, please let me know how you make out. if $35 can fix it that would be great. Thanks.