· Scheduled ROCK database backup fails. ROCK: Version 2.1 (build 271) production - Server: Version 2.65 (build 1653) production - Manual backup attempt also fails. After failure, Roon client shows: There was an issue loading your library. Only way to get client working again is to re-boot ROCK server. This lasts for a day or so and then again client displays same "There was an issue loading your library". Another re-boot and same issues above repeat.
Renamed old folder as suggested and re-started server. Let it run for almost 8 hours and attempted new backup. As soon as backup started, Roon remote displayed: “Uh oh, something’s not right” Make sure Roon server is turned on…. Roon remote then displayed: “Waiting for your Roon server”. After several minutes, I restarted the server and the remote responded again. Still cannot perform a backup, and since I do not have a backup there is nothing to restore. Anything else I can try?
The repeated database loading errors, the inability to complete a backup on a fresh database, and the entire server locking up strongly indicate a hardware failure. In our experience, these are classic symptoms of the primary M.2 SSD (which houses the ROCK operating system and your database) failing. When Roon attempts a disk-intensive task, the failing drive likely drops offline, causing the server to crash.
Before purchasing a replacement drive, you can verify the health of your current SSD to be absolutely certain. Since ROCK is a closed operating system without built-in disk diagnostic tools for users, you can test the drive using one of the following methods:
Method 1: Use a Live Linux USB (No disassembly required)
Create a bootable USB drive with Ubuntu desktop (or another Linux distribution).
Plug the USB into your NUC, enter the BIOS, and boot from the USB drive.
Once in the Ubuntu desktop, open the “Disks” utility.
Select your internal M.2 SSD and check the “SMART Data & Self-Tests” section for any reported errors, bad sectors, or pre-fail warnings.
Method 2: Test on another PC
Open the NUC and carefully remove the M.2 SSD.
Place the SSD into a USB M.2 enclosure, or plug it directly into a spare slot on a Windows or Mac computer.
Use a disk diagnostic tool (like CrystalDiskInfo for Windows or DriveDx for Mac) to read the SMART health status of the drive.
If the tests confirm the drive is failing or dead, you will need to replace the SSD, perform a fresh ROCK installation, and start with a new database.
Let us know if you are able to run these tests or if you have any questions about the process!
I followed Method 1 above. Disk appears to be okay from the test results. I have uploaded 4 screenshots from the “Disks” screen. It looks like Roon OS/boot is on the 512GB SSD and the 512 NVME is formatted as Roon storage. Let me know if you see any issues. Sorry for the blurry screenshots. Computer is a Beelink Mini S w/16GB memory.
Thanks for the update! From a fresh server diagnostic report, we see the backup subsystem initializes cleanly on startup ([broker/backups] initializing) and the network share at \192.168.8.230\backups mounts successfully over CIFS. There are no backup errors, failures, or abort events anywhere in the fresh report. The backup appears to have been working normally throughout the last few days.
Overall, things look stable. No backup errors, no database loading failures, no server crashes in this log set. Let us know how the next few days go
The backups appear to be working. I noticed that the server re-starts every few days. Music was playing earlier when all of a sudden it stops and I get the “Uh oh, something’s not right” message. Checking ROCK says server is not running. A few minutes later, it is running again. Is there any way to see what is causing the server to re-start?
Thanks for the update. The backups appear to be working, but the server restarts every few days and briefly stops playback with the “Uh oh, something’s not right” message.
Please let us know the exact local date and time the message next occurs and we will enable diagnostics. That will help us narrow down what is triggering the restart.
