Roon nucleus +
Ethernet from router to nucleus via gs108 switch
T+A pdp3000hv dac
Via usb
Playing music when sound suddenly stopped out of the blue.
Have plugged in and reboot nucleus and get the following
doesn’t find it
doesn’t find it
The 169.254.x.x address seen on the first screen usually means that your DHCP server, which is part of your router, is unreachable by the Nucleus.
As a first step, turn off all networking devices, and then turn on again, starting the ISP router last.
2 Likes
I had to move nucleus to another room to get to a screen with hdmi so just quickly plugged an ethernet cable in to get a little further along on the boot.
Strange for it to have a problem with dchp after such a long time.
A 2nd reboot of the router has solved it.
thanks @mjw
3 Likes
Had to restart my router again just , I am beginning to think it is a problem with either the router or virgin’s dchp service.
It’s been solid for ages and now since yesterday it has needed a reboot.
Must be your router. DHCP is a service performed by your router inside your network. Nothing to do with your ISP or the internet.
This morning, I have just checked Roon before going to work and it is again not finding the core.
If everything else on my network is working as usual wouldn’t a problem with dchp also affect them as well?
This seems to have started with the last software update (it is the early access version.)
A couple of things to consider.
-
If not done already, setup address reservation for the Nucleus in the router’s settings
-
Try a different Ethernet cable
1 Like
Martin , Are you referring to the ip address?
If so then that has been reserved for several years .
I had to move the nucleus to get to a screen to be able to take the screen shot I took a couple of days ago , which was connected by a different cable.
@Early_Access , would the logs show anything that might help me solve this problem.
Was this done at the router, or in the Nucleus web interface, or both?
At the router
I thought that may be the situation. Assuming the Nucleus is still connected to the alternative Ethernet cable, and you still have the issue, it could be a bad network interface.
Maybe someone else can chime in?
I have got home from work and the connection is up of its own accord, no idea how or why, will see if it stays connected or causes any more needs for rebooting.
@mjw Thanks for your suggestions I appreciate you giving your time trying to help me resolve it.
1 Like
Last night mid play it lost the Roon core again and now this morning it has found it again. .
At a loss as to why this is happening @Early_Access
@support
I’ve removed the “Solution” marker on this thread so that Support will circle back and help. Certainly sounds as though you have intermittent loss of LAN connectivity. Can you be specific about the current setup, i.e. is the Nucleus now back at its original position using the original cable, or is it still in the temporary location using the alternative cable? Thanks.
It is back in its original position , so from router to a switch and switch to nucleus, all Ethernet. Control via iPad or iPhone via wifi
What happens if you connect the Nucleus to a different port on the switch? If no change and you still get failures, follow up this test by connecting the router to a different port on the switch…
Any chance of changing the cables as a further test? I guess that you’ll just have to go through a process of elimination until you can isolate the faulty component. This may indeed be in the Nucleus itself, but let’s try and rule out any of the other possibilities first…
As suggested above, try connecting to different port(s).
Your router probably needs to be replaced.
Router or switch can die after being used for a long time. We had multiple failures of different brands of corporate grade switches (i.e. ten times more expensive than consumer switches) in our office in the last two decades.
2 Likes
Hi @RodS,
I am sorry you’re running into trouble here.
I’ve spent some time looking at the diagnostic logging for the unit and am finding a whole host of mount errors for your “diskstation” storage location. In fact, in one log alone, the error exists more than 20k times. Double-check that your Roon>Settings>Storage settings are all correct and either fix them or disable them if no longer in use. This error could also be a result of the unit losing connectivity to your storage location.
In addition to these errors, there is also a lot of “no route to host” errors that definitely indicate a problem with connectivity.
I would certainly investigate the angles provided by others here. Change the port on the switch, change the switch’s port on the router, and swap out cables.
It is also possible that the network card on the Nucleus is failing but that’s usually the last possible culprit.
Please let us know what you find and we’ll keep monitoring to assist you further.
Regards,
Wes
Hi Wes
The music is mounted on the NAS drive but I usually only turn it on when I am going to be listening to it. The power settings are set to turn the NAS off overnight.
I have now plugged the Ethernet directly from the router to the nucleus using a different port out of the router with no switch in between.
I will turn on the NAS and leave it on 24/7 for a while so that the logs for storage are not an issue.
The problem is that the Roon core keeps on having the core not found error.
Now I have swapped the routing between the router and nucleus I will see how it fares.
I will have to order in another Ethernet cable as it is approx 15meters long and not something usually stocked locally.
The router is a virgin media supplied one so I will see what happens with what I have done so far before speaking to Virgin about getting another router.
The strange thing is, is that no other computers/cable tv box have been having any problems so I assume that if it was a router problem other problems with streaming T.V would also be evident.
Hi @RodS,
The good news is I can see your switch is unmanaged and should be acting as a passthrough. Ports go bad but cables are more often the culprits in my experience.
This is reflected in the logs. Aside from it being unable to connect to Roon’s servers with a no route to host error, the no route to host errors exists for it attempting to connect to your endpoints and remotes as well. It’s just dropping off the network.
Hopefully, this test with the Nucleus connected directly to the router will remedy things. The last error was May, 24 2:40 pm GMT.
Wes
1 Like