I recently acquired a Roon Nucleus One and installed a 4TB Samsung SSD.
Unfortunately, it has been impossible to copy my music library to the Nucleus One because of the instability of the Roon interface under Sequoia.
Roon crashes over and over again while attempting to move files to the Roon Nucleus One.
I have thus far installed Roon on three separate Macs running Sequoia and the result is the same on all three.
It is simply impossible to copy any reasonable amount of data to the Roon Nucleus One without the Roon software on the Mac constantly crashing. As it stands this makes it impossible to copy my music library to the internal SSD.
Does Roon intend to address the issue of unstable software under Sequoia in the their future?
I am copying the files from the hard drive on my Mac (using the Roon interface and dropping and dragging) to the new Nucleus Ones w/ 4TB SSD installed.
Also tried this on several MacBooks with attached external SSD - same result.
What I am calling the Roon interface (i.e. Roon installation from MacOS) continually crashes.
How much data are you trying to drag and drop? Does it work when you drag and drop just a few albums?
I am running MacOS Sequoia. Up until now I’ve been importing files by copying directly to the network folder on the Roon server (Method #2 described here). I just tried for the first time to drag and drop onto the Roon app, and it worked for a 1.5GB folder. I wonder if the problem is related to the amount of data or number of files.
mSpot: Because it is an initial setup of the Roon Nucleus, these are large file folders, so you may very well be correct. It does seem to work for small file sizes, but spending several days copying the library in smaller packets seems like an unreasonable solution. Thanks for your thoughts.
I can no longer see your other post here, which reads: "Hi David,
Fellow user here. For a large library transfer I always suggest the SMB Connection (Alternate Option) discussed in the Nucleus Internal Storage FAQ and how to transfer music."
That sounds like a reasonable solution. I will try it today.
I would be surprised if it is not a Sequoia issue, since I have replicated it on multiple computers with fresh installs.
If you search the web, it seems like there have been many issues with Sequoia and Roon. That being said, I am not really qualified to speak definitively on this issue.
It’s frustrating since the entire point of the Nucleus is (in my opinion) to be “plug-and-play”. In fact, purchased it to avoid these types of troubleshooting issues. Thank you for your input.
There have been many with network access permissions, and this is reflected by many threads on the forum. In the same way, one would expect crashes during copying to be reflected, but there weren’t any reports (at least no significant numbers)
Maybe it’s caused by something else. Like I said, in any case something to investigate for support.
I suspect that the Roon app runs out of memory and crashes when the drag and drop has a large number of files. It’s a bug that should be fixed, but an advantage of copying directly to the shared network folder using the Mac Finder is that you can arrange the folders as you’d like. With drag and drop into the app, Roon copies files into a new subfolders path: “Roon imports” > “[computer name]” > “imported at [date][time]” which most people would probably find cumbersome.
BTW, look for the folder InternalStorage and copy your files there (Data > Storage > InternalStorage)
Thanks for taking the time to write in! Sorry to hear about your issues with transferring your files.
The good news is we’re not seeing any direct errors in relation to RAM and your Nucleus holding/receiving your local library.
On the Mac side, we do see an issue around the network connection with your Nucleus’s /Volumes/InternalStorage folder, which is leading to a crash.
Can you provide a bit more information around your network setup, and how your Mac and Nucleus are connected to your primary router? Can you please test out setting up a direct ethernet connection from both machines to your router, and see if the same issue occurs?
If you have any Apple Crash reports in Console (Applications > Utilities > Console), please also upload them here at your convenience for our developers to investigate: Log Uploader
First of all, I want to thank Rugby, Sudkiez and mSpot once again for helping me to figure this out. I am grateful to the community of people on this chat.
I think that Rugby really nailed the correct answer when he wrote to use the “SMB Connection (Alternate Option)”. This is the only reasonable solution. It works. The Roon drop-and-drag interface does not and this really cannot be blamed on the stability of my network (or SMB would not be able to transfer files that Roon cannot).
I think that mSpot was also ver insightful, when he wrote “I suspect that the Roon app runs out of memory and crashes when the drag and drop has a large number of files. It’s a bug that should be fixed, but an advantage of copying directly to the shared network folder using the Mac Finder is that you can arrange the folders as you’d like. With drag and drop into the app, Roon copies files into a new subfolders path: “Roon imports” > “[computer name]” > “imported at [date][time]” which most people would probably find cumbersome.”
There is a clear advantage to what mSpot is suggesting, particularly because it allows you not only to better organize files and folders, but also to better locate and easily overwrite corrupted and/or incomplete files and folders.
As for wiring my desktop directly to the router, I live in the (modern) world of WiFi. I just am not set up to snake dozens of meters of CT-6 cables around my apartment. I imagine I am not alone in this.
All and all Roon is great, but from where I stand the Nucleus One isn’t as refined a solution as it could be for Apple users with large libraries. Hopefully, Roon will work out the bugs.
In the meantime, Roon may wish to post an FAQ with the SMB work around. It may also wish to incorporate direct error (crash) reporting as an option in its software.
Thanks again to all of you for your help. I very much appreciate it.
We don’t quite yet have sufficient information to draw a firm conclusion on this case and we’d very much like to equip you for long-term success with this setup and identify any potential improvements on our end.
Since what is crashing appears to be the Roon app on your Mac, that would suggest the problem lies there (i.e. the Roon app), and not with the Nucleus One itself.
I have the same setup here: Roon (client) app on MacOS 15.3.2, with Nucleus One and 4TB Samsung internal SSD.
No issues copying whatsoever, using the SMB InternalStorage method, with rsync.
I have Roon running on a dedicated music server from Upscale Audio, with Roon running on my iMac and iPad, no problem whatsoever, so its not Roon, its your setup.
