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)?
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 It will STILL then need to be formatted in the web admin interface to be useable with Roon.
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