Intermittent Library Inconsistency on Linux Server Requires Roon Server Restart (ref#NFAMLF)

Support
1

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Trouble creating or restoring backups

Tell us what's going on

· Hello Roon, imusing run for several years running on a Linux Server since December I started to experience problems regarding the library. Am I fall out your instructions and tried different approaches like restoring the whole run Server directory from a backup and of course restoring darun backups themselves I was hoping the issue with the consistency of the library would go away as I apply the roon server updates. Currently I'm solving the inconsistent library issues by simply restarting the rune server which solves the problem but only for a while
. Please advice how to get this fixed. Rgds kai

Tell us about your home network

· Linux Server, Music Data on Synology, Tidal,

2

Please see:

Note:

So this solves nothing then. It is, by design, a temporary workaround to let users access their library (if possible) until they have time / knowledge to fix the issue actually.

3

Thanks, please advice on the steps to get the library fixed. It contains approx 8000 Albums, approx 3000 as files and 5000 via Tidal. Rgds kai

4

Steps are in the linked Guide. In short, there is no repair option for a corrupted database. You either have a good backup or you have to start all over fresh. The most important thing though is to make sure your hardware is still in good shape and not the cause of the corruption.

5

Hello @kkaaii,

Thank you for the detailed description. Based on what you are experiencing — library inconsistency that temporarily resolves after a restart — this is consistent with low-level database corruption. This can happen due to a failing drive, unstable power, or filesystem issues on your Linux server.

Here is what we recommend:

  1. Stop Roon Server on your Linux machine
  2. Navigate to your [url=https://help.roonlabs.com/portal/en/kb/articles/database-location]Roon database location[/url] — typically ~/var/roon/RoonServer
  3. Rename the RoonServer folder to RoonServer_old
  4. Restart Roon Server — it will generate a fresh database
  5. On your Roon Remote, press "Use another Roon Server" and connect to the new database
  6. Restore from a backup taken before the issues started via Settings → Backups → Restore
If the restored database loads cleanly and remains stable, the issue should be resolved.

Before doing this, we also recommend checking the health of the drive where your Roon database lives — run smartctl -a /dev/sdX to check for any SMART errors that could indicate a failing drive causing the corruption.

If you do not have a usable backup, unfortunately a fresh start is the only option, though your local file tags and Tidal library will be intact.

6

Hi @kkaaii,

If there are external factors contributing to the corruption (like a failing hardware component or a problem with the underlying track files), then it’s not unreasonable to expect symptoms to return.

We wanted to reach out before this thread auto-closed due to inactivity to see if you’d had any problems on the new database.

Can you please share a screenshot illustrating any inconsistencies you see with your library count in Roon, if so?

7

I have deleted the library and restored a backup. The inconsistency appears to be fixed now since also RoonArc is able to sync again (which previously led to crashes due to the library issue).
Can be closed - Thx