Highfalutintodd

This was exactly it. Followed the instructions and I'm back up and running. Thanks!

Updated to v4 and immediately getting: [Fatal] ConsoleApp: EPIC FAIL! [v4.0.0.741] NzbDrone.Common.Exceptions.SonarrStartupException: Sonarr failed to start: Error creating main database

Are there current best practices for this? I searched and found this from a post from several years ago on reformatting the cache: Is that still correct? thank you!

Posting here as recommended by Squid in Fix Common Problems More Info. My UnRaid setup has been running damn near perfectly for months if not years. Recently I was downloading a lot of seasons and a ton of episodes of old TV shows for my wife (via Overseerr / Sonarr / binhex-sabnzbd) when everything went haywire. binhex-sabnzbd started throwing a ton of errors and then Fix Common Problems showed the errors in the title, then all Dockers stopped working altogether. (As a note, I'm still on 6.11.5 simply because everything had been working beautifully and I just kept waiting until l had some time to update since something inevitably seems to break for me at each major .XX update.) Any help greatly appreciated! wordraid-diagnostics-20231101-1655.zip

EDIT / UPDATE (11/21/22): So, using Krusader, I changed the 'Group' and 'Others' permissions of the sonarr.db files from 'Can Only View' to 'Can View & Modify.' This is probably the exact wrong way to do it, but it worked and Sonarr seems to be up and running again. If I've done something horribly wrong that should be corrected immediately, someone please let me know. Otherwise since it's working I'm considering this closed. FYI and thanks! ORIGINAL: (TL;DR Same readonly database issue, but don't see a perms.txt and don't know how to fix) Hi - I hope someone will please take pity on me. I set up my UnRaid server a couple of years ago and really haven't thought about it since as it'a all just been working. So I've generally taken a hands-off, if it ain't broke don't fix it approach. I'd held off on updating from 6.9.2 for fear of breaking things until a couple of days ago when I finally updated to 6.11.3. Sure enough, things broke. Reading around, I found that the issues seemed to be the Docker / PUID / PGID issues that many had been reporting. In particular, binhex-sabnzbd didn't want to load. Changing from 99 / 100 to 1000 / 100 on binhex-sabnzbd (and only that Docker) seemed to do the trick and then all seemed to be going well - I did a test request through Overseerr of a movie which downloaded through Radarr / binhex-sabnzbd and then on to Plex so I thought all was well. Until I realized that Sonarr wasn't downloading anything. (IMPORTANT NOTE: JUST BECAUSE I'M THROWING THESE NUMBERS AROUND DOESN'T MEAN THAT I HAVE ANYTHING MORE THAN THE VAGUEST CLUE WHAT THEY MEAN BESIDES SOME GOOGLING!) I'm getting the same "[v3.0.9.1549] code = ReadOnly (8), message = System.Data.SQLite.SQLiteException (0x800017FF): attempt to write a readonly database attempt to write a readonly database" error, but changing from 99 / 100 to 1000 / 100 didn't help. Finding this thread I started looking for a perms.txt file and while I can find that file in other dockers (binhex-preclear, binhex-sabnzbd, nzbgetvpn), I don't see one in Sonarr. Please help - I'm not Linux-savvy enough to truly grok all the discussions around users / permissions and if I can't get this fixed my only recourse will be to restore back to 6.9.2 and hope that helps. THANK YOU IN ADVANCE!!!!!