While I was away my plex docker stopped responding, when checking my unraid gui it seemed my array was filled to the max and I assumed it was why I was having issues. I went to delete a 400+gb folder in the unraid gui but nothing seemed to happen. I restarted the server and noticed that the docker service had failed to start up. I cant exacrly remember the next steps I took in what order but have tried scrubbing the drive as well as using the Filesystem Status check, neither seem to have done anything to help.

This is my 9th attempt making a post about this. If I log in to my actual unraid account there is no post topic button, If I add a quote block for logs it refuses to post. I'm kinda betting this wont post either

hilly-diagnostics-20251021-2223.zip

31 minutes ago, sleepingzombieALT said:

This is my 9th attempt making a post about this.

Since this was your first post, it had to be approved by a moderator.

Docker image is corrupt; delete and recreate it, but before that, and since btrfs is detecting some data corruption, recommend running memtest first

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

5 hours ago, JorgeB said:

Docker image is corrupt; delete and recreate it, but before that, and since btrfs is detecting some data corruption, recommend running memtest first

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

Thanks for replying. I ran memtest and found a bad stick of ram. Have removed it and restarted unraid. Havn't dealt with docker yet but it now seems like there are a lot of duplicate files between the cashe drive and array. I tried running the mover again and it seemed to finish very fast. I had run it once before realising how bad the issues were, I'm guessing it's copied files to the array but wasn't able to delete them after? Is there a way to fix this.

I did also run another filesystem check and have attached the result...

Is this still likely to be just the corrupted docker image or do I have larger issues?

this.txt

Pool filesystem has other issues, which is expected after running the server with bad RAM. I recommend backing up the pool and reformatting. Note that the mover won't move duplicate files, so if there are any, you will need to decide which ones to keep; you will typically want the older ones.