UPDATE 2[Fixed…FOR NOW]: Not a Docker issue. I stopped the Plex container, moved the config directory to another drive and restarted. Now it works, at least for a little while. I really need to know how to fix it without having to move it. The 12TB drives are PMR but the 8TB are SMR (shingled) so I don’t want to move it to them. The 12TB drives are less than 1/2 full and show only 14% inodes used. The 1st drive I had it installed on is XFS file system and worked for about a month. The other 12TB drive is BTRFS. Any ideas what I need to do to fix this before it happens again? I could still write to the original drive. I even tried chmod 777 all the files in that directory so it shouldn’t be a permissions issue.
EDIT/UPDATE 1: I think it is more of a OS issue than a Docker issue. Thinking back and looking at play history I think this broke about the same time I turned on photo backups on my phone. It only uploaded a couple hundred of the several hundred, then stopped. The drive I have/had? them saving to is the same drive that holds the config/database files. The inodes are less than 14% and I can still copy files to it.
Server Version#: 1.19.1.2701
Player Version#: Web 4.22.3
Lifetime Plex-Pass since 2014 so I’m not new to Plex, but I am new to Docker. I only found walk-though instructions for linuxserver/plex so I installed that on my home built PC running OMV 5.4.2-1 with Docker5:19.03.8 and Portainer 1.23.2(Current versions now, I don’t know what versions a month ago). Worked for about a month then started erroring. Tried too many things to list, finally removed all images, stacks, containers, uninstalled Docker, Portainer and Cockpit. Reinstalled Docker and Portainer. Found instructions on installing plexinc/pms-docker via command line and added 1 library with only 10 movies (4K). This fresh install will also not play a movie, just spins. I didn’t reuse the same config directory from previous Docker. I’ve checked inodes (highest 14%) and inotify (didn’t return an error)
PC is i5-4670 with 16GB ram
OS on 32GB SSD (7GB free)
Data on 2x8TB + 2x12TB NO RAID (off-site rsync) (all less than 1/2 full)
Config and transcode mapped to 1 of the data drives
I’ve Googled for a couple days now and have no idea what else to look for. Logs attached from newest install this morning of plexinc/pms-docker.
command ran to install:
docker run
-d --name plex
–network=host
-e TZ=America/Los_Angeles
-e PLEX_CLAIM=“copied code from www.plex.tv/claim/”
-v /srv/dev-disk-by-label-12Torange/12T.orange/Docker-Config/Plex:/config
-v /srv/dev-disk-by-label-12Torange/12T.orange/Docker-Config/Plex/Transcoder:/transcode
-v /srv/dev-disk-by-label-12Tblue/12T.blue/4K:/mnt/movies/4K
plexinc/pms-docker
Worked for about a month before it stopped playing.
Changed file permissions recursively on the external config directory for Plex to 777, still wouldn’t play.
Initially using the linuxserver/plex I set uid/gid to numbers for admin/users installed with Docker Compose
I didn’t see where I needed to specify uid/gid for the plexinc/pms-docker installed via command line, so I don’t know what those are.
I tried reinstalling linuxserver/plex to a new directory, no play
I tired installing plexinc/pms-docker to a new directory, no play Once I moved the directory to a new drive I have it working, but for how long? Drive was using 4.07TB of 10.91TB (6.84TB available) This drive is formated XFS. I moved to to a drive with 5.47TB used of 10.91TB (5.44TB available ) that is formated BTRFS.
Before using any docker image you should fully read the documentation for it. If you skip this step, and run into problems, read the docs. How to use uid/gid in the plexinc/pms-docker is…in the documentation, in the Parameters section.
You say you now have it working, but you probably have no idea why. You might want to find out why, because every time you use a docker image you have another chance to have problems.
I know the issue is related to the file system, but I can’t figure out what the issue is exactly. I checked the inodes and I can still write to the drive, but plex would not play any files…until I moved the Docker config (database) files to another drive.
I think the issue happened when I started backing up my photos from my phone, it worked for about a third of them and then wouldn’t upload any more. That is about the time I see no more history for plays.
Like I said file ownership/permissions are the most frequent problem area. Plex is notorious for this and that’s in a native install. Dockers are by design going to be sensitive to and exasperate this.
Looking elsewhere without first examining ownership/permissions and the container runtime context is really pointless.
I appreciate you looking into this, but I’m pretty sure I’ve covered how I’ve taken care of permissions and that isn’t where the issue is. I’ve ruled out it being a Docker issue as well since I’ve reinstalled the Docker image and even changed which Docker image I was using.
It was working, then it stopped. Everything looks great until I, or someone, tried to watch a movie. It just spins, no error. I changed the read/write/execute permissions to 777, no play, just spin. Once I copied the whole Docker config file over to another drive it works again. It isn’t a space issue and I can still copy files to and from the first drive. I add movies, Plex finds them, updates the metadata, but won’t play any movie…until I copied and pointed to another drive.
