1.26 beta ruined my library. How do i request a refund for my lifetime pass?

Please tell me how supposedly valid backups taken over a period of time stop working because one single copy get corrupted? This makes no sense.

If you have a valid backup with PMS version X you can always roll back to that version of PMS with that specific backup and it will work. Corrupting one single instance of the database does not change them all.

FYI what you’re saying makes no sense especially if you have incremental system backups made by the OS or another 3rd party application.

Unless you are doing something wrong.

I suspect database was broken before the update, but when said, then the scheduled backup should also stop, so puzzled here, thus why I asked for a db copy

2 Likes

Just sent a DM with a dropbox link to my DB file.

Works until I upgrade to the latest 1.26 then Plex no longer starts. Popup error about having a corrupt DB.

I then tried replacing the .db file with one of the dated backup ones with the same error popup.

Each time, I’m able to get working again, by replacing the Plex install dir (with the Plex binaries) with one from a system backup.

2 Likes

I’d like to know too - I’ve tried both the Plex auto backups as well as system backups made by Windows Server Essentials (basically a standard shadow copy/VSS backup service) with the same results.

I even ran the integrity check command that’s in the ‘how to restore a corrupt db’ instructions and the command says that all of those files are corrupt.

It’s weird. Anyway, I sent Dane22 a link to my currently working DB that stops working if I do the 1.26 update (tried 3 times now).

1 Like

This was almost my exact process. 1.26 really did a number on my system.

Hi all. Dane22 went over my log files and I’m now back in business.

It turns out that I had a .wal file that was causing problems - even when I tried to use a post-migrated db.

In the end, I also had to delete the com.plexapp.plugins.library.shm and com.plexapp.plugins.library.wal files. Started with just the com.plexapp.plugins.library.db file and all was good (Plex auto created new versions of those files afterwards).

I am now successfully using the current 1.26.

2 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.