trurl

The fact that all except disk2 is showing unmountable makes me wonder which disks if any actually had any data. If you can tell us which disks should have data it might be possible to repair their filesystems individually and then start from whichever disks work and can be repaired to build a new array.

There isn't really a "rebuild" operation to choose. When you replace a disk and start the array, Unraid rebuilds to the replacement. But in order for that to work, or even be allowed, ALL other disks must be available. Parity by itself cannot rebuild anything. Parity PLUS all other disks are required to rebuild a missing disk. If you have dual parity then you could rebuild 2 missing disks, but that doesn't apply to you. You have 2 missing disks according to your screenshot, so rebuilding is not possible. If you can give us a better understanding how this happened, it might be possible to get Unraid to rebuild one of the missing disks by telling it that all the other disks are OK. But we need to know exactly how you got here in enough detail to let us at least take a guess at what disks parity is based on. Do you have backups of anything important and irreplaceable? The simplest way forward is probably just to save disk2 and format the rest.

A little unclear how you got here. Your first mistake was not asking for help when you were having trouble with disk7. Since you already had a missing disk7, your array had no redundancy to allow you to replace any other disk. Disk1 SMART isn't showing in the diagnostics. Are your sure it is really dead? Bad connections and cables are more common than bad disks. The thing I am having trouble understanding though is disk3. Unraid seems to indicate it is the correct disk in that slot, but you say it is a replacement. See if you can describe exactly how you got to this point, step by step, starting from the last point in time when all of the array was showing no problems.

Nov 3 10:21:43 Tower emhttpd: unclean shutdown detected The array stopped/started status is stored on flash. If for some reason flash can't be written when shutting down, or if power is removed before stopping the array, then you get an unclean shutdown which results in a parity check. Put flash in PC and let it checkdisk.

I don't use radarr, but /opt/radarr would definitely be inside the docker image, unless you have mapped /opt or /opt/radarr to Unraid storage. But I doubt mapping that is the usual way. More likely you are just missing setting some path within the application settings and it is defaulting to that path.

Understanding parity can help make sense of many things about how Unraid manages your disks. Here is the wiki on how parity works: https://wiki.unraid.net/UnRAID_6/Overview#Parity-Protected_Array

No need to panic. Parity doesn't contain any data. It only has bits that allow the data for a missing disk to be calculated from those parity bits PLUS the bits on all the remaining disks. You can definitely start the array and access its data with parity missing. In fact, if it was a data disk that was missing and parity was OK, you could even access the data on the missing data disk, from that same parity calculation I mentioned. What you can't do with a missing disk is have any redundancy in the event of another disk failing in some way. When you get the replacement disk, you would just install it, assign it to the slot of the disk you are replacing (parity in this case), and Unraid will rebuild the disk contents using that same parity calculation I mentioned.

Post your docker run command as explained at the very first link in the Docker FAQ: https://forums.unraid.net/topic/57181-real-docker-faq/

You only have 1 data disk and no parity disk in the array. Data disk1 is unmountable. It should show this clearly in Main - Array Devices, but you didn't mention it. User shares cannot work with no disk mounted in the array. Check filesystem on disk1: https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS Be sure to capture the results so you can post them if needed.

Changed Status to Open Changed Priority to Annoyance

I've never heard of the encryption key appearing in the diagnostics. Are you sure it's there?

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

I split your post into the Docker FAQ feedback its own thread. As explained in this very first post in the Docker FAQ thread: Please don't post in the FAQ thread unless you are posting the ANSWER to a Frequently Asked Question. I always recommend a docker image size of 20GB. There is some slight chance you would need a little more since you have so many dockers. Unless you have one or more of your docker applications misconfigured, you are very unlikely to even need 30G. The most common reason for filling docker image is an application that is writing to storage that isn't mapped. This would be a setting in the application itself. You must make sure that every place the application can be set to write something is set to use a path that corresponds to the container path in the volume mappings configured for the docker. Common mistakes are not using the same upper/lower case as specified in the mapping, or not using an absolute path (must begin with /). Making docker image larger will not fix the problem, it will only make it take longer to fill. When you updated the docker, it was reinstalled, so that would explain why it wasn't using the space any longer. But it is likely it will continue to grow since you didn't actually change anything that was causing it to grow. Check all of the paths specified within the application settings.

DONE

Post your docker run command as explained in the very first link in the Docker FAQ: https://forums.unraid.net/forums/topic/57181-real-docker-faq/

Have you seen the Docker FAQ? https://forums.unraid.net/topic/57181-real-docker-faq/

It sounds like you are considering not replacing the disk right away. You shouldn't continue to run the array with that disk since it compromises the redundancy of the array. And removing a disk (shrinking the array) is a different procedure than rebuilding a disk. Let us know what you intend to do, there are specific procedures for the different ways you might change your disk configuration. If you look on the Dashboard, you should see SMART warning for that disk. If you go to Main - Array Devices and click on the disk to get to its page, then look at Attributes, you should see some lines in yellow. Those are the things that make me say the disk should not be used in your array. And they are good evidence that the disk is untrustworthy.

This question makes me wonder if you misunderstand parity. Parity does not contain any of your data. It is not any more important than a data disk. If anything it is somewhat less important since it doesn't have any files on it. Parity by itself can't recover anything. Parity PLUS ALL remaining disks allow the data for a missing disk to be calculated.

You want to format it before returning it? You absolutely must not format a disk in the array unless you don't want any of its data.

Do you have backups of anything important and irreplaceable?

Yes it is, replace it. https://wiki.unraid.net/UnRAID_6/Storage_Management#Replacing_failed_disk.28s.29

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Please don't try to fix anything without further advice.

Some things, such as moving/copying files on the server, are more efficient than doing that over the network. But be careful, you can easily get yourself in trouble. You must never move/copy between user shares and disks, or you could lose data, since linux won't know that the source and destination could be the same file and so could overwrite the file it is trying to read. And as you have seen, some things don't survive reboot. This is because the entire OS is in RAM. Only the actual storage persists. Unraid unpacks itself fresh from the archives on flash at boot into RAM and runs completely in RAM. Plugins, for example, are reinstalled at boot. It's probably best if you don't get too carried away with the command line until you have a good understanding how Unraid works and how it might be different from a full linux installation.

You have mapped /mnt/user/Media_files to /media, so Plex will see those in /media.

NP, "Newbie"😉