trurl

You have too many missing disks. Single parity will only allow you to run with one missing disk. And will only let you recover the data of one missing disk. Do you mean you would now like to simply forget about those other disks and any data they might have had, and go ahead and run with fewer disks than you had before? If so, then you will have to set a new config and rebuild parity. Probably you shouldn't do anything but get rid of that controller and work with us to get all disks working again. I think it's possible none of your disks have failed and the controller is the cause of all your problems. That and the fact that you didn't ask for advice when you had the first problem and just decided to do something that made things worse.

Your screenshot is showing you have 3 missing disks and it says you have too many missing disks. Which agrees with your diagnostics. Did you used to have more disks? What have you done?

You have too many missing disks. Post a screenshot of Main - Array Devices and Main - Array Operations.

You can map any host port you want to the container port 8080

Don't change the container port. You have set the host port as you want it to be, and that is OK, but you have changed the container port to match. You have to leave the container port alone and let it use the port the container expects it to be. That is what mapping is all about. The container port corresponds to (mapped to) a different port on the host. Just like with volume mapping. /config in the container corresponds to (mapped to) a different path on the host, /mnt/user/appdata/openvpn-as. Understanding mapping is most of what you need to understand about setting up any docker all by yourself and without relying on anybody else to tell you exactly what you need to do.

Post the docker run command that results from attempting this in bridge mode.

Maybe you should look at a different solution. Many routers have OpenVPN builtin and you don't have to bother with getting a docker or anything running on Unraid. There is also the Zerotier docker which might work for you and be easier to setup.

Did you actually try this? You mostly just seem to be telling us lots of different things don't work, and frankly, I haven't been able to figure out what you have even tried. It all just comes out as a bunch of stuff all running together. You need to take a single attempt, explain it completely and clearly, and let us help you clear it up. I don't know if we are having a language barrier, or you just don't understand enough to express things in an intelligible way. The key to mapping ports is to leave the container port as it is already configured to be and don't even attempt to change it in any way. Instead, change the host port that maps to that container port. Whatever port you want to use on the host side will be translated by the docker engine to the port the container is expecting as long as you don't change the container port part of the mapping.

Please edit your post and delete all of those separate files, then attach the Diagnostics zip file you downloaded instead.

Seems orders of magnitude more complicated to implement.

Do you understand mapping? What port mappings are you using when you set it to Bridge mode?

Seems like is exactly the functionality you would want. What would a button do, restore everything? Even Windows Recycle Bin makes you select what to restore.

If you are using Host then you can't map ports. Not sure if you understood that from things already said here since you seem to be trying things at random.

Yes. You must let Unraid format any disk it will use in the array or cache, so if you are planning to use disks that already have data on them then you will have to consider what to do with that data. Those 500G disks are smaller than often used here, but that is OK for starters assuming they are reliable. Parity by itself cannot recover any data. Every bit of Parity PLUS every bit of all other disks in the array must be reliably read to reliably recover the data for a failed disk. And parity is no substitute for backups. You must always have another copy of anything important and irreplaceable. Yes. You can make a pool and add another later for redundancy if you format it as btrfs. You can RDP / VNC to other VMs. You can access disks from other systems with the Unassigned Devices plugin

All drive assignments appear to match a diagnostic posted on March 7 https://forums.unraid.net/topic/78533-loads-of-gz-files-added-to-root-dir-of-unraid-usb-key/?do=findComment&comment=728325 EXCEPT disk5 is a different disk. So not a swap but also not sure when or how a new disk5 was introduced. For future reference, you can always download a zipped copy of flash at Main - Boot Device - Flash - Flash Backup. Even after you get your array fixed, by not having a backup of flash, you have lost all settings you made in the webUI, including docker templates.

Post your diagnostics and docker run command. https://forums.unraid.net/topic/37579-need-help-read-me-first/ https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

We always recommend not overclocking

One way to work around this is to refer to user0 for the share that doesn't use cache. mv /mnt/user/share1/file.txt /mnt/user0/share2/file.txt Unfortunately, users aren't aware of the problem or the workaround. To the user, it is surprising behavior, but not as potentially disastrous as the surprise they get with the "User Share Copy Bug". Lots of ways users and their setups can work with files directly on the server instead of over the network these days and without ever going to the command line.

Looks like the shares that belong on cache are all on cache now so that looks good. You only have a couple of other shares, and they have files on disk1, isos and another with name starting with D. If you have VMs or dockers using those shares then that might explain the drives not spinning down. There are a few plugins that might help figure it out. Go to the Apps page and take a look at Dynamix Active Streams, File Activity, and Open Files plugins.

So if I understand correctly, you have not actually removed any disks, and perhaps the disk you intend to remove still has data on it. You would only go to New Config after you had already copied the data from the disk you want to remove to other disks in the array. The Unbalance plugin can help with this. I think you can probably just leave that New Config page since there isn't really a new config until the array is started. Or, there should be a check box saying parity is already valid, and that should make that message go away if you check it. Maybe you should give us a screenshot just to make sure we understand what you have. Wait and see if there is another opinion, since I haven't done New Config in a very long time. But I think you can probably you can just quit that page and nothing will change.

Tools - Diagnostics, attach complete zip to your next post.

Post new diagnostics

Some odd things in your diagnostics but maybe just because your version is so old. You are getting wrong csrf tokens from preclear in syslog, but according to your diagnostics you don't actually have the preclear plugin installed. You have given your docker image 50G, which makes me question if you don't have some issue with your docker setup. But you aren't filling that up, it's just the fact that you have it so large that makes me think you may have been filling it in the past. It is extremely unlikely you would ever need more than 20G, and you currently aren't using anywhere near 20. But filling docker image is not the same as filling rootfs anyway. Filling docker image would mean one of your applications was writing to a path that wasn't mapped. But filling rootfs might mean one of your volume mappings isn't to actual storage. But according to your diagnostics, you don't actually have cache, so if you have that as some path then maybe we found your problem.

Some of your system share is still on the array. Go to Settings and disable both Docker and VM services then run Mover. Mover can't move open files so if either of those services are running it can't move their image files to cache where they need to be.