Regular crashes

Roon Core Machine

Nucleus with built-in 4 GB disk

Networking Gear & Setup Details

Dedicated Netgear GC510P with only Nucleus and dCS Bartok connected. No VPN.

Connected Audio Devices

Main: dCS Bartok> on the same switch. Further down the network and mostly not switched on with crashes KEF LS50w, Project Streambox Ultra, Auralic mini.

Number of Tracks in Library

90536 tracks
7940 albums

Description of Issue

Roon is crashing on a regular basis. It is unpredictable when, and I cannot find a pattern.It is really a poor experience now. I have invested in a lifetime contract (I think since 2016) and a Nucleus. When it happens it takes upon to 5 minutes(!) for the system to be back. Which forces me to switch to the dCS app, which is not convenient but never crashes.
I do experience these issues since a year now.

In the meanwhile I have changed the DNS to the Cloudflare settings. Faster reaction. But I still had a crash since. I have tried a lot.I think it is caused by the Nucleus.

Hey @Hans_van_Mierlo,

Thanks for your patience while we work through each thread. Following up on this issue, can you please take note of the date and time the next time you experience a crash, and share that information?

From there, we’ll be able to pinpoint what might be going on at the time of the crash :+1:

With that, I would also do a fresh OS install via webUI and see if the crashing continues. I’ll be on standby for your reply.

OK, I have done the OS already and will monitor the next crash and report it to you.

It just happened again. At 20:40 CET. At 20:54 (14! minutes later) Roon came alive again.Then it takes a couple of minutes more to have everything from Qobus,Tidal and the built-in SSD visible again.

Thanks for the info @Hans_van_Mierlo!

How is your nucleus connected to your router? We’re seeing a fair amount of networking errors in your account diagnostics, not concretely connected to your crashes, but an important thing to note nonetheless.

What external devices do you have connected to your nucleus?

With that, I’m seeing that you’re close to hitting the limit on your internal music storage space on the device. This doesn’t directly relate to your crashes, but things can certainly start acting funny when you’re out of space in general.

I’d be curious to see if you run into the same issues on a fresh database. Steps to follow below:

  • Create a Backup of your current Roon Database
  • Stop RoonServer from running in Nucleus’s WebUI
  • Navigate to your Nucleus’ Database Location
  • Find the folder that says “RoonServer”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Restart the RoonServer in the WebUI to generate a new Database
  • On the Roon Remotes, press “Use another Core” and connect to the new database

I’ll be on standby for your reply :+1:

Thanks Benjamin. Right now, the Nucleus is standing next to my main renderer in my music listening room. This is in the back my garden, which is approximately 75 meters of cable and three switches in between the nucleus and the router. So I can imagine that this is giving some errors. However, I do not have hick-ups or other bandwidth issues. I have a dedicated high-end switch, where only the Nucleus and the Bartok are connected, both with high-end CAT8 cable. Actually this is one of the mitigations I have tried to solve the frequent crashes. I use to have the Nucleus on the first switch close to the router. But even then I also had the crashes. Also when playing on the other renderers on the same switch.
What is better? The Nucleus close to the router (modem) or close to the renderer?
Also I did experience another crash on Sunday at 21:10 CET.

Oh and I have done all that you have mentioned. I am reluctant in doing it again, as I will lose my last added selection again.

Hey @Hans_van_Mierlo,

Generally speaking, having your core directly hardwired to your router will almost always provide a more stable environment.

To confirm, did you first test out using your Nucleus on a fresh database before restoring from a backup? Did you still run into regular crashes?

If you don’t run into crashing on a fresh database, you could have a corrupt database, or you may want to consider increasing your internal space on the Nucleus.

Thanks again Benjamin. So I will install the Nucleus again close to the Internet modem / router. Question: should I connect directly to the router or to the first switching the circuit. I always read that the built-in switches are not that good. The modem is the Gigabit connect by Ziggo (I think the manufacturer is Arris)

When you mention the limit do you mean the hard disk? I should just remove files or install a bigger SSD (this one is 4TB)? Or is it RAM memory. In that case how should I do that?

Just a note, this is from your router manual.
I don’t know which cable was used and how serious is this to be taken.

Thanks Axel! But I think a hub is different than a switch. Switches are used just as a direct connection. So I guess regular ethernet cables are ok.

Hey @Hans_van_Mierlo,

Directly to your router should suffice.

Take a look at the WebUI of your Nucleus - you’ll see only 5% left of 1848GB remains available. Removing files or getting a bigger SSD would certainly help with managing available space. You can check out this thread here on a more detailed step by step on replacing the SSD :

So the Nucleus hangs directly on the Modem(router). It still happens. Feb 8th 21:45 CET. Can you check what is going on now?

Hey @Hans_van_Mierlo,

Per my last follow up, did you take a look at the webUI of your Nucleus and see you are out of space on your SSD? I’ve listed a thread with steps on how to upgrade the SSD.

Let me know if this is something you’ll be able to do :+1: if not, you can always look at removing larger files on the device as well.

Hi @benjamin,
I am working on the removing of files. I figured that 4TB should do it for files at home with Tidal and Qobus to support. However, it is not easy to remove files… ;-).
But above I think you mentioned that this is not the reason of the crashes right?
Same as in the screenshot of the post: now at 6% of SSD available and still 89% of 114GB available. If the SSD space is causing the issue I will start removing more drastically. But then. what should be the available space?

9% now :slight_smile:

Hey @Hans_van_Mierlo,

Generally, keeping it around 15% is safe. However, upgrading your RAM is pretty cheap, and would be a good thing to do in the long run, especially if you plan on growing your library. :slightly_smiling_face:

The thread I’ve included in my previous reply will help you if you need it - it shouldn’t take more than 5 minutes. Let me know if you continue to experience issues afterward!

Thanks @benjamin,
I will continue to clean up the tracks on the SSD to reach around 15% free space. Plus I ordered 2 Crucial 8GB RAM cards. I will report back if the crashes persist or hopefully are gone after the upgrade.


@benjamin I have deleted albums until 15% SSD space (simply replaced a number of albums on the share by Qobus hi-res or Tidal MQA files) is free and I have quadrupled the RAM memory by replacing the standard 4GB card by 2x 8GB. Let’s wait and see the result.

1 Like