Server Version#: 1.15.4.994
Plex Media Server v1.15.4.994-107756f7e - Docker Docker Container x86_64 - build: linux-x86_64 debian - GMT -07:100:
Linux version: 4.19.41-Unraid, language: C
Processor Intel® Core™ i7 CPU 950 @ 3.07GHz
Having an issue with a fresh install unraid 6.7.0 and the offical plex docker. I get everything setup and start adding library’s. PMS seems to scan everything and download the metadata. However, when the server is restarted the docker logs spam starting PMS Server, and will keep looping. Reading online someone else had the same issue and it was suggested to repair the database. I do so but all libraries are missing. So i re-add and start over, but each time it has to scan and redo all metadata and all my watched history is gone. Really wish there was a way to sync or backup the database, especially across servers or if the trakt plug in was offically supported.
not sure how to fix this issue or what logs are needed to even look into this. all help is appreciated.
My Plex is also having database corruption after latest Unraid update with the latest Plex. I had to completely do a clean install of Plex and it seems to be working okay for now.
no i mean after the clean install of plex have you tried rebooting your machine? I only ask because i have tried clean installs and i still have the error. looking on here it seems like a lot of people are having the same issue. one person mentioned a older version of unraid helped. now i’m wondering if something has changed with the latest version of unraid that plex doesn’t like.
I upgraded from unRaid 6.6.7 to 6.7.0 last Sunday, May 12th. Almost immediately, my plex database was corrupted. Since then I have tried the linuxserver, plexinc and limetech containers, all have crashed with a corrupted database. I totally delete the plex folder in appdata before I reinstall, and still it gets corrupted. I have reboot my unRaid numerous times, before installing a new container into an empty folder. Still I get corruptions. A few minutes ago I reverted to unRaid 6.6.7 from 6.7.0, and am testing to see if that makes any difference. I’ll update this post when I’m sure it makes a difference, or not.
I’m not sure who to point fingers at, but Plex and/or unRaid need to get together if necessary, and fix this.
One thing I had noticed was enabling the creation of preview thumbnails, caused it to crash almost immediately, and thought that may be the problem. Not so. My latest corruption was at 16:07 this afternoon, with preview thumbnails disabled, though it had been running almost 24 hours.
I removed plex from docker, deleted the plex folder from appdata, and rolled back from unRaid 6.7.0 to 6.6.7. Reinstalled plex (with preview thumbnails enabled), and it’s been running error free since about 17:00, about 4 1/2 hours. That’s longer than it has ever run with the thumbnails enabled, since I started getting the database corruptions.
UPDATE
As of today, it’s been six days since I went back to unRaid 6.6.7, using the latest linuxserver.io Plex container and I haven’t had a single problem!.
Thank you @Mongo75! I just downgraded my binhex Plex install using the following line as the repository. I am hopeful that I can replicate your success!
I Made the changes to my Plex, still under unRaid 6.6.7, and let it run over night. Yesterday morning, it was still running and looking good so I decided to update unRaid to 6.7.0. That was at about 10 in the morning. I’m still running with no database issues, 30 hours later.
This is my Step by Step:
Go to Docker and stop Plex.
Go to your appdata folder.
Rename (or delete) your Plex folder.
Either reboot now, or update unRaid to 6.7.0 and reboot.
After the reboot or update, install and configure Plex. Before you click on “APPLY” and after configuring it to your liking, click the “Show more settings…” dropdown near the bottom of the screen. This is where you set your Plex folder location.
You will see the default setting, /mnt/user/appdata/(container name). You want to change this to /mnt/cache/appdata/(container name) if you use a cache drive, or to /mnt/disk(number)/appdata/(container name) if you don’t use cache. I don’t use cache, so in my case, I changed /config from /mnt/user/appdata/PlexMediaServer to /mnt/disk1/appdata/PlexMediaServer.
Now click on “APPLY” to install Plex.
Once you’re satisfied everything is running smoothly, update unRaid from 6.6.7 to 6.7.0, if you didn’t do it in step 4, and everything should keep running smoothly.
Following the above Step by Step, I’ve been up over 30 hours with no errors, longer than it has ever run since initially updating unRaid to 6.7.0 back on May 12th. I hope this helps
Sadly, my Plex just died again.
May 30, 2019 17:09:57.041 [0x14b38a9f4700] ERROR - SQLITE3:(nil), 11, database corruption at line 65066 of [bf8c1b2b7a]
Also experiencing database corruption with unRAID 6.7.0 and Plex version 1.15.8.1163 on linuxserver/plex:latest Docker image. Database restore steps didn’t help, restored from an old backup of the /config Docker volume, dashboard showed unexpected error again within 8 hours.
Logs:
Jun 03, 2019 13:25:55.925 [0x1505c93e9700] Error — SQLITE3:(nil), 11, database corruption at line 79051 of [bf8c1b2b7a]
Jun 03, 2019 13:25:55.925 [0x1505c93e9700] Error — SQLITE3:(nil), 11, statement aborts at 7: [select distinct metadata_items.id from metadata_items where metadata_items.library_section_id in (1) and ((metadata_items.metadata_type=2 or metadata_items.metadata_type=18) and (metad
Jun 03, 2019 13:25:55.926 [0x1505c93e9700] Error — Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
I initially configured this server with unRAID 6.7.0 so I don’t want to downgrade to 6.6.7 (which sounds so far like the only fix) so I’m just going to disable Plex and follow the forums until there is a fix.
I’m working on a script that i will run with cron.
it automatically creates a temporary copy of the database file, runs a pragma test, and then will rename the temporary file to have the date appended to the end. This way we have a daily copy to fall back to if the database does corrupt.
once the my database corrupts again i will add to the file so it will stop the docker, delete the corrupted database, restore the last backup, and restart the docker. that way we don’t have to keep doing it until a fix is found.
here is a link to what i have made. I’m in no way a expert and take zero responsibility for how this file may impact you, your system, your router, your sisters boyfriends computer. Basically use at your own risk.
