JonathanM

Global share settings, set "enable user shares" to "No"

Post your docker run command.

Prepare the new flash with 6.12.4, copy the config folder from your backup overwriting all, you should be good to go.

Which IP were you connecting to? The VNC console is listening on the host (Unraid) IP, on port 590X, where X starts with 0 on the first VM started, and increments by 1 for each additional VM started. If you want to install a VNC server inside the guest OS that will listen on the guests IP, you can certainly do that, I prefer nomachine, it has audio support out of the box, and feels more performant to me.

Kitten will interrupt any attempt. And then fall fast asleep as soon as you are good and awake.

You don't. Wait for the new version to propagate to the repository, the new container will be built with the update after that happens. Never update working production software with a new version first thing, always wait for any bugs to get found by brave early adopters.

Unplug it. Better, if the case has a reset button, it's usually MUCH harder to push, so plug the reset button into the power header, and leave the power button unconnected.

When the docker service starts, yes.

You can try using an external VNC client, point it at the server IP address and port 5900, 5901, or whatever number it happens to be depending on how many other VM's with the VNC video are launched first.

The order and delay only applies to array start. Start all means exactly that, start all the containers. Auto start refers to containers you want started without manual intervention when the array starts. Currently there is no mechanism in place to recreate array start conditions for the list of containers without actually stopping and starting the array. It's pretty easy to write a script to start containers, so if you regularly stop all your containers without stopping the array I'd recommend just scripting it. docker start <container name> sleep 60 docker start <container name> sleep 30 etc etc

No.

Not relevant at all. Each parity disk is independent, and works with 2 different types of math. Parity 1 is a simple calculation, parity 2 is much more complex. They aren't interchangeable and they don't "team up".

When you first start the array, go to the docker tab and see if it's running through the auto start sequence. Set a long wait (maybe 300 seconds?) on the first container in the list. Until you get this figured out I'd disable auto start on all but the first 4 containers so you can start things correctly.

I agree, with one exception, if one of the company principals is the one in charge of the Unraid server because it was their idea, then I'm fine with it.

Unraid as a VM client is not officially supported. It's not forbidden or actively discouraged, but if you have issues the first troubleshooting step will be to recreate the issue running on bare metal. There is a forum section specifically for those who choose to run it as a VM client so they can help each other. New releases are not validated against the huge variety of virtualization platforms, so if there is a breaking change you will be on your own along with the other brave souls running Unraid as a VM to figure out how to make it work. If a fix is found that won't effect the bare metal user base Limetech will likely eventually include it, but it's not a priority.

Assuming you are talking about a krusader docker container running on the Unraid in question, that's to be expected. Containers only have access to file paths specifically mapped to them, all other paths are inside the docker image. Easiest solution is to shut down Unraid, put the boot stick in another computer and do the copying there.

Unraid doesn't use RAID5.

Amount of data is totally irrelevant, parity doesn't know anything about data, just the raw 1's and 0's that make up the entire drive.

This statement feels wrong, but it may just be terminology. File system corruption is dealt with by doing a file system check, a disabled drive is dealt with by rebuilding it, preferably to a different replacement drive so the original drive is still available if more recovery options are needed. If a drive slot displays unmountable, a rebuild won't fix that. The parity equation emulates the entire file system, if there is corruption that is also emulated. It doesn't know about files. A drive that failed a write is disabled with a red x, and parity takes over emulating that drive slot. If parity was valid when the write failed, the emulated drive will be identical and all files will be available, that is what will be rebuilt to a new (or the same) drive when you rebuild. If the emulated drive is unmountable, the rebuild will also be unmountable. Hopefully you already understood all this and just used the wrong words.

If you don't see what's wrong here, you just need to take the calculator down. It's not usable. Unraid is limited to 2 parity drives, and no data drive can be larger than either parity drive.

Which video / tutorial are you referencing?

Please correct the calculator, it is not usable as is, the number of parity drives is not limited to 2, and it allows invalid configurations to be entered. If someone is relying on it for accurate results they will be disappointed when Unraid won't allow them to configure their array as depicted on your page.

Unraid isn't a set and forget, it needs monitoring and maintenance fairly regularly. If there is no one on site that can provide that care and feeding, I wouldn't recommend it either. For Unraid to be successful in a business setting, one of the principles in the company needs to be the one setting it up and maintaining it. Otherwise it's liable to be abandoned and when the first issue comes up it will be catastrophic. One of the downsides of Unraid just working for most people most of the time is that it becomes part of the background, and when something happens your normal IT support isn't going to be able to help. Since Unraid is now offering direct paid support options that isn't as large of an issue as it once was for a company, but it's still a thing. If no one at the company when it breaks even knows who to call, it's going to be scrapped for something that the local IT is familiar with.

Isolate the Unraid box from your LAN to see if it's a device on your network.

IPMI uses the dedicated graphics chip built in to the IPMI module, so if the OS (Unraid) is outputting video to another GPU, it won't show up in IPMI. Have you mucked with the BIOS settings? Are you SURE it's not booting? It could be coming up just fine without showing anything on that particular screen. Check to see if the NIC's MAC is showing up in your router's attached devices area.