Erratic behavior of Nucleus after power outage

After a brief power outage last week, I opened the Roon Remote app and found just 52 albums, instead of the 550+ in my library. I restored the database from a backup, after which I could not connect to the Nucleus from the Roon app. The Nucleus web interface showed nothing amiss. I reinstalled the Roon app on my tablet, restarted the Roon Server Software, and finally reinstalled the operating system. Eventually I regained the connection to the Nucleus and my full library.

Even without power outages, I find I have to restart the Nucleus maybe once a month after the system freezes for reasons unknown. It may sometimes happen after software updates, although I can’t swear to that. Is there something wrong with my Nucleus, or is this expected behavior? Is there a logical sequence of things to try after these interruptions, besides rebooting everything under the sun, reinstalling software, etc.? Thanks in advance.

Roon Core Machine

Roon Nucleus, Rev. B, bought 11/2021.

Networking Gear & Setup Details

The Nucleus is connected to a Netgear Nighthawk AC1900 router and Netgear Nighthawk CM2000 modem with ethernet cable. I’m not using VPN.

Connected Audio Devices

McIntosh MA5300 integrated amplifer connected to the Nucleus with USB A to B cable.

Number of Tracks in Library

8301

@Paul_Murtaugh, I have moved your post to a new thread, since Roon staff prefer one issue per thread.

It would be really helpful if you could complete the support template below. Incidentally, please note that Roon responds to support requests in the order they were received. However, experience community members may be able to assist.

Please be sure to include details of your core, network, storage location of your media files, and any messages displayed by Roon. Thank you.

Roon Core Machine

<!‐-Include your operating system and machine info (Model, CPU, RAM)-‐>
<!‐-Write below this line-‐>

Networking Gear & Setup Details

<!‐-Your network gear (model of routers/switches) and if on Wi-Fi/Ethernet, are you using VPN-‐>
<!‐-Write below this line-‐>

Connected Audio Devices

<!‐-Specify what devices you’re using and their connection types, like USB/HDMI/Chromecast, etc.)-‐>
<!‐-Write below this line-‐>

Number of Tracks in Library

<!‐-Tell us how large your music library is, e.g. “30,000 tracks”-‐>
<!‐-Write below this line-‐>

Description of Issue

<!-‐Tell us about the problem you’re having in as much detail as possible. Screenshots are always appreciated!-‐>
<!‐-Write below this line-‐>

Including these details in your first post helps resolve your issues faster.

Hey @Paul_Murtaugh,

I’m sorry to hear you’re having issues with your Nucleus! You’ve done some excellent troubleshooting so far. As a good next step, could you please take note of the specific date and time you run into this issue, and share that info here?

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

My desktop computer rebooted at 0508 Pacific time on Thursday, June 8, so I’m almost sure that was the end of the power outage that wreaked havoc with the Nucleus most recently.

Hey @Paul_Murtaugh,

I would highly suggest investing in a UPS protector to help with any future damage that may be caused from a power outage. Mainly, you can experience severe corruption if your Nucleus is online and active during a power outage.

That said, I would suggest making a fresh backup for safekeeping, and then head to the webUI of your Nucleus and reinstall the OS. Here is more information on this:

Following your suggestion, I bought a UPS, but, before installing it, made the mistake of switching off the power strip which had the Nucleus plugged into it. There followed a long period of trying to regain functionality of the Nucleus: I repeatedly power cycled the Nucleus, restarted the Roon server software, restarted the tablet with the Roon app, turned the McIntosh amplifier off and on, and reinstalled the operating system. This led to a Roon system that sends a signal to the Nucleus but has no sign of the McIntosh audio zone anywhere in the Roon app (see screenshot). Nothing has changed in the setup of my system described above.


Update: I powered down the Nucleus using the web interface, and rebooted my modem and router. After the internet connection was reestablished, I powered up the Nucleus, only to find that the Roon app now does not find the Roon core.

Just a thought , when power is restored after an outage it is likely the Nucleus will boot quicker than the network , so it will be looking for a network connection and fail .

I get power outages sometime twice or three times a day , the answer maybe to allow the network to connect (Whatever coloured lights it has) then Reboot the Nucleus once a steady internet connection has been made.

Power outages (touch wood) do not seem to have any impact on my library/database

My NUC is set to restart on power restore ,so its a common issue. The only problem I normally see is Tidal fails to connect and I have to “Retry”

Thanks, Mike. Yeah, I wait until the network is back up and running before restarting the Nucleus. Currently, the Roon app is still not finding the Nucleus core. The Nucleus is accessible via the web interface, which shows an OK status for everything, and via my router web page. I’ve checked and rechecked the physical connections between the network, the Nucleus, and the amplifier. Given the variety of dire symptoms I’ve been seeing – corruption of the database, inability to find the audio zone, and inability to find the Roon core – this feels like a hardware or software failure in the Nucleus. Hopefully Roon support will weigh in soon.

Hey @Paul_Murtaugh,

It could be the case that the network settings need to be refreshed on the Nucleus. I will list out the needed steps below.

1. Connect the Nucleus to a monitor or TV via HDMI.
2. Connect a USB keyboard to the Nucleus and boot up. 
3. Press ENTER on the keyboard.
4. Type: resetnetwork
5. Press ENTER again.

Let me know if you’re able to connect after the above steps. Thanks!

After Step 2, the manufacturer, model, o.s., serial, and hostname appear, along with the messages: ‘Searching for network address … If this persists, please check your network connection’. No further effect of pressing ENTER. When I type ‘resetnetwork’, I get ‘Network settings reset. Hit enter to continue’. After I hit ENTER, I go back to the ‘Searching for network address’ messages.

When I reinstall the Nucleus on the network and try to access it with the Roon app, I’m back to the ‘Remote connection … Waiting for remote Core’ screen.

Hey @Paul_Murtaugh,

Thanks for giving that a try! Next, we’ll want to see how things run on a completely fresh database. Steps to follow below:

  • Create a Backup of your current Roon Database (if you don’t have a recent backup available)
  • 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

Let me know things go prior to restoring from a backup. Thanks!

I have only linux machines in my house. How can I find the Nucleus’ Database Location?

The path is given in the link above, which isn’t just about the Nucleus

Thanks, Suedkiez. The exact paths in the link depend on the o.s. (\NUCLEUS\Data for Windows, smb://NUCLEUS/Data for Mac). I doubt that you can access the Nucleus Core using linux, but someone correct me if I’m wrong. So, Ben, I can’t complete the troubleshooting steps you outlined above, unless there’s a different way to reset the database.

But this has to be more fundamental than a database issue, doesn’t it, if the system hangs at the ‘Remote connection … Waiting for remote core’ screen?

Sorry, I had misread, I thought your Core was running on Linux.

Of course you can access the path on the Nucleus from Linux, it’s just the SMB protocol, implemented by Samba on Linux, which is available in any Linux distribution. (The Roon OS on the Nucleus and ROCK is based on Linux, so …)

As usual, there are many ways on Linux. You can do it on the command line or in the graphical desktop environment that your Linux distribution uses.

If you use Ubuntu or Fedora, the desktop environment is usually Gnome. There, you start the file manager and click Other Locations in the sidebar:

The Nucleus should normally appear there automatically. For me it’s ROCK:

Double-click that and then go to Data. It will ask for username and password, enter guest/guest. You may have to choose “Registered User” first so that you can enter username/password. You can also choose to remember the password.

Then you will see the folders as described in the above link:

The Nucleus will appear as connected in the sidebar as well, you can rightclick this and add a bookmark, which will remain in the sidebar for later access:

If you use a Linux distribution with the KDE desktop environment, it works similarly in their file manager, see here:
https://www.addictivetips.com/ubuntu-linux-tips/connect-to-servers-on-linux-kde-file-manager/
(This describes entering the smb:// path in the address bar, but you can click Network in the sidebar just as well)

Other distributions such as Manjaro, or what have you, will either use their own desktop, where it will work very similarly, or they use Gnome or KDE anyway

Hi Suedkiez, Thank you very much for taking the time to walk me through this. I managed to access the Nucleus by navigating to smb://xxx.xxx.x.x, where I got the IP address for the Nucleus from my router web pages. I was given the option to log in as Anonymous, which let me access the RoonServer folder.

Ben, I followed your instructions to create a fresh database, and, miracle of miracles, when I used the Roon app to select another core, I was able to access Roon once again. You mentioned that I should wait to hear from you before restoring from a backup, so I will do that. Many thanks for your help with this problem.

2 Likes

Yes, a huge thank you for the step-by-step @Suedkiez! :pray:

This was a good test to perform, as it indicates a fresh database is able to properly boot up and function. You are free to go ahead and restore a recent backup and let me know how things run. :+1:

1 Like

Hey Ben, I restored from a backup, and I think everything’s fine. There were some heart-stopping moments when I couldn’t connect to the Nucleus and when my library was ‘stuck’ at 61 albums, but those issues seem to have resolved. Thanks again. Until next time! :slight_smile:

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.