Have to Reboot Nucleus Every Morning

Roon Core Machine

Nucleus

Networking Gear & Setup Details

Internet: Comcast business
Router: Technicolor Device Type BWG, Model DPC3941B
Network: Linksys Velop Mesh Network
Roon connected to network through ethernet to a TP-Link 8 Port Gigabit Ethernet Network Switch | Ethernet Splitter | Sturdy Metal w/Shielded Ports |Plug-and-Play | Traffic Optimization | Unmanaged (TL-SG108)

Connected Audio Devices

Bluesound iNodes
QNAP connected to the Network Switch

My phone and iPad all connect wirelessly through the Mesh Network
My MacBook Pro is connected to the switch with an ethernet cable

Number of Tracks in Library

29011 tracks

Description of Issue

Ever since the update before this last one, when I bring Roon up on a new day, I get the message that it cannot read my database and to restore a backup. But if I reboot the nucleus instead, everything works fine until the next day.

If you check my history, I have database problems more than once a year - when you do major upgrades.

Richard, a few questions.

First, are you shutting down your Nucleus every night and restarting it the next day, or are you having to reboot manually due to the database issues? How long have you had the Nucleus?

What version of Roon are you on, 936 now? Are you able to create a backup from 936, and do you have a backup from 935 or 933?

Can you share a screenshot of admin screen of your Nucleus? It does not appear your Core software is an issue but rather your database, but the issues may be related or it may be the drive holding your database in the Nucleus.

AFAIK intended behavior.

Because your database has become corrupted. You should restore from a backup and if that doesn’t work, start all over with a fresh database.
You may also choose to use the restart workaround every day until the system eventually totally breaks and doesn’t start at all.

Maybe interesting reads:

2 Likes

It is conceivable this is a failing M.2 SSD. Mine began as running no longer that 14 days between reboots (my present NUC numbers 100+ days between OS reboots). These became more frequent until it was only running for hours at a time.

1 Like

I am running 936.

I do not shut it down at night. I just have to reboot in the morning.

It started two upgrades ago.

I have had my Roon since November of 2018.

I firmly believe that my problem is hardware. I have to rebuild my database from scratch once or twice a year. This is my 3rd year with database corruption issues occurring a couple of times a year after an upgrade

I have backups from build 903, 918, 923, and 931. Roon has not been able to do a backup since April 12th.

Attached are screenshots of my admin and backup screens.

Richard, just one last check, although it seems you probably have a hardware problem. Do you have an external USB drive to which you can try to save a manual backup just to confirm that this has stopped working?

Also, do you remember the last time you had to rebuild your database and possibly the Roon version you were using?

@Robert_F

REBUILD DATABASE HISTORY
Last “old” RoonServer I created was 2/5/22
I also had to create them:

  • 1/29/22
  • 12/30/21 (5 restore from backup retries)
  • July 2021 (5 restore from backup retries)
  • May 2020 (3 restore from backup retries)

USB DRIVE BACKUP QUESTION
To create the USB backup, do you want me to attach the USB drive directly to the Roon? Currently it is connected to my MacBook Pro.

NEW DATA POINT
I noticed this morning, that the Nucleus does appear on my network in the morning. I have to reboot it so that it shows up and I am able to access the Nucleus.

Thanks again Richard. Yes, it would be useful if the external drive were connected directly to the Nucleus, but the external drive it cannot be formatted as a Mac drive (either HFS or HFS+) as the Nucleus cannot write to these types of drives; exFAT, NTFS, and other types of formats also work with Roon. It definitely is acting as if there is a hardware issue somewhere in the Nucleus.

@Robert_F

I don’t know anything about external drive formats, but I had two that I tried:

I directly connected a

  • G-Drive that Roon has backup to before (but I can also access files from my Mac, so don’t know if it is the right format or not.)

  • A Western Digital Passport I have used with Windows machines.

In both cases, I got the “creating snapshot of your database” message and it looked like it was working and then I got the same “cannot load database” error screen.

Should I try to restore a backup, and if so, from which build? I am running 936, and have backups from:

903, 918, 923, and 931

If it is a hardware issue, what is the process? I love, love, love Roon, I have had such trouble with my nucleus in the past 3 years it is getting tiresome.

There appears to be a number of problems here, some pointing to network issues which may be the source of the problem.
As a former Linksys Velop user I often experienced erratic or obscure behaviours, usually problems accessing various devices and/or using Roon. On these occasions I restarted the velop network which almost always resolved my problems (many hours spent with linksys support never resolved the root cause).
So, if you haven’t done it yet, power off your devices try restarting your Velop network & the power everything back up (if using a separate router reboot that as well), It only takes a few minutes and can save a lot of “headaches.”

I reluctantly dumped my Velop network hardware but everything has been stable since.

The most recent one I guess. What would be the reason to choose something older without need?

I am not able to restore from any of my backups. It says it cannot find them, though I can see them there. I had to build my database from scratch again. How do I get my nuclear repaired or replaced?

I assume by contacting your dealer.

Will do BlackJack, thanks!