Server Version#:
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
I have bo idea what happened. I updated my docker container and now its dead
1 Like
In my log file it looks like the sql database is corrupted. Im going to guess noone has a solution and im going to have to blow away the docker and start over. Ive had a few apps do that lately. Ill wait until someone responds though incase theres a better way to fix it that diesnt lose all my settings.
ChuckPA has a nice tool for database repair: GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases
1 Like
Bueller? Bueller?
I have just Wiped everything out and reinstalled. I it’s rebuilding the database right now (scanning files, adding recording data etc)
I want to see if I can add that database script to run every few months automatically to fix small errors before they snowball
Hey, I’m waiting on someone to come online who knows unraid to show him this.
apologies, as I said I already wiped it out since I wasn’t getting feedback. I want to record the Trump CNN thing tonight, should be fireworks.
@electrohacker I hate to say this, but its fairly common for unraid to kill the database. Something with how it manages its file system. My best suggestion besides switching to another platform would be to create regular backups of your database and keep them for at least 60 days.
(you probably could have used one of Plex’s automatic backups to recover but never gave enough time for that response)
I also think that years ago I over installed a new copy of plex media server (the official version) without deleting the files. I think this could have added to the problem.
yeah I probably rushed it, but all I lost was my recording schedule (and a few manually matched files?) nothing I cant fix over time.
Thank you for the suggestions to prevent this in the future.
I have also scraped the Plex container and reinstalled it with a new empty database. Sorry, I didn’t expect any reactions in this thread anymore.
@Raki72 Sorry to hear you had this issue. I would advise you to add an additional bind mount path into the Plex container for database backups
Then in the Server setting you change the backup path in for databases, to /backups which in my case will then save these to /mnt/user/Backups/PlexMediaServer/ on the “host” Unraid side.
2 Likes
that path DOESNT EXIST, in the offical plex unraid docker container.
I find it extrememely frustrating that we have to add these paths manually for setting you know exist in your docker container. When I was new to unraid this is one of the things that really turned me off. I think this could be a reason you lose so many new users, they dont want to manually add features.
@electrohacker the path does not exist in the offical Plex container as it is not required for regular use. The standard appdata path contains the backups folder by default and is sufficient for most users.
The reason I recommend adding an additional path is to allow you more control over where database backups go.
excuses. also the Nvidia transcoding variables are there by default either.
Thanks for posting this, it’s a cool idea that I wouldn’t have otherwise thought of.
1 Like
I rolled back to plexinc/pms-docker:1.32.0.6973-a787c5a8e and it works fine now. Updating to the latest breaks it again.
I switched to linuxserver/plex:1.32.1 and everything works fine now when started from scratch.
