Build 1538 seemingly causing nightly database corruption

Tinkering
1

I was running Room in docker fine for months. Upgraded from 1534 to 1538, and now I have corruption every single night. Roon works fine, then I want to use it in the morning and I have the restore prompt. I restore, all works fine again, only for the issue to repeat the next day.

Can anyone advise on how I can get Roon back on track? This kind of thing hasn’t happened to me in a decade of Plex.

And I know Roon does not officially support Docker. But it’s the only way I will run this and it has worked very well until now.

2

Hmmm, also running in docker (same version) and not seeing any issues. Not sure that helps. Maybe a failing hard drive? Are you doing a nightly backup that could cause corruption to be detected?

3

I think this is coincidence since my Podman container is working fine. Most likely, something else, i.e., HDD/SSD, is the cause of corruption.

Note that the Roon database (LevelDB) runs in memory and is written out to disk periodically.

1 Like
4

I’m running this Docker on an UnRaid system, so I know the drive is fine and tightly monitored.

The only other thing I did before this started was repair some SMB write permissions on all shares including the media and docker app data folder. But I only added, I didn’t remove or change any permissions.

5

This is now happening daily. Restoring the yesterday’s backup always works, until the next morning.

I’d really appreciate some assistance from Roon directly. Otherwise I’ll call my year 1 subscription sunk cost and just use Plex again. I loved Roon while it worked.

6

Those of us who use containers know that this is an unsupported configuration.

If you run a bare bones Roon server, restore a backup, and still see this issue, Roon will assist.

However, as already pointed out, the issue is most likely with your container, the host, or hardware. You appear to have ruled this out which is probably why the community hasn’t responded futher.

7

Update:

I installed the standard Linux Roon Server on a Ubuntu Server VM (minimal), mounted my host library and backup shares. Then restored library and remapped watch folder. It’s running significantly faster than the docker and hasn’t corrupted overnight.

Was my first UnRaid VM so a bit of a learning curve, but glad I did it.

8

This information would have been relevant upfront. Host > VM > Container is asking for problems, and should only be used for experiments or learning.

However, Host > Container works really well. I also have Roon server on the host, but have the Systemd service disabled; this is used purely for issue resolution.

Anyway, good to hear you are sorted now.

9

The container ran directly on the Unraid host. It worked fine for a few months, until it did no longer. Now Roon runs in a VM - and is much faster.