trurl

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

That disk1 SMART didn't have reallocated, but it did have a number of pending, which was actually more concerning. Probably the reallocated you have now were some of those pending, which is actually a good thing if pending has decreased. Unraid disables a disk when a write to it fails. This is because the failed write and all subsequent writes to that disk still updates parity so those writes can be recovered, but the actual disk isn't used any more (disabled) and won't be used again until rebuilt, because it is no longer in sync with parity. When a disk is disabled, Unraid emulates the disk (for both read and write) using the parity calculation. A failed read can sometimes cause a failed write, because if the data can't be read from the disk, Unraid will get the data from the parity calculation instead, and then try to write it back to the disk. The way things stand now, it isn't possible to start the array since there are 2 missing disks. And it won't even let you start it with that disk1 installed again without jumping through some hoops, since that disk has to be rebuilt which can't happen with missing disk7. No problem removing another drive to get disk1 reconnected. But it isn't that important either, at least for now. We can get current SMART for it when you are able to get everything connected again. And in order to rebuild disk7 there isn't really any choice but to rely on disk1 for the rebuild of disk7. Not sure if you know how parity works, but in order to rebuild a disk, parity PLUS ALL other disks must be read to calculate the data for the missing disk. Parity is just an extra bit that allows a missing bit to be calculated from all the other bits.

You will probably need to use some application on the server such as Krusader to manage files in appdata since their permissions won't let you work with them over the network.

You should also post your diagnostics. Maybe there is something about how you have docker itself configured. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Also, go to the Docker page, click the Container Size button at the bottom, and post a screenshot.

Do you use the DVR capability in Plex?

I hope you have removed it. It is not necessary to actually make a change to get the docker run. From that FAQ:

The size of appdata can't make your docker image grow because it is already outside docker image assuming you did it correctly. There isn't any way for part of plex appdata to be outside and part to be inside. It is either all outside or all inside. As explained at the very first link in the Docker FAQ: https://forums.unraid.net/topic/57181-docker-faq/

What specifically were these SMART errors and where did you see them?

Well, that is important, since that is the disk Unraid wants to rebuild. But it is possible, though a bit more complicated, to get it to rebuild a different disk instead. The most important thing I wanted to look at is the SMART report for the disabled disk, which would have been in the diagnostics if it was still connected. Looks like that was disk1, which is disabled and not present. Disk7 also not present, I assume the fried disk. Do you have a SMART report for disk1, a screenshot of its SMART attributes, or any older diagnostics that I might look at?

Here is a FAQ about unclean shutdowns more generally:

Virtualizing Unraid isn't supported, but we have a subforum here for where users that are virtualizing Unraid can support each other. I have moved your thread there.

Can we assume you never started the array while that disk was removed? If that is true, then the only missing disk will be the one you fried, so you should be able to rebuild the fried disk to a new disk assuming the disk you were intending to replace works well enough.

Go to Tools - Diagnostics and attach the complete diagnostics ZIP file to your NEXT post.

Install Community Applications plugin (pinned near the top of this same subforum), then use it to install any other plugins or dockers.

Since you didn't allow it to modify, it only checked and didn't fix anything. Try again without the -n flag.

If you had other write activity on the array then of course that would be competing with trying to clear the array disk, since both would be updating parity. The whole point of clearing the md device is so parity will be updated to stay in sync with all those zeros when clearing the disk. Then it can be removed without affecting parity since all the zeros have no effect on parity.

Not clear why that would make any difference at all. Formatting a drive just writes an empty filesystem to it. The wiki uses the word "clean" (not the same as "clear") when it talks about a quick way to empty a disk by formatting it. If a disk was already empty, then it has an empty filesystem, whether it was newly formatted to get that way, or whether all files were deleted or moved from it. And the only reason the disk has to be empty is because the script doesn't want you to accidentally clear a disk that has files on it. Doing it with dd as you are it doesn't matter at all what is on the disk.

UFS Explorer is often recommended.

Mover ignores cache-no shares. That is why you get the warning, because those will never be moved. You must set it to cache-yes to get them moved to the array. You can run mover on Array Operation page and after moving you can change it to cache-no if that is what you want.

Nothing obvious in those. Near end of syslog it says May 6 02:46:37 htpc-sbb clear_array_drive: Clearing Disk 5 is complete ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 6 02:46:38 htpc-sbb emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/showLog.php clear_array_drive May 6 03:40:16 htpc-sbb crond[2646]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null May 6 11:29:03 htpc-sbb sshd[2467]: Accepted password for root from 10.0.0.6 port 62012 ssh2 But I am guessing that "complete" wasn't really and so you went on to another method. Personally, I would just remove the disk and rebuild parity. Might even be faster.

Tools - New Config will let you assigne any disks you want to whatever slot you want, and optionally (by default) rebuild parity.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Is the controller configured as JBOD? You don't want to use any RAID mode with Unraid.