For me it has only happened twice where I had to wipe my whole DB and start over. The 75% was where I either unplugged the computer as if power was lost which is a problem where I live in the winter or I just powered down from the power button on the PC with out shutting down Drone properly. I tested 6 times and 4 of them resulted in the error and I grouped the other 2 in making 6/8 erring for me. It seems strange to me that I woulds get it to error that often and I wish it wasn’t the case because I really like to software and would love to be using it again for my day to day stuff.
Attempt to start NzbDrone.exe, if it works you won’t lose everything and it will just start normally. I prefer doing the mv command as it just changes the filename so if you need to access it again you just name it back to its original name.
I started to setup last night on OS X 10.10.2 and had a failure. This is something specific to sonarr and OS X. I see reports of it all over the net and several threads here about it not starting unless you remove and install again. That isnt a acceptable solution. I want to get away from sickbeard and this isnt making a very good case for it.
is anything being done to look more at this problem?
I should of cleared that up. Yes different situation but with same result. The DB file in .config/NZBdrone gets corrupted on a reboot if you launch it using the drag and drop OS X application. I have wiped it out and installed the terminal version of the application. I can run it using mono nzbdrone.exe with no problem.
Just wanted to report it is something in the app causing this corruption it seems.
Was just about to report I got corruption again this morning even using the terminal version of Sonarr and a plist auto start after a reboot. It wasnt immediate however like when using the drag and drop app.
I’ll hold off on a solution before attempting to set up again. Thanks for the feedback.
Thanks for the tip. I just restarted my MBA and had the EPIC FAIL message. Restoring nzbdrone.db did not fix it since it was logs.db that was corrupt. Deleted and started sonarr, works fine now.