Database Corruption - Can't launch PMS after fixing it

Plex Media Server Desktops & Laptops
1

Server Version#: 1.18.4.2171
Player Version#: 4.18.1

I got a notification that my OS X Plex Server has a corrupt database. I followed the instructions from https://support.plex.tv/articles/201100678-repair-a-corrupt-database/ and now PMS won’t launch. I was able to workaround the issue by restoring an older version of the db, but I haven’t bothered to check if corruption already exists on the backup. Any suggestions of how I can fix the current db and still have PMS launch? It sounds like another user reported this issue previously here: Database Corrupted and fixing it kills PMS

2

Sadly it looks like a full Uninstall and then download the Plex media server again.

Support article how to properly uninstall.

3

That’s a pretty big hammer and I’m going to lose all my watch history. My current solution of restoring an old backed up DB seems to be a better solution than losing everything.

4

Lets see, the only big unknown is how far back does the issue underlie. I have had to do it once before, yes a bit of work but was a solid fix.

Cross your fingers…

5

You’re running on the backup db, that’s good. You’re uncertain if it contains some corruption, which is understandable. There are two ways to check that. Enable debug logging on the PMS and restart it, wait 6 minutes, then Download Logs. You will see SQLITE3 messages about corruption in Plex Media Server.log if there is corruption. The 2nd way to check for corruption is to follow the repair article that you linked in your OP. Because you’re checking a copy of your .db file, it’s safe.

You also asked how to fix your newer db so that PMS starts. If you’d like to go down that path, we’ll need exhaustive details from your PMS in debug mode to see what’s causing it to not start.

I’m curious which previous database you had. Was it created by PMS during scheduled tasks?

6

Thanks for the tip. I don’t see any SQLITE3 messages in the Server logs so I’m guessing it’s clean. I restored to a db from December 30th so I’m guessing it was a scheduled task because I never manually backed it up.

7

nice I would think you had terrific success.
That log file also organizes itself into levels of messages.
ERROR messages and CRITICAL messages would optimally not exist.
Some errors during the first 6 minutes after PMS is restarted are non-errors that solve themselves when the users’s remote access comes online.

I’m wondering if an unexpected power cut led to your corruption in December.

8

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