My Roon Core Is No Longer Recognized

Support Nucleus Support
1

Roon Core Machine

I have a Nucleus B and a Samsung SSD internal hard drive.

Networking Gear & Setup Details

My DAC is an ADI-2 DAC FS

Connected Audio Devices

I have Bryston 7B mono amps, B&W 800 Series 802 D speakers

Number of Tracks in Library

I have less than 2000 tracks from my personal CD’s
The majority of my music is selected directly from Qobuz

Description of Issue

Ever since the 2.0 update came out and I attempted to update to it, my Roon Core is no longer being recognized. It has now been about 4 months since I could play my music, but I feel overwhelmed by the problem and have been ignoring it. I did have ARC capability for a short period but no longer.

I am worried about making changes because I don’t want to lose all my music from Qobuz. However, I do wonder if it would simply be best to just start over from scratch, but somehow still be able to keep my playlists from Qobuz. All my personal CD’s are on my Nucleus and my backups have been continuing automatically. I have simply been overwhelmed by what seems like a daunting issue.

Is there a relatively simple way to start over without losing all my playlists created with Qbuz? Any advice would be greatly appreciated.

2

Hey @user214,

Thanks for your patience while we work through each thread. I’m sorry to hear you’ve had issues getting your Nucleus up and running after updating to 2.0!

I understand how daunting it can feel when such an issue pops up. The good news is it sounds like your backups have been saved, so chances are we’ll be able to restore your core back to normal without issue.

Before doing that though, let’s see if we can figure out what might be going on! A good first step is connecting to the web UI on your Nucleus. See more information on this below:

Please share a screenshot of your webUI if possible. Let me know how the above goes!

4

Screenshot 2023-01-13 at 2.05.11 PM
Screenshot 2023-01-13 at 2.05.11 PM1380×1908 128 KB

Thank you! When I attempt to sign in I get the screen shot above. I am unable to connect to my remote core and it asks if I want to select a different one which I don’t. I presume this is the step you suggested in using Roon to load up the Nucleus. Hopefully, I understood your suggestion.

5

I suggest that you do click on the “Select a different Core” button - it may be that there’s a glitch and clicking will bring up the Nucleus and you can then connect to it.

6

Screenshot 2023-01-13 at 4.41.46 PM
Screenshot 2023-01-13 at 4.41.46 PM1464×1396 140 KB

Do you suggest that I set up a new Roon Core by selecting the Use this Mac button?

7

@benjamin is asking you to sign into the Web GUI. That can be reached by entering the address of your Nucleus into a browser window on a PC, Mac, iOS , or Android device.

Don’t do that.

Since you have a Nucleus, you want ‘Find my Roon Core’,

What happens?

8

It searches for my Nucleus but can’ find it

9

At this point we need to see if the Nucleus is getting an IP address and if so what does the Web GUI indicate.

Follow @benjamin’s link to get to Web GUI.

Another way to get the Web GUI is to enter nucleus.local into a browser window. I’ve never had luck with that, but try that method.

There are two other ways to find out what your Nucleus IP is. If you’re comfortable with getting into your router software, then if the Nucleus is on the network, you can find the IP there.

The other way is to hook up a monitor to the Nucleus at boot time and take note of the IP that is displayed.

Once you get an IP, enter it into a browser and you should see something like this -

image
image1185×700 23.4 KB

It sounds like your Nucleus might not be on the network. In that case, we need to see what messages are being put out at boot time. The only way to do that is to hook up a monitor.

1 Like
10

I think you are probably right about the Nucleus not being on the network. You suggest hooking up a monitor. Are you suggesting connecting the Nucleus to a Mac via a cable?

11

No, I am saying to hook a monitor (display device) via HDMI to the Nucleus. Boot up the Nucleus and take note of the messages that are displayed.

12

I connected an HDMI cable to the Nucleus on both the HDMI-A and HDMI-B and then to a Dell Monitor. I then powered off the Nucleus and then powered it up again. The Dell Monitor failed to recognize a connection.

13

OK, that sounds like a hardware problem.

I’ve seen 3 possible problems with Roon hardware.

The Ethernet port could have died; the easiest and cheapest to fix and (ironically) also the rarest problem.

The next cheapest and easiest to fix is a dead M.2 drive that holds the Roon OS.

The one problem you don’t want is a failed motherboard or motherboard component.

Is the Nucleus two year warranty in effect?

14

Yes. The Nucleus B was purchased new last January. Is it possible for me to determine if it is a hardware problem for sure before mailing in to someone?

15

Yes, but you have to open the case.

You should wait for @support to chime in before you do anything further.

Good luck.

1 Like
16

Thank you for your assistance. Should I contact support or will they respond automatically?

17

I tagged them in the post above.

18

I have been advised that my Nucleus B may have a hardware issue and that I should wait for Support to chime in. Not sure how I do that. Should I contact someone at Roon?

19

Thanks, just saw your post.

20

I just rechecked my HDMI connection to make sure it was secure and in the process my Nucleus B was recognized. It shows Manufacturer as Roon Labs. Model as Nucleus. OS as RoonOS 1.0 (build 227) stable. Serial #54B2039EF9DD. Host Name is Nucleus.
It says, “Roon can be accessed by opening any Roon Remote product. If you don’t see Roon OS Web UI can be directly accessed at http://192.168.86.38/”

21

Screenshot 2023-01-14 at 12.49.39 PM
Screenshot 2023-01-14 at 12.49.39 PM2372×1960 282 KB