Server Version#: 1.40.2.8395
Running Windows 11 and since June 20th, every new update I’ve tried to install corrupts my database. I have to totally uninstall, delete all files, then reinstall to get it to work again. Any ideas of what the problem could be?
Keep in mind that server upgrades can include significant changes to the database schema. If your database is already corrupted (but still not bad enough so it’s obviously visible), this could cause more trouble while attempting to upgrade.
Also… rolling versions back and forth does not necessarily help in such a situation.
Have you already looked into repairing the database?
You might want to use the bat/ps1 scripts from this project to verify its status (and if possible fix it).
Thanks for the info! When it first corrupted, I did look into repairing and was able to find a script, but it didn’t work. I think I found it on a forum on here, didn’t use the one you linked on Github, so I will definitely try that. I guess I was rolling versions as a quick fix, thinking the next update would work, but it failed again. 
Also keep in mind that depending on various reasons, the database update can be really quick or take a bit of time. A big part of this is the size of your database based on number of media items you have throughout all your libraries. The bigger the size, the longer it will take to complete. If you are not being patient, you could be prematurely be stopping Plex while it is still doing the changes to do the rollback which can result in corruption.
-Shark2k
The corruption error shows immediately upon opening Plex, it doesn’t even attempt to scan, it just immediately says database is corrupt. I’m going to try the Github script mentioned in the other response and hope it works!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
