Any time a loss of power happens it’s always a half hour trying to get my Nucleus Plus to reboot and on the network. More difficult to know what is happening when there is no status light on the front panel and the rear only has the Ethernet activity lights and the power button which seems to be always on if powered is connected.
i cut the power completely to the stereo because the Ropieee has a screen and the I can see the boot sequence of that device which should correlate somewhat at least to the nucleus plus as that is also a Pi3 I believe. But I keep trying to restart the nucleus blindly until at some point it connects.
With ropiee loaded and waiting to see the roon core, I basically keep rebooting the nucleus plus give it several minutes to see if it connects to the ropieee. When I see that it still hasn’t I check the ip address, that says it can’t connect so I check the room app, still searching for the nucleus so I power that off, wait a couple of minutes, plug it back in, press the power button and repeat…half an hour this far and still it doesn’t see it. Keep going until it does. This is the usual procedure when there’s been a power loss. Doesn’t happen often, but when it does I know I’m in for a nightmare…
The Nucleus Plus is not a Raspberry Pi3. I believe it is a 7th or 8th generation (depending on whether it is the first generation or the ‘Rev B’ model) Intel i7.
I’m not sure what the Nucleus Plus boot times are (I’ve never owned one) but I strongly suspect that they exceed those of the Raspberry Pi3 (or Pi4) by some margin.
As mentioned it is not a Rasp Pi it is an Intel CPU (if your’s is a Nucleus + then that was an i7). Also, unlike Pi’s, the RoonServer is starting up and running an in-memory database. Any sudden loss of power can corrupt the database, so quick shutdowns should be avoided (long press on power button). And, the unit should be on a UPS to provide you the opportunity to gracefully shut down the PC before power drops.
So long press, no long press, any suggestions as to what I should be trying?
The power had been back up for a full day before I decided to try and restore the connection, knowing full sell the nightmare I’d encounter.
It was re-connected to power, I pressed the button more than ten minutes ago. Surely that is enough time for the Nucleus to have booted but the ip address times out, and neither the Roon app nor the Ropieee “sees” it. And without ip address access, what else can I troubleshoot? A scan of my network does not show the device at all though the ethernet status lights are blinking.
At that point, I’d plug it up to a keyboard and monitor (and network cable of course) to see what the screen is showing. If the screen is indicating it cannot receive an IP address, then the first thing I’d do is to do a network reset as detailed on this FAQ page:
I live in South Africa , so I’m a self styled expert on power cuts , we had 2-3 a day until a year ago.
The problem is that your Nucleus will start up almost instantly but your network will take much longer So once started the Nucleus will try to connect to Tidal (etc) and Roon Cloud BUT at that stage your network will not be ready .As @Rugby says the Nucleus will take a while to startup depending on the library size but in doing so needs a network connction
So let it all start up , when the router shows network connection Restart the Nucleus or go to the Web Admin page and restart the Server software.
I agree db corruption is a possibility but I went through several years of power outages without any corruption , my db must be nearly 10 ys old.
If this doesn’t work you may have a more serious problem, I followed this method for several years with 100% success.
Changed the port on the switch the Nucleus is connected to, changed the ethernet cable; I don’t have a USB to ethernet adapter right now. The network reset instructions say:
If you’ve set a static IP on a RoonOS Server (ROCK/Nucleus) that is no longer accessible on your network you can resolve this by resetting the network settings on your device. You can do so by following these instructions:
Connect the Nucleus to a monitor or TV via HDMI
Connect a USB keyboard to the Nucleus
Press ENTER
Type resetnetwork
Press ENTER
All network settings will now be reset and you can try connecting to the server once more.
Step 1. does not produce any video out of either HDMI port. I’ve tried following steps 2 through 5 blindly, but nothing.
Any other suggestions before I seek support? Unfortunately, I’ve always found that to be hit or miss. The few times I’ve had trouble over the more than ten years I’ve been a Roon user, I’ve found success easier to find here in this forum.
I have lots of internet connected devices- Ring doorbell and security cameras outside, Wyze cameras inside; they all take forever to come back online while my Eero boots back up and serves WiFi. I know the network is back up and running fully when these devices start informing me that they’ve reconnected to the internet.
I may have connected the HDMI in the past and don’t remember what the output should look like during boot, but right now neither port is outputting anything. And pressing Enter, typing “resetnetwork” and pressing Enter sequence without video output has not worked any of the several times I’ve tried it. My database is regularly backed up to a flash drive, I presume my music is safe on the internal SSD, and I do have that backed up as well. I’m not afraid to start from a factory reset- it would not be the first time I’ve had to do it, though the last time was certainly much closer to the beginning of my Roon experience…I don’t even remember those steps though I’m sure I can find instructions. It may be an easier route than trying to troubleshoot this mess with Roon Support; I am hoping something is posted on this board that saves me from embarking on either of those unpalatable routes!
The Nucleus is a standard Intel NUC computer in a Roon designed case. Like any computer, if you are turning it on and it is not producing video of any kind, then it might be a sign that the motherboard has died. At this point, I would absolutely engage Roon Support using the link I provided.