Issues with Nucleus One setup and SSD usage (ref#K9U4HR)

Select your Nucleus model from the list below

· Nucleus One

I'm having trouble with my Nucleus hardware

· Other

Select the option that fits best

· 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

Nucleus one to matrix element s acting as network bridge to Pontus 15 toAthena preamp to Thallo main amp . Had issues with ticking and distortion .removed everything and reconnected clearing cache etc .all seems fine now but question is ..I am running two SSD on usb A rear panel 5tb and 4 tb ...is that permitted ? If I wanted could I also add internal SSD in addition. ? Regards Roger

The important thing to bear in mind is that the Nucleus One is specified to handle up to 100,000 tracks in a Roon Library. You already appear to have 9 TB in external storage available and now you want to add more storage internally? That would seem to suggest that you want to hold more than 100,000 tracks in your library - and this will impact the performance of Roon.

Hello @Roger_Schofield,

Glad to hear the ticking and distortion cleared up after reconnecting everything.

To answer your questions - yes, running two SSDs on the rear USB ports is perfectly fine, there’s no restriction on the number or size of USB drives. And yes, you can also add an internal SSD: the Nucleus One has an internal bay for a 2.5" SATA drive, which you can format directly from the Nucleus web administration interface and use as music storage alongside the USB drives.

That said, may I ask what you’re planning with the additional storage? If the goal is simply more space for your library, the internal SSD is actually the preferable option - it keeps the storage inside the unit, frees up the USB ports, and avoids any USB enclosure/controller quirks (which occasionally show up as exactly the kind of playback artifacts you described).

One thing worth keeping in mind, as Geoff mentioned above: the Nucleus One is specified for libraries up to around 100,000 tracks. This isn’t a hard cutoff - it’s a guideline reflecting overall library complexity - but as you grow well beyond it, you may start noticing slower browsing, searching, and longer startup times. So the storage itself isn’t the limit; the library size the Nucleus One has to manage is.

Hi @Roger_Schofield,

This thread will shortly auto-close without any new responses, but you can always reach out in a new tech support request if you require any additional troubleshooting or have further questions. Thanks!