· Something else
· None of the above
· Other
Roon Nucleus+ no longer starts, is no longer visible in the network
Rooter: Swisscom Box 3 / 2 x Netgear Lab Switches 10 Gb: XS708T / Lan Cable CAT 8 / Roon Nucleus+ con. to Switch 1 / QNAP NAS con. to Switch 2 in Büro: QNAP TVS-872XT
Roon Nucleus+ does not start and is not visible on the network
Short explanation 1:
Roon Nucleus+ (Roon Server version 2.0, build 1455)
All devices are connected to an internal 10 GB Ethernet network via 2 10 GB Netgear switches in the form of a bone division with CAT 8 Lan cabling,
i.e. on the 1st-10 GB Netgear switches (in Swisscom Rooter proximity) - system area
the Roon Nucleus+ and all other devices are connected,
on the 2nd-10 GB Netgear switches - office area
the QNAP NAS and the PCs are connected,
Process of switching off and on:
The entire technical system is de-energised at night,
i.e. all devices are shut down, put into standby or switched off beforehand.
The following sequence applies to the Roon Nucleus+, the QNAP NAS and the Swisscom Rooter (process has been in place for over 4 years):
(PC’s are excluded from this)
System switch-off sequence:
first manually switch off the other devices,
Roon Nucleus+, wait until shutdown is complete,
QNAP NAS, wait until shutdown is complete,
then switch off the power to the entire system,
incl. Swisscom Rooter and 2 x Netgear switches (have no switch).
System switch-on sequence:
incl. Swisscom Rooter and 2 x Netgear switches (do not have a switch).
QNAP NAS, wait until ready to start
Roon Nucleus+, wait until fully started
then all other devices are switched on
Correction:
Roon Nucleus+ just started, after approx. 2 h after pressing the illuminated start button on the Nucleus+.
During this approx. 2 h, the illuminated start button went out for a short time and then came back on again, this was repeated once a minute.
Is this normal for approx. 18 T albums (= approx. 200 T M. files), distributed over 4 x 8 TB Samsung SSDs in the QNAP NAS?
Many thanks and best regards
Michael Strickrodt (near Basel Switzerland)
.
Hi @Michael_Strickrodt ,
Thanks for reaching out and sorry to hear about the difficulties. A 2-hour startup time on Nucleus is very unexpected.
I’ve activated diagnostics mode for your Nucleus and what this does is upload a log set for review to our servers. Looking over this log, I am not seeing signs of hardware issues, there doesn’t appear to be any SSDs errors noted in the system diagnostic.
The RoonServer logs also look fairly normal, though there is a large amount of networking issues present. Also, in past cases, I’ve noticed the light turning on/off every minute is a symptom of a BIOS issue.
My first suggestion to you is to create a Backup of your Roon database and then try to perform an Operating System reinstall via the Web UI:
Then, if the issue is still present, can you confirm if the behavior is the same if the Nucleus is temporarily plugged into the main router, bypassing all the switches? This should tell us if the network is impacting the startup time.
Finally, if this still does not fully resolve the issue, please try to reset the Nucleus back to factory settings:
Let us know once you’ve had a chance to look into these suggestions and your results, thanks!
Dear Noris,
Thank you very much for your examination of my Roon Nucleus+ and for your suggestions.
I have made a backup of the Roon database and will now update it again.
However, I do not want to carry out a reinstallation,
as I am afraid that nothing will work anymore,
I am not an IT specialist, I am a retired mechanical engineer
and here in Switzerland nobody will help me,
as the sales company in Basel no longer exists.
About the Nucleus+ system:
Roon Nucleus+ startup problems I have had for about 1 year, since the album count exceeded 10 T.
The startup time of the Roon Nucleus+ increases continuously, but is sometimes shorter, < 1 h, sometimes < 40 minutes.
During the unsuccessful start phases, the Nucleus housing becomes quite warm to the touch at the top and I cannot see any entry with the IP login in the rooter setup,
the QNAP NAS also does not register any access to the SSD discs in the NAS.
In normal operation, when the Nucleus has network access, the Nucleus enclosure only gets slightly warm to the touch at the top and then works without any problems until it is switched off manually before the power is switched off.
In my opinion, the Roon Nucleus+ has a problem with the network login, or also with the Roon Lab feedback regarding authorisation.
The Roon Nucleus+ behaves as if the internet is not present,
although everything is there,
it should actually also start normally in the intranet and without the NAS,
so that it can then be used as a WEB radio,
but nothing works for a long time after a long start-up phase,
until it works again by itself, which is abnormal.
I don’t understand why it sometimes takes a very long time until it finally works, right up to manual switch-off using the illuminated button after approx. 15 hours.
Kind regards and many thanks
Michael Strickrodt (near Basel Switzerland)
Short addition:
So far, the network setting for the Roon Nucleus has been set to ‘DHCP’.
If a fixed IP address is specified here, isn’t that better?
Furthermore, the SMB setting on the QNAP NAS is currently set to 2 to 2.1,
Is SMB 3 now possible with Roon?
That should be normal today!
Many thanks and best regards
Michael Strickrodt ( near Basel Switzerland)
.
Just another user here, but I would suggest restarting the Nucleus+ with the NAS storage locations disabled to see if it is the Nucleus+ or the size of the “library/network load” that is the cause.
Are all the drives you mentioned listed under one entry in Roon under “Settings/storage”? You might try disabling them individually, if they are separately listed, to see if one of the locations is the cause? Or if, like you said, it is once you reach a certain library size limit that the issues starts happening.
P.S. Retired ME here too. But I am also a geek and have installed networks and built/repaired computers for friends and families… Cheers
No it’s not, generally speaking
Dear BearFNF,
The problem here is that the Roon Nucleus+ is not logging into the network.
I can see this via the monitoring of the Swisscom Rooter and the monitoring of the QNAP NAS.
On the QNAP NAS, you can even follow the individual phases of the Roon Nucleus+ boot processes in a data transfer diagram that is displayed over time.
It is definitely the Roon Nucleus that is not dialling into the network, or not dialling in correctly. This dialling-in process is repeatedly cancelled and restarted,
This can be recognised by the light button of the Nucleus+, the button light goes off and on again briefly once a minute, up to one to two hours today.
The SSD discs in the QNAP NAS are all listed individually in Roon and are precisely monitored by the QNAP software. The SSD discs are all OK.
The Roon Nucleus simply does not want to dial into the one internal network
and then, after about 2 hours, it does work, which is a paradox!
It’s a problem with the Roon Nucleus that Roon Lab needs to fix,
via firmware and software update.
Many thanks for your suggestions and best regards
Michael (near Basel Switzerland)
.
Addendum to BearFNF,
after about 2 hours of own login attempts from the Roon Nucleus+ itself, it now works without any problems.
Tomorrow morning there will be problems again, until about 10:30 / 11:30 am,
then the login from the Roon Nucleus will work, like yesterday and today, after about 2 hours.
Does this have something to do with the authorisation of the Lifetime Abbo?
I don’t think so, but it’s certainly strange!
Best regards
Michael
.
Dear Suedkiez,
I have no experience in this regard,
but with a fixed IP address I was able to fix
a printer problem in the internal network.
Kind regards
Michael
.
This indicates that a network problem existed to begin with, that had to be worked around. DHCP just works in any healthy consumer network and has done so for decades. Though it’s possible that a particular printer model had a broken DHCP.
On balance, there are far more problems caused by people setting static IPs and then forgetting about them and causing IP collisions than there are problems caused by DHCP.
Thanks for sharing your reports, but it’s unclear if you’ve tested any of the previously suggested troubleshooting steps. Unfortunately this issue is likely tied to your specific device and isn’t something affecting other devices. I’ll re-list the steps still needing testing:
I’m sorry about your situation locally in that the sales company is no longer available as an additional resource. Let us know the results above. 
Dear Noris, dear Benjamin, dear BearFNF,
Is it a miracle? Are there any miracles at all? What is a miracle?
The Roon Nucleus+ started and worked perfectly today!
What did I do yesterday?
by means of ‘Power Off’,
until now I used the illuminated push button on the Nucleus.
What did I do this morning?
started the network (incl. Swisscom Rooter plus 2 x Netgear switches)
removed the Roon Nucleus+ from the installation system
and removed the 4 TB Samsung SSD that was still installed there but deactivated, then reinstalled and connected the Roon Nucleus+ to the plant system
At 8:55 a.m., the illuminated push-button on the Nucleus briefly switched off and on again,
this happened about 3 to 5 times.
At approx. 9:02 a.m. Roon started, visible on the tablet by the Roon symbol.
Roon could be used at approx. 9:06 am.
First I tried the WEB-Radio, → it worked.
A blue three-quarter circle was visible on the tablet in the Roon programme at the top right for approx. 1 minute.
The second step was to start the music from the QNAP NAS → it worked.
It is very strange that now, today from about 9:00 am (Basel time) everything works again as before,
after approx. 13 minutes after pressing the light button on the Nucleus, no more extremely long waiting times.
Speculation remains,
a) e.g. switching off the Roon Nucleus+ via the IP menu, see item 1 above,
the Roon Nucleus+ may not have shut down completely and is hanging.
b) the removal of the internal SSD, which was deactivated and no longer read out, see item 3 above;
c) does the 4 TB SSD connected to the Roon Nucleus+, which was deactivated, have a defect?
The 4 TB SSD is still being tested for function
d) The fact that the Roon Nucleus+ was unable to dial into the network was rectified, by whom?
Did the authorisation via the Roon Lab server now work better and faster?
What really happened?
There will be another test,
that runs exactly as before, before this test,
then we can continue to speculate.
Best regards and many thanks to all of you who have contributed here.
Michael (from near Basel, Switzerland)
.
Hey @Michael_Strickrodt,
I’m glad to hear you were able to get things performing properly! We didn’t push anything on our end, not to your device specifically at least.
There was an update that became available earlier today, did you by chance also update your Nucleus in your testing?
Outside of that, let me know how the next 24 hours feel. We’ll be on standby for your response!
Dear community, dear Benjamin,
yes, my / this Roon Nucleus+ has also received the new update today, Thu.19.Sep.2024, approx. 21:15:
Roon Nucleus+ (Roon Server Version 2.0, build 1462)
Best regards
Michael
.
Dear community,
dear Benjamin, dear Noris, dear BearFNF,
here is a test repetition after the Roon update for Roon Nucleus+
(Roon Server Version 2.0, build 1462).
by means of ‘Power Off’,
this morning, Friday, the network (incl. Swisscom Rooter plus 2 x Netgear switches) was started up
at 8:31 am (Basel time) the Roon Nucleus+ was switched on:
At 8:32 a.m. the illuminated pushbutton on the Nucleus briefly switched off and on again,
this happened 5 times until 8:36 a.m,
about 5 minutes for unsuccessful network access.
At 8:38 a.m. Roon started, visible on the tablet by the Roon symbol.
At 8.45 a.m. Roon could be operated.
at 8:46 QNAP NAS switched on, startup time as usual approx. 3.5 minutes, which is normal.
at 8:50, QNAP NAS is ready
System consisting of Roon Nucleus+ and QNAP NAS can now be used and is working.
A blue three-quarter circle was visible on the tablet in the Roon programme at the top right for approx. 1 minute.
It should be noted,
or a reboot in each case.
every modern laptop is ready for operation after < 2 minutes!
The light button on the Nucleus going out and coming back on again indicates a possible bios problem, as other users have already discovered here!
This is where Roon Lab comes in.
Others in the community are also affected by the problem described above:
Roon Nucleus not communicating with network since yesterday (ref#W8MX5K)
‘Waiting for your Roon Server’ message
Nucleus+ server not found and turning off every 60 seconds (ref#WNWN3U)
…
This also applies to my problem case.
I think there are more who have the same or a similar problem as me, which was just described slightly differently in the headline.
The light button on the Nucleus going out and coming back on indicates a problem that others in the community are having.
If this is a Roon Nucleus Bios problem, then Roon Lab must solve this problem
and not force a user with further tests, as this problem is known to Roon Lab.
I will do a test with the original test sequence.
I have one important request for Roon Lab,
please do not perform a factory reset on my Nucleus+!
Best regards and have a nice weekend with a working Roon Nucleus
Michael (near Basel, Switzerland)
.
Hey @Michael_Strickrodt,
When there’s a BIOS issue, there’s usually evidence of an error in the Nucleus logs. In your case, we’re not seeing any issues related to the BIOS. Users also aren’t usually able to get out of this constant restarting state.
We’re seeing reoccurring network-related errors, but these errors don’t point at the Nucleus specifically, but rather the connection between your network and the Nucleus:
System.Net.Sockets.SocketException (101): Network is unreachable
I’d test out bypassing all your network gear, and get a stable ethernet connection to the Nucleus directly to your router, even using a more basic CAT cable. That may help increase network speeds.
This isn’t something we can do on our end, so nothing to worry about there.
Let me know how things perform with a more simplified network!
Dear Benjamin,
Thank you very much for your feedback, your help and for checking my Roon Nucleus+.
Now I can get a much better night’s sleep.
Here is another test,
the Roon Nucleus+ is now outside the internal 10 Gbit network,
connected directly to the Swisscom router :
yesterday evening, Friday, the Roon Nucleus+ was shut down using the illuminated power button,
this morning, Saturday, the network (incl. Swisscom Rooter plus 2 x Netgear switches) was started up,
at 7:50 a.m. (Basel time) the Roon Nucleus+ was switched on
At 7:52 a.m., the illuminated pushbutton on the Nucleus briefly switched off and on again,
this happened 5 times until 7:57 a.m,
about 5 minutes for unsuccessful network access.
At 7:58 a.m. Roon started, visible on the tablet by the Roon symbol.
At 8:06 a.m. Roon could be operated, approx. 16 minutes after switching on.
at 8:07 QNAP NAS switched on, start-up time as usual approx. 3.5 minutes, which is normal.
at 8:11, QNAP NAS is ready
System consisting of Roon Nucleus+ and QNAP NAS can now be used and is working.
A rotating blue three-quarter circle was visible on the tablet in the Roon programme at the top right for approx. 1 minute.
There is no difference.
The reactions of the Roon Nucleus+ and its duration until it is fully operational are the same as in the previous test, where the Roon Nucleus+ was connected within the 10 Gbit network to the 1st Netgear switch in the system area.
For your information,
the Swisscom Rooter has 4 x 1 Gbit Ethernet Lan connections
and 1 x 2.5 Gbit Ethernet Lan connection, the 1st Netgear switch is connected here.
The QNAP NAS has 2 x 10 Gbit Ethernet LAN connections.
There is 25 metres of Ethernet LAN CAT 8 cabling between the two Netgear switches.
All streaming devices are connected to the 1st Netgear switch (system area)
and the QNAP NAS is connected with various PCs to the 2nd Netgear switch (office area).
The 10 Gbit Lan network was set up to avoid possible ‘network bottle necks’ with regard to Hi Res data transmission.
The Roon Nucleus+ retrieves the data from the QNAP NAS via Ethernet Lan connection
and then passes processed data via USB connection to a Meitner MA3, which converts the digital data and passes it analogue to a preamplifier.
Questions:
Does the Roon Nucleus+ now support Windows connection type SMB 3 protocol?
Does the Roon Nucleus also work with Windows connection type Samba?
The Roon app on the iOS tablet consumes an incredible amount of battery resources, is there a corresponding update?
Where can I buy a Roon Nucleus Titan in Germany and Switzerland?
Many thanks for your help and support, have a nice weekend
Michael
.
I can answer some of those until Roon support is back after the weekend:
@Suedkiez did a great job answering your questions. Based on your last few posts, it’s hard to tell if the Nucleus is still taking more than a few minutes to boot up?
Are you still having issues at this point? If anything, perhaps further investigation of your QNAP may help increase start-up times.
Let me know!