Hi all,

Struggling with the next steps on this one.

I have had a disk die - (disk1) so I proceeded to move everything off it to other disks in the array as I cannot afford a new drive currently, this completed but after it did, the emulated disk showed 4TB still in use. I had started to troubleshoot this but didn't get far as I had to go out today, I did manage to get a screenshot showing the usage below, despite there being literally nothing on this disk when looking into it:

What was also interesting and a bit scary was that when I was moving data off the drive, disk6 started to throw up UDMA CRC errors. I wasn't massively worried about this at the time as I understand these are generally cable issues so I purchased another breakout cable and planned to replace it but combined with the latest issue I am now a bit worried!

So I came home and my Plex docker seemed dead, it was running so I restarted it, same issue, I then checked the log and could see the following:

2026-10-11 16:29:10,132 DEBG 'start-script' stderr output: chmod: changing permissions of '/config/Plex Media Server/Codecs/EasyAudioEncoder-6a4213e165f8ac3d108a346e-linux-x86_64': Input/output error

I then checked other docker containers and half are not running, half are, but cannot be used. So I am suspecting some docker image corruption perhaps... I then just thought let's reboot the server to see if perhaps the disk1 usage thing clears and it maybe fixes the issue if some paths are looking at disk1. When it came back up, disk1 started to show "Unmountable: wrong or no file system" I stopped the array and started it again, with disk1 still in but same issue. I am wondering if I should replace the cable that disk6 runs on and then create a new hardware profile with all the drives moved up 1 so I can then scrap disk1 but I am a little worried with the docker issue on top and wanted to run it by you guys before I likely make anything worse! I've also attached diagnostics as it currently stands.

I thought I'd do some less intrusive testing and did a 'touch' on disk6 and it shows input/output error on that disk when I try, the other disks work fine so perhaps the dockers won't start successfully as they're trying to write data to disk6 first and it's not allowing it so they just break?

atlas-diagnostics-20261011-1701.zip

Edited 16 hours ago16 hr by J89eu

You appear to have 2 shares on cache with the same name but different case. Linux is case-sensitive, so these are different shares. Possibly you accidentally created one of these by specifying a host path in a container with the wrong case.

Even though the share with the lowercase name is on cache, it has default settings since they weren't configured. One of those defaults is to not use cache.

You should probably consolidate those 2 shares by moving the files from the lowercase share to the uppercase share, and checking that all of your containers are using the uppercase share. But leave that for later.

Not sure what is going on with your dockers. Possibly some of your appdata was on disk1 but it is disabled, and the emulated disk1 isn't mountable.

I recommend going to Settings - Docker and disable Docker until you get these other problems fixed.

Then check filesystem on emulated disk1. Post the output.