March 14, 20251 yr Noticed yesterday that Plex was suddenly having issues loading some files. Saw there was an update for the Docker, so attempted to run the update to see if that fixed the issue. This update was unable to run: Pulling image: plexinc/pms-docker:latest TOTAL DATA PULLED: 0 B Removing container: TheStash2.0 Error: Server error Command executiondocker create --name='TheStash2.0' --net='host' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="GreatBambino" -e HOST_CONTAINERNAME="TheStash2.0" -e 'PLEX_CLAIM'='claim-boCsbosDZxRLyqhcAges' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web' -l net.unraid.docker.icon='https://raw.githubusercontent.com/plexinc/pms-docker/master/img/plex-server.png' -v '/tmp':'/transcode':'rw' -v '/mnt/user/Bambino Media/':'/data':'rw' -v '/mnt/user/Bambino Music/Music/':'/music':'rw' -v '/mnt/user/appdata/Plex-Media-Server':'/config':'rw' 'plexinc/pms-docker' Error response from daemon: Conflict. The container name "/TheStash2.0" is already in use by container "645b02faf3692806d591b3cbe4dc3705691a062ad68956741ac4914d94ea60bc". You have to remove (or rename) that container to be able to reuse that name. The command failed. Unsure what exactly is causing this, then attempted to just start the Plex Docker again, now receiving a message: Execution error Image can not be deleted, in use by other container(s) Server had been rebooted during this troubleshooting, so all other dockers were also stopped. Noticing now that any attempts to start other dockers results in the same "Execution error" message. This server has run mostly problem free for quite some time, so I am at a bit of a loss and appreciate any suggestions. Diagnostics file is attached. greatbambino-diagnostics-20250314-1135.zip
March 14, 20251 yr Community Expert How exactly are you getting it to produce that output? That looks like you are trying to create a new container with the same name. Usually you would edit or update the container from the Docker page, or update it from Community Applications. Often simply restarting a container will make it update the application within. That is how I usually do Plex.
March 14, 20251 yr Author 3 minutes ago, trurl said: How exactly are you getting it to produce that output? That looks like you are trying to create a new container with the same name. Usually you would edit or update the container from the Docker page, or update it from Community Applications. Often simply restarting a container will make it update the application within. That is how I usually do Plex. I am clicking on "apply update" on the Docker page (the same process that has worked without issues for several years now).
March 14, 20251 yr Community Expert Mar 13 17:11:37 Tower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 4554799 off 1995149312 csum 0x6898ab57 expected csum 0xb82a1e7d mirror 1 btrfs csum errors are usually bad RAM This cache corruption could be related to your problem. But in any case, it is much more serious than the problem you are asking about. memtest is on the boot menu.
March 14, 20251 yr Author 29 minutes ago, trurl said: Mar 13 17:11:37 Tower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 4554799 off 1995149312 csum 0x6898ab57 expected csum 0xb82a1e7d mirror 1 btrfs csum errors are usually bad RAM This cache corruption could be related to your problem. But in any case, it is much more serious than the problem you are asking about. memtest is on the boot menu. Running memtest now, assumed this was likely a bigger issue than just the Plex docker, as I am having similar issues with all other Docker containers now as well (even trying to delete unneeded ones - I get the error "Execution Error: Server Error". I also noticed that Fix Common Problems is saying "Unable to write docker image". Could that relate to bad RAM as well, or could that indicate the problem is in another direction?
March 14, 20251 yr Community Expert 20 minutes ago, ketchy311 said: "Unable to write docker image" Because it is corrupt. We can deal with that after you fix what is corrupting everything.
March 14, 20251 yr Author 5 minutes ago, trurl said: Because it is corrupt. We can deal with that after you fix what is corrupting everything. Memtest appears to have passed, unless I am missing something with this. Next thought was maybe it's the SSD Cache drive? Smart short self-test passed, Extended currently in progress.
March 14, 20251 yr Community Expert memtest failure would be failure. memtest pass isn't really a guarantee but maybe longer run would be more assurance. Just noticed you are using Ryzen. Have you seen this?
March 14, 20251 yr Community Expert After checking that try recreating the docker image, as long as it doesn't get corrupt again soon, it could all be OK, if it does, there may still be an underlying issue.
March 14, 20251 yr Author 42 minutes ago, trurl said: memtest failure would be failure. memtest pass isn't really a guarantee but maybe longer run would be more assurance. Just noticed you are using Ryzen. Have you seen this? My errors now seemed to be pointing towards an issue with the Docker image / its cache drive that it resides on: Mar 14 14:05:01 GreatBambino kernel: BTRFS: error (device loop2: state A) in __btrfs_free_extent:3073: errno=-2 No such entry Mar 14 14:05:01 GreatBambino kernel: BTRFS info (device loop2: state EA): forced readonly Mar 14 14:05:01 GreatBambino kernel: BTRFS error (device loop2: state EA): failed to run delayed ref for logical 14184448 num_bytes 8192 type 178 action 2 ref_mod 1: -2 Mar 14 14:05:01 GreatBambino kernel: BTRFS: error (device loop2: state EA) in btrfs_run_delayed_refs:2150: errno=-2 No such entry I have now deleted the docker.img and recreated a new one, installing Plex from the Previous Apps section and so far so good. Not sure if this will be a long term solution, maybe the docker.img just got messed up somehow? Or perhaps a hardware gremlin will still pop up after this runs a while. How do I move or recreate docker.img? The easy way to move or recreate docker.img - 1 Go to Settings -> Docker -> Enable Docker, and set to No, then click the Apply button (this disables Docker support) 2 If recreating your docker.img file, then switch to Advanced View, then check off the box and press Delete, then skip to step 5 3 Using mc or any file manager or the command line, move docker.img to the desired location (/mnt/cache/docker.img is recommended) 4 In Settings -> Docker, change the path for Docker image to the exact location you just copied to 5 Now set Enable Docker back to Yes, and click the Apply button again (re-enabling Docker support) NOTE: If you have created any custom docker networks (eg through docker network create) you will need to recreate them after recreating your image and before reinstalling your applications The standard way to move or recreate docker.img is to stop Docker support, delete the current image, re-enable Docker support The easiest way to reinstall your applications would be to go to the Apps Tab, Previous Apps Section. Then check off all of your previous applications and hit "Install"
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.