What happens if you press the "Select a different Roon Server" button?
· I don't see Roon Server.
Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.
· No, the issue remains the same
Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.
· No, the issue remains the same
Please select how you've connected your Roon Server to the internet
· Roon Server is connected by *Ethernet*
Have you checked your firewall settings to ensure that Roon is allowed through?
· Roon still won't connect even after checking this aspect
Have you verified that Roon Server is on the same subnet as your Remotes?
· My Remotes and Server are on the same subnet and I still can't connect
Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.
· I've reinstalled the Roon Remote but it did not help
What is the operating system of your Roon Server host machine?
· *Nucleus*
Select any of the following components that are present in your local network setup
· None of the above
Describe the issue
Roon NucleusPlus won't connect to the network after restart. Ethernet lights blinking but not on network.
Describe your network setup
it looks to me like the Linux install is not booting up. I have it connected straight into my laptop and trying http://necleusplus.local and it's hanging
@Carl is asking the correct next questions, are you able to get your Nuclues connected directly to your primary router?
With that, if you’re still unable to connect, could you connect your Nucleus to a monitor via HDMI (while still connected to your network) and share a screenshot of what you see?
I would also review your router settings and ensure that all your Roon devices are running on the same local subnet within your network.
My Nucleus+ is normally in the living room media cabinet. When it’s in there, there are probably three 1 Gbps switches and one 2.5 Gbps switch between it and my Synology NAS. On Friday, we had a power failure that lasted 2.5 hours. Everything in the media cabinet and the NAS in my office are on UPSs but the switch in the utility closet is not so when the power goes out my home office and the living room are cut off from each other over wired ethernet.
The real issue was when the power came back on. I went around the house powering things up and eventually noticed that the Nucleus+ was not on the network. The port lights on the back of it were flashing but I could not ping it or get into the web interface. I problem-solved on the network issues and power cycled the Nucleus+ several times to no avail.
Eventually, I pulled it out of the media cabinet and brought it into my home office to make sure that I had only one switch between it and the gateway router and NAS. Even then, I was getting nothing. Then, it finally came on the network and everything seemed normal again.
My conclusion here tentatively is that when I powered off the UPSs in the media cabinet and the power was cut off to the Nucleus+ it must have gone down with it’s file system(s) in a dirty state and when it powered on it was running fsck … and my impatient powering it off and back on again only delayed things further.
As it is, though, I think it would make sense if this thing had something like a BMC so that it’s possible to see the console in the web interface even if the main os is running a fsck. I realize that that probably sounds like madness and you think I should just plug the HDMI in. Fine. I guess I’ll do that next time.
BTW, a few other things:
Of course my whole house is on one subnet. It seems odd to me that anyone would have it any other way unless it’s by ignorance or accident.
Over the course of the weekend, I purchased a 4 TB Samsung EVO SSD, installed it in the Nucleus+ and following the recommended steps moved my collection (1.2 TB) over to that. It’s now running on the internal SSD and all is good and intact. My playlists are good. etc. With this change, I think I’ve eliminated at least half of my headaches here. I was able do a CIFS mount directly on my NAS and rsync the files over so I still have a fault-tolerant copy of my music which will remain the “master” and I’ll just rsync any additions via the CIFS mount in the future.
With all that said, the Nucleus+ is still on the floor in my home office. Probably tomorrow, I’ll shut it down and move it back to the media cabinet in the living room. I’ll also temporarily connect the HDMI port to the TV and watch it boot up just to see what that looks like.
Please keep this ticket open until I’ve confirmed that #3 worked okay. To me, this whole interlude suggests more fragility of the Nucleus+ than I realized. It’s kind of supposed to be robust to power cycling and whatnot. Granted it did come back eventually but you should probably be running file systems which are more robust and/or you aren’t using write caching on the root file system etc. In other words, if it’s a consumer product, which it is, then it should behave like “a box”. When you switch on “a box” with only a short delay (like 10 seconds) it’s visibly alive and ready to use. What you have here acts like “a Linux computer”, which it is, but it should have robustness that keeps it from acting like one. i.e. - it should be almost impossible to cause it to need fsck (if that’s indeed what it was doing) when you switch it on. I’ll let you know.
