Endless starting loop after implementing internal SATA SSD to Nucleus

Roon Core Machine

Networking Gear & Setup Details

Connected Audio Devices

Number of Tracks in Library

Approx. 25,000 tracks

Description of Issue

Story starts after the latest Roon Update in November.
My Nucleus Plus dissapeared out of my Network.
I send it to my dealer (in Germany) and they send it to an Nucleus Repair Service.
The Nucleus Repair Service changed the internal M.2 NVMe SSD.

Now Nucleus boots, gets an IP and the Core is working.

BUT if I add my internal SATA SSD (to add my music), then Nucleus is doing an endless starting loop.

I assume (no idea with Linux OS), that the booting sequence is wrong set.

It should boot with the M.2 NVMe SSD where the Core is installed, but it is searching on the SATA SSD for the Core - can not find it and repeats booting …

I already checked the SATA SSD (Samsung 970) formated in NTFS. If I connect it to my Windows Notebook via USB/ SATA Adapter, then it is shown as normal drive.

Is it possible to change the booting sequence of Nucleus (if this could be a possible case)?

Best Regards
Hubert

You need to format the drive from the web interface.

Screenshot 2022-12-11 at 21.32.36

No, @mikeb - there’s a problem with the boot sequence. That needs to be addressed first.

What you can try is formatting the SSD as exFAT using Windows, to see if that helps with the boot issue…

1 Like

Ok, so connect a monitor + keyboard, and hit delete to get into the BIOS, then correct the boot sequence. I have never seen this being necessary for a Nucleus, and I presume the Samsung SSD is not bootable, but re-formatting it to ex-Fat on a PC will fix that :slight_smile: It will STILL then need to be formatted in the web admin interface to be useable with Roon.

Thank you for the fast feedback.
I will try it again with the exFAT format.

Just to clarify:
The first internal M.2 NVMe has the OS on. It is a Kingston.

The second internal SATA SSD is Samsung and it‘s only ment to store music files.

I added a picture.

It is just very strange, because I used the same SATA SSD before the problems after the update started in November.

When I disconnect it (I mean the Samsung) in Nucleus, then Nucleus is booting in Roon Core as it should.

If I connect the SATA SSD (Samsung ) then Nucleus starts with booting loops - no IP address so no possibity to format the drive via web interface…

If exFAT will not help, then I will try to set the boot sequence in Nucleus it‘s BIOS.

I will let you know…

1 Like

This doesn’t make any sense…
The internal storage of a ROCK server will need to be initialized from the GUI before it is usable. And it will be formatted using EXT4FS, not the claimed NTFS…
So, something has happened to this drive while out of the Nucleus, or it is another drive. And i agree with MikeB, if the drive is cleaned, there will be no active partitions and no boot issues.

You need to access the bios settings in the Nuc and set the m.2 ssd as the first boot device. It most probably got reset when they serviced the Nuc. If it had music and was working in the Nuc before as a SATA drive you might not have to format it again, but the issue sounds like it’s trying to boot off of SATA and not m.2

2 Likes

The solutions did not work.

I formated the Samsung SATA SSD to exFAT format.

Before implementing it I opened BIOS and it looks like this:

I went out of BIOS without saving because there was only the Kingstons M.2 NVMe connected with the Roon OS.

Hardware looks like this:

Even just by going in and out of BIOS my Nucleus got into this endless starting and shutdown loop.

I could only get it started and back into my Network by disconnecting the electricity for approx 20 Minutes…

Then I disconnected electricity and LAN and implentented the SATA Samsung SSD.

Connected the Electricity and LAN , pressed the start button and the endless starting/ shutdown loop began again.

I took Nucleus another 20 minutes from electricity and tryed to get into BIOS during restart with F2.

Didn‘ t get so far, due to that even my USB attached keyboard have been ignored during system boot.

And again the endless boot/ shutdown loops started.

Really don‘t know how to continue…

The next thing I would do is to try a different SSD as a test; doesn’t have to be the same size.

Can you try it with a different PSU (after trying another SSD)? Maybe the extra load of the SSD is causing power issues?

Thank you for the fast feedback.
I already tryed another SATA SSD with 250 GB.

Same Probleme appeared.

Nucleus started to do endless Boot/ shutdown loops…

Don‘ t think it is the SATA SSD itself. They work priiy good on my Windows Notebook.

What shows on the hdmi port if you connect a monitor to the Nuc while it’s booting up?

Hi, finally I gave up and send it to my dealer for repairing. Lets see what they fix this time…

In the end, Nucleus was going into this endless booting loops. HDMI seems in this state not been activated.
There was nothing shown on my monitor….

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.