Zakire

Isn't that what we have all been doing with the repair commands? Legit question, because I don't know if your method does something else. After repair, *arr is working fine for weeks, sometime months, before it gets corrupted again.

I'm not running any backup script at all (although I have had it on my to-do list for far too long), and it happens to me every now and then (about once or twice a month). I have lived with this problem for years. No update what so ever of either Unraid neither any of the *arr applications have solved it. Haven't upgraded to Unraid 7 yet though.

I've actually managed to get rid of the corruption. Not totally sure if it was an update or something I did. Although, last time I did a repair, I decided to delete the logs.db after the repair. Haven't had a single corruption in several months now. Not in Radarr, nor in Sonarr (previously had a corruption like every week on both systems).

I'm running Sonarr and Radarr on a single SSD. Although it's configured as a cache drive (without any data movement), so it might not be completely single and outside of all the Unraid stuff anyway?

I have the same issue and have had so for a long time (not sure how long, a year maybe). I don't have any backup solution in place. Both my Sonnar and Radarr databases keeps corrupting like once a week. I repair and restart, and all is fine for about a week or maybe two. The databases resides on an SSD drive configured as cache, without any data movement. What's on the cache SSD always stays there. I have googled the s**t out of it and it seems like only Unraid users have those problems.