Roon Nucleus Titan recurring disconnection and reconnection issue (ref#KS6NLT)

Hi! What’s not quite right with Roon?

· Roon is slow, freezing or won’t start

Roon is slow, freezing or won’t start

· Roon won’t start up at all

Tell us what's going on

· Recently purchased the Roon Nucleus Titan and imported all my music (30,000+albums) from my NAS drive which took almost a week. Both the Titan and NAS are wired to two separate switches. Most recently when connecting to Roon it wall work for a few minutes and then continues to go to the “Uh oh, something’s not right…” and then the half moon with moving vertical lines and/or “Waiting for your Roon Server…” message appears and then it will reconnect after awhile, for a few moments and then the whole cycle starts over again.

Tell us about your home network

· Router is a Cisco model CBS1 10-8T-D. My switches are Nordost QNet 7 for the NAS Synology DS923+ and a pakedge SX-8P switch for the Titan along with eero Pro 6E extenders throughout the house. I was using the synology DS923 as my Roon core prior to the Titan.

Hey @Bob_Jahn,

Thanks for the detailed write-up.

The good news is this isn’t a network problem. Your switches, eeros, and the connection between the Titan and the Synology all look fine in the logs. What we’re seeing instead is that the RoonServer software on your Titan is running out of memory and being automatically restarted. Over roughly a three‑hour stretch of your logs, the server restarted 16 times, about once every 8 to 12 minutes. That restart cycle is exactly what you’re experiencing: it works for a few minutes, then the server becomes unresponsive, restarts itself, shows “Uh oh…” / “Waiting for your Roon Server,” reconnects for a moment, and repeats.

The cause is memory pressure. The Titan ships with 8 GB of RAM, and your library has grown large enough that the server might be hitting that ceiling, it’s spending a quarter to a third of its time on memory cleanup, with pauses long enough that it stops responding and gets restarted.

A couple of things would help us get you stable:

  1. Let’s confirm the true size of your library. The server currently shows around 380,000 tracks across your ~30,000 albums. Because your initial import from the NAS ran for about a week, it’s worth making sure nothing got imported twice, a duplicated watched folder or an interrupted import can inflate the track count significantly. In Roon, go to Settings → Storage and confirm you have only one folder location pointing at your NAS music (not the same library added more than once). If you’re seeing obvious duplicate albums in your collection, let us know, cleaning those up may bring the size back down on its own.

  2. Ease the load while it’s still processing. Roon is currently running full‑speed background audio analysis across your entire library, which adds heavily to the memory and CPU load during a big import. Go to Settings → Library → Background Audio Analysis Speed and set it to Throttled (or Off for now). This alone should help it settle down while the library finishes building.

  3. If the library is genuinely this large, the Titan will benefit from more RAM. For libraries in the several‑hundred‑thousand‑track range, 8 GB is on the light side, and 32 GB makes a real difference. The Titan’s memory is user‑upgradeable, we can walk you through the exact part and steps if you’d like to go that route. (One note: self‑performed upgrades can affect warranty coverage, so we’ll make sure you have everything you need before you start.)

If you can start with steps 1 and 2 and let us know what you find on the Storage screen, and confirm whether the album/track counts look right to you or seem inflated, we’ll know whether this is purely a “needs more RAM” situation or partly a duplicate‑import cleanup. From there we’ll get you to a stable setup. :+1:

I did verify that there are no duplicate files in storage that were imported and the track count prior was 381514. Regarding The Background audio analysis I’m having difficulty tuning it off due to Roon not staying connected long enough for me to make the adjustment, I’ll continue to try. It appears the 32 GB of RAM might be the answer. Thanks, Bob Jahn

Hey @Bob_Jahn,

Thanks for checking the storage side and confirming the track count. Since the duplicate import angle is off the table, the next most likely factor is still the Titan running up against memory limits while it is trying to keep up with a library of this size.

We recently released a new version of Roon that includes performance fixes, so please try updating to that first and see whether it changes the behavior. We would also like you to run the Clean Up Library function, but only after making sure all of your active music directories are connected and visible in Roon. If that function is run while a storage location is offline, any stale references to those files will be removed from the database, along with their associated metadata and edits.

Once you have a chance to try that, please report back with what you see. If the disconnect and reconnect cycle is still happening after that, we can certainly look into the RAM adjustments further.

Unfortunately, Roon will not stay on long to run the cleanup library function. I was able to update the software with no changes. I’ve decided to upgrade the RAM to 32 GB.

Thanks, Bob Jahn

Hello @Bob_Jahn

Please hold off before you open the Titan, and let us correct something we told you earlier.

In our first reply, we mentioned that the Titan’s memory is user-upgradeable and offered to walk you through it. That was not good advice for your situation. Your Titan was recently purchased and therefore still under warranty, and on the current Nucleus generation, any work done inside the unit by the owner voids that warranty. Our manufacturer is strict about it. We should have led with that rather than leaving it as a footnote, and we are sorry for the confusion.

There is a better route. We run an official RAM upgrade program for the Nucleus One and Nucleus Titan, precisely so that owners do not have to open their own units. For the Titan we can take you from 8 GB to either 16 GB or 32 GB, we do the work ourselves, and your warranty stays fully intact. Given the size of your library we would point you at 32 GB rather than 16 GB.

Two things from you, please.

First, and most importantly: please tell us whether you have already opened the unit or ordered memory. If you have, please say so plainly and we will work out where that leaves you. It is much easier to help if we know.

Second, please tell us whether you would like to go ahead with the official upgrade.

One practical tip in the meantime, since you mentioned you cannot stay connected long enough to change anything. Your server is restarting roughly every 8 to 12 minutes, so you do have a window. As soon as Roon reconnects, please go straight to Settings, then Library, and set Background Audio Analysis Speed to Off in one move, without browsing anywhere else first. Leaving it off will take a lot of load off the machine while we sort the memory out.

I’ve already sent the unit into Roon to upgrade the RAM to 32GB.

Thanks, Bob Jahn

Hello @Bob_Jahn

Thank you for the update.

Glad that you have sorted this out. We are closing this thread. Feel free to raise a new one in case of any questions or concerns.