I came home today and found that drone stopped working. I tried restarting and rebooting but I keep getting a windows error: 1053.
Any ideas?
I tried the backup/restore as per the wiki but same error message. It only works as a new install, so does that mean that the db is damaged?
Please, say it ain’t so. 
Shedrock
Check your logs to be sure, but it sounds like its corrupt. The FAQ has a link to a guide to recover as much as possible from the DB if it is corrupt: https://github.com/NzbDrone/NzbDrone/wiki/FAQ#wiki-database-disk-image-is-malformed
I don’t know what to look for in the DB. I also don’t understand those instructions.
Also, why would the DB become corrupt? Wouldn’t this always be an issue then?
I had a back of NzbDrone Ver. 2.0.0.1022. Would this automatically updated to the latest develop branch. I tried it manually but it keeps failing.
I am still getting the same error with the old DB.
You don’t have to look for anything in the DB, the guide covers how to copy the data out of the corrupt db into a new one.
Could become corrupt for various reasons, power loss, disk corruption. I don’t see how it would always be an issue. There is always a chance it becomes corrupt, but not always will it be corrupt/corrupted.
Check your logs: C:\\ProgramData\zbDrone to see what the error is, new database with old version won’t work for various reasons.
I reinstalled drone from scratch and added about 150 series. I left drone idle for 20 mins, came back to the PC and the service has stopped. Tried restarting and I get the same windows error.
This is frustrating. I am at a lost and have no idea why this is happening.
Maybe the bottom of the attached log may shed some light for you?
I tried drone on 2 other machines, which coincidentally were both updated to the latest branch. This is the problem from what I can see. I had ND on both machines before and I had no issues.
I could be wrong, but it is strange only when it got updated that I get this error.
I reinstalled everything again but this time I set it to the ‘master’ branch and it seems to be working okay so far.
It a DB migration issue with the latest develop release. Working on a fix.
Comes with the territory of being on develop. Had you looked at your logs or posted them as you did, you could have saved some time and a lot of posts (use edit next time).
For someone who does have the same issue and hasn’t deleted their old DB, is there a quick fix or wait for your fix?
My logs are almost identical to shedrock’s bar timestamps and yes, I am on the develop branch. Would a switch back to master solve this?
Apologies for necro’ing the other thread, it seemed to be the closest in a google search.
Fixed now, you will need to manually update from to the latest release, steps are here: https://github.com/NzbDrone/NzbDrone/wiki/Recovering-from-a-Failed-Update
It was a migration issue, the migrations were taking minutes (mine was bout 3:23) instead of seconds, due to a poor design of one of them, switching branches wouldn’t resolve the issue since the DB was halfway through when Windows terminated it (switching branches with a failed migration would never really work).
I’ve tested this latest release on a couple DBs and its able to resolve the issue (added some extra checks) and does it within a couple seconds.
Please let us know if you continue to have issues after updating to 2.0.0.1100.
Awesome! Solved the issue for me, now back up and running 