permster

I don't know all that much about Jellyfin. I run the container but don't use it. Doing some googling I found this post here that talks about repairing a corrupt DB. Sorry I can't be of more help.

@cattledog I know there are ways to repair SQLite db's that have been mentioned previously on this thread but I don't know of anything specific to Jellyfin. Best case would be to restore from a recent backup if possible. I actually just had this issue come back again in Sonarr this morning after quite a few months of no issues. I don't believe it's related to the Appdata Backup or the CA Auto Update Applications plugins. Those are scheduled and run at completely different times of the week that don't match up (at all) with when this latest corruption occurred. I see old forum posts talking about the Direct IO tunable and another thread mentioning the mdcmd set md_restrict 1 command but I think that fix was already rolled into a previous Unraid version. Not real sure where to go from here. Doesn't seem to be any end in sight. Unraid version: 6.12.14 Sonarr container: lscr.io/linuxserver/sonarr

I don't have a solution yet but I did add some monitoring for this issue recently. Hope this helps others. The below script leverages the User Scripts plugin so if your not familiar read up and install it first. It also uses the sqlite3 command line tool which I think may be built into Unraid but I'm not 100% sure on that. It was already installed for me. Set *arr backups to daily instead of weekly. (only needed so your not losing as much on restore) Settings > General > Backups Change the Interval to 1 days. Be sure to click the 'Show Advanced' button at the top or the "Backups" section won't be visible. Create an Unraid User Script that checks the Sonarr logs.db file for database corruption. #!/bin/bash result=$(sqlite3 /mnt/user/appdata/sonarr/logs.db "SELECT Count(*) FROM Logs WHERE Message LIKE '%database disk image is malformed%' AND Time >= datetime('now','-4 hours');") if [[ $result -gt 3 ]] then echo "Database corruption detected, sending notification" /usr/local/emhttp/webGui/scripts/notify -s "Sonarr corruption" -i "alert" -m "Please attempt to restore Sonarr from a known good backup! Don't forget to add any shows that were added since the backup." -d "Sonarr database corruption detected!" else echo "No corruption detected" fi With a Custom cron schedule to run every 4 hours (example below). 38 */4 * * * Feel free to adjust the script for you needs. It is easy to adapt this to radarr by changing the path to the logs.db file and then adjusting the echo and notify strings. You can change the schedule as well if you think every 4 hours is too aggressive. Adjust your User Script schedule accordingly. Adjust the SELECT statement in the script which is currently set to look back 4 hours. datetime('now','-4 hours')

This issue stopped for a month or more but just happened again in Sonarr last week. I still don't know how to fix this as putting the *arr appdata on a single disk seems silly to me. When you say "rebuilt again" it sounds a bit worse than it seems. For most people that aren't constantly changing things all you have to do is restore from the last good backup and your good to go. Before restoring I go check to make sure there aren't any newly added series or movies since the corruption occurred. Those need to be added back after the restore. One thing that might help recovery is to change the backup frequency and retention under Settings > General > Backups which by default is only every 7 days I believe. Does anyone know of a good way to monitor for this issue? The built-in health alerts in Settings > Connect don't catch this. I tried Notifiarr which supposedly monitors for database corruption but wasn't alerted. If I can't find anything I'll probably just write some python code to monitor the logs.db for the issue.

Same issue here but only impacting sonarr, no other containers have issues. Been running fine for a year and a half. The issue just started a few weeks ago but has corrupted the DB multiple times since. May be related to the below post which I also replied to earlier but still don't have a solution. Let me know how it goes on a single disk. I may have to go that route eventually as well if this gets much worse.

I also started having issues just recently with Sonarr database corruption. I can restore from backup and all is fine but then it corrupts again a day or two later. Just this morning I saw all the disk I/O errors in the Sonarr events. My appdata share is set to Primary > Cache and Secondary > Array with mover action set to Array > Cache so I'm not set to cache only but I'm still experiencing the same issue. No other containers have this issue that I'm aware of. Are there any other ways to troubleshoot this issue? I see nothing in syslog when these issues are occurring in the Sonarr container. Unraid - 6.12.9 Sonarr - 4.0.4.1491 Database - Sqlite 3.44.2