There was an issue loading your library - INNUOS ZENith MK3 Hi there,
I have a Innuos ZENith MK3 and the roon database keeps on crashing. Its the fourth time now within the last couple of month and I am tired of restoring from a backup. The log files have just been uploaded.
Describe your network setup
Router: avm fritzbox 7690 to switch: cisco ws-c2960cg to Innuos PhoenixNET switch to Innuos ZENith MK3 all cat wired.
From this, it sounds like the backup you used may have also unforatnutly be suffering from database corruption.
Do you have an older backup you’re able to test out? If your oldest backup still fails, you may have to start with a completely fresh database which is far from ideal.
Let me know if the above is possible - we’ll be on standby for your reply.
After reviewing your RoonServer logs, the issue is not directly caused by Roon itself, but rather by the storage setup on your Innuos ZENith MK3. Specifically:
Your log shows multiple entries like:
[broker/filebrowser/volumeattached] skipping /storage because it is not a removable drive
mountline: /dev/sda4 /storage ext4 rw,noatime,nodiratime,errors=remount-ro
This indicates that the /storage drive is being skipped because Roon treats it as non-removable, and the drive is mounted with the errors=remount-ro option.
The errors=remount-ro flag is a standard ext4 safety measure. It automatically remounts the drive in read-only mode if the filesystem detects errors. If the drive itself has issues, or if the Innuos software is not handling it correctly, the Roon database can become corrupted during read/write operations.
In plain terms: either the drive on your ZENith MK3 is experiencing filesystem problems, or the ZENith hardware/software is not reliably maintaining the database, which leads to repeated crashes and backup corruption.
Examples from your logs:
EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: errors=remount-ro
and repeated Roon messages about skipping /storage because it is not a removable drive.
Recommendation:
If you have an older backup stored elsewhere, try restoring from that.
If not, you may need to start with a fresh database on a known-good storage device. Because your existing backups may have latent corruption and lead to the same issue on the new drive.
Additionally, consider checking your ZENith’s drive health using Innuos tools or running fsck from a Linux environment.
This isn’t a Roon bug — it’s a storage/hardware issue that directly affects your database integrity.
Recommendation: