Server Version#: Windows 1.32.6.7468 (x64)
Platform: Windows 10 x64 PlexLog-09062023.zip (2.2 KB)
I’m attempting to update from Windows build 1.26.2.5797-5bd057 (x86) to 1.32.6.7468 (x64). The install goes well, it uninstalls the 32-bit version and installed the latest. When it starts and does the database migration, it crashes. Attached is the log.
I’m wondering if it could be database corruption, but I’m not sure how to check or correct that. Or, maybe I should do smaller updates and work my way up to 1.32.6.7458?
I have a backup of my plex appdata folder and registry from yesterday before I started the attempt, so worst case I can roll back. I just want to try getting everything up to date and secure.
I suppose I could start fresh and rebuild my libraries, but I’d hate to lose the watched status and lists for all of my family members.
'Doh! I always ask my coworkers if they’ve checked the knowledgebase before calling me… I need to take that same advice. I just found this and am going to try it.
Rather than deleting the thread, I’m back with an update in case it helps anyone else.
I followed the steps outlined in the Repair a Corrupted Database article and it’s back in business. The database did drop in size from 520,377 KB to 472,136 KB so I’m sure some data was lost. I logged in and it still shows my movies in progress and shows that I’ve been bingeing, so we’ll see if anything comes up that’s weird.
It was wild to see that I have apparently been down this road before and forgot. My folder has some database backups from 2014 and 2018! I guess I’ve been moving those along with everything else during my hardware migrations.
One thing I’m curious about is the com.plexapp.plugins.library.blobs.db. and com.plexapp.plugins.library.blobs.db-wal files. Those are large… like 2GB each. I’m wondering if those are thumbnails or something? Ah well… that’s for another thread!
