I already uploades my logs.
In this thread? I donāt see them.
In another thread. Iāll do another
Iām rebuilding my library, i can get them for you by 6am my time. Iāll post them here.
Iāve downgraded to 1.25.8.5663 after uninstalling a dev build 1.26.1 that I was cordially invited to participate, installing PlexMediaServer-1.26.0.5715-8cf78dab3-x86, and uninstalling that. Quite a PITA, but I seem to be ok on Windows 10. You should have these available in [AppData\Local\Plex Media Server\Updates].
I found your other post. It looks like you rolled back quite a few versions?
Apr 13, 2022 10:29:03.559 [5172] ERROR - Migrations: Attempting to run both down and up migrations simultaneously, something weird happened.
Thatās very strange.
Do you remember the order you tried things in - what versions of PMS you went through?
My guess is that a migration was either cancelled/interrupted/crashed (Plex can take a few minutes to perform some of the larger migrations). Or there was a preexisting problem with the database files, and the migrations revealed that issue. Things can work āfineā on a broken database file for a long time, but attempting to modify broken areas will then cause issues.
I agree, I donāt have any remote guesses how to help after that error. Iām hoping the Plex devs see this one and look at your logs (and ask for your databases).
1 Like
I had the database migration issue as soon as i installed 1.26. I initially went back to the version I was using. Then i tried opening my OG backup 09.16 (best version ever!!!) and saw it was completely missing. Thats when i looked at the database and tried 1.25 etc.
If you have a backup from 1.25.x, before 1.26.x, I would try to repair that database. It would be interesting to see what the PRAGMA integrity_check reports.
If youāre already rebuilding, thatās probably easier ā¦ but obviously painful for different reasons.
Ugh. Good luck.
1 Like
Apparently my logs show a skipped 1.25. So i have nothing from that build.
I am able to use the old web UI from a previous version (09.16) and that is rebuilding my library and database. 1.26 and the new UI is doing funny things to my setup.
I can confirm there is something seriously wrong with the 1.26 upgrade. My DB corrupted as well and following the DB repair instructions didnāt work despite having backups.
In the end, I had to replace my plex install with one off my incremental system backups.
Confirmed that I repaired everything and that Plex was working with the restore. Then I tried to install 1.26 again and it immediately corrupted my DB again.
Iām now in the process of pulling the incremental back up again to get back into a working state. Wasted my entire night on this.
Kind of scared now and not sure when I can trust plex to install an updated version.
I might turn off my Plex pass downloads after this. I donāt really care to pay to be a beta tester.
2 Likes
Save your backups and logs! Iām hoping the Plex folks will want to look at them.
This sucks. Iām sorry you also have to deal with this.
Reminds me of the show Drop Out
1 Like
Wow, you tried to roll back to a version that was released mar. 2016 !
If that was the version you used before, then do note, that the database migration could take a VERY LONG time
And with all respect, but expecting to be able to roll back +5 years of versions, is kinda strecting it, in my personal opinion
What I can suggest, is that you use a backup database from then, and run newest version, and after powering up, let it sit there for a couple of hours, before trying anything else
Please expand on above
1 Like
Simply set your update prefs to public to avoid Plex Pass versions
I would just start over if itās THAT big of a problem? Why fight it? Itās media software, not a critical production environment for a fortune 500 company. It doesnāt take very long to pull in new metadata.
Afterwards implement an expanded backup solution to fit your highly strict needs.
Chalk it up to lesson learned the HARD WAY. Stop riding solely on another persons back and take the initiative to protect your own data.
Thanks, Iāll stick to the public releases for now. Iām kind of in a weird position now. I manually restored the plex install dir from a system backup and now up and running againā¦ but I tried to install the release 1.25 version (I restored to an older 1.25) and it still thinks Iām on 1.26 so it says I have a newer version and wonāt install.
Is there a way to force a reinstall of 1.25 or to uninstall/reinstall without losing settings? Plan B is to just wait until a later release of 1.26 and hope the DB corruption bug is fixed.
FYI - I have Plex doing autobackups (I have 4 backup points in the Plex data folder), plus I have incremental system backups going back to the dawn of time so I have all of the older backups too. The problem is that once 1.26 corrupts your DB, it wonāt recognize any of the backups as valid - so youāre forced to start all over.
Thatās not such a fun prospect when you have thousands of video files. Especially the detecting intros part for TV shows - it takes forever.
I agree with 7ven in that an upgrade from 1.25 to 1.26 shouldnāt destroy things. Iām really hoping the bug is fixed before I try the upgrade again on a later release.
1 Like
Are you backing up when Plex is running or do you shut it down?
And normally it would not!
( And also not a wild spread issue )
So something else was/is wrong with the database, and causing this.
If you have a copy of your 1.25 database, and are willing to upload it on like dropbox, and then send me the download link in a DM, I would love to take a look at it.
2 Likes
