I’m using a Roon Nucleus with an internal SSD that contains my ripped CD collection.
The internal storage was visible and in use before. While troubleshooting missing albums, I deactivated the internal storage in Roon and rebooted the Core.
Since then, the Nucleus web interface shows: Internal Storage: Not Ready
The Nucleus boots normally and immediately, but the internal SSD no longer mounts and is not available as a storage location in Roon.
I have not formatted, repaired, or re-initialized the drive and have not removed the SSD.
I would like to recover the internal storage and the music data if possible, and would appreciate guidance on safe recovery steps.
Please let me know if you need logs or additional information.
Thank you for your help.
Tell us about your home network
· no vpn , silent angel switch,router from my local system meo everything including the nucleus worked fine before
We’ve reviewed the diagnostics from your Nucleus, and here’s what we’re seeing:
The internal system SSD (NVMe) is detected and mounted normally.
The internal music SSD is detected by the system (/dev/sda is present), however it is failing to mount.
The system logs show repeated SATA I/O and CRC errors on that drive, including link resets, read failures, and the drive being temporarily disabled by the controller.
Because of these low-level I/O errors, the OS is unable to safely mount the filesystem, which is why the Web UI reports “Internal Storage: Not Ready”.
Importantly, this behavior is not caused by deactivating the storage in Roon. Deactivation only removes the location from Roon’s configuration and does not affect the disk itself. The timing here is coincidental.
At this point, the issue is below the Roon application layer and points to a hardware-level problem involving the internal SSD or its SATA connection (for example the drive itself, cabling, or power stability).
To protect your data, we do not recommend formatting or attempting repairs on the Nucleus at this stage.
The safest recovery path is:
Remove the internal SSD and connect it to another computer (direct SATA or a reliable USB-to-SATA adapter) to check whether the data is readable.
If the drive is readable externally, your music can be copied off before deciding next steps.
If you’d like, we can also advise on replacement options for the internal drive once your data is secured.
Just to reiterate, we recommend connecting the drive to another PC or computer via SATA (or USB-SATA) and seeing if you can access the files.
A useful first step would be to simply copy the music files to another location (like a network share or even a USB drive) so you can access them while you troubleshoot the SSD.
Let us know if you’re able to see the files in a file viewer on another computer and we’ll be able to proceed from there.
We’re pinging this thread since we haven’t seen a response.
Ultimately, we need to try to determine whether this drive is still physically healthy. The low-level I/O errors we see in system logs show that the mounting problems are at the level of the operating system.
The most expedient test is to see if another operating system can successfully mount the same drive. You’ll likely need a SATA-USB cable in order to test this using a PC/Mac. If the drive is readable, you can at least save your music to a separate location.
We’re of course here to assist with the particulars of this process should you have any questions. Keep in mind, however, that this thread will close automatically after a few days if we don’t receive any further responses from the OP.
This thread is now closing due to inactivity/lack of response. You can reactivate the conversation by simply submitting a new tech support request here if you require additional support.