trurl

Do either have parity?

That is basically the difference between dockers and plugins. Plugins are running in Unraid. Plugins are enhancements to Unraid itself, not a separate application.

Does your BIOS see the disks?

Containers run in a virtual environment like a VM. So

Unraid only requires a clear disk when you are adding it to a new slot in an array that already has valid parity.

yes

Have you done memtest?

On the other hand, if you create a top level folder on cache or array (or even in /mnt/user), it is automatically a user share with default settings. And if you delete all top level folders of that name from all cache and array disks, then the share is gone. It is still better to manage from the webUI though, since it will remove all top level folders for you after all share contents are gone. Note that none of this has anything at all to do with any container. User shares are simply the top level folders on cache and array. According to your syslog, you had an unclean shutdown. Why did you have an unclean shutdown? Perhaps that is the FCP error. Since you have no parity disk you didn't get a parity check from the unclean shutdown. Why don't you have parity?

krusader is NOT an Unraid app, it is a docker created by other Unraid users. As with all containers, Unraid doesn't know what is going on in the container, and the container doesn't know what is going on in Unraid. That's sort of the point of containers.

Very first link in the Docker FAQ:

I assume you mean the CA Backup plugin, not a docker.

You should get a new backup anytime you make changes to your configuration. This is especially important when making any changes to disk assignments.

Assumed that, but it might make sense for mover behavior to accommodate moving from one pool to another for prefer shares. Or not.

I would expect it does have a GUID, but there is no benefit to USB3 for the boot flash, and those very small USB3 drives are prone to overheating. USB2 flash drive booting from a USB2 port is likely to be more reliable.

I didn't look at the logs before since you had already been warned. Close all ports on your router immediately and/or take your server out of the DMZ on your router. The internet is full of bots that automatically look for things to attack and will attack relentlessly. Just a sample from your syslog. There are likely hundreds of others and it will continue until you take your server off the internet: Jul 21 13:23:16 UNRAID sshd[27160]: Disconnected from invalid user devopsuser 54.37.44.95 port 34858 [preauth] Jul 21 13:23:16 UNRAID sshd[27288]: Accepted none for adm from 5.188.86.212 port 57365 ssh2 Jul 21 13:23:20 UNRAID sshd[27352]: Failed password for root from 222.186.175.183 port 48002 ssh2 Jul 21 13:23:20 UNRAID sshd[27401]: Accepted none for adm from 5.188.86.168 port 43027 ssh2 ... Jul 21 13:23:24 UNRAID sshd[27529]: Accepted none for adm from 5.188.62.14 port 38206 ssh2 ... Jul 21 13:23:41 UNRAID sshd[28073]: Accepted none for adm from 45.227.255.207 port 58710 ssh2 https://www.abuseipdb.com/check/54.37.44.95 https://www.abuseipdb.com/check/5.188.86.212 https://www.abuseipdb.com/check/222.186.175.183 https://www.abuseipdb.com/check/5.188.86.168 https://www.abuseipdb.com/check/5.188.62.14 https://www.abuseipdb.com/check/45.227.255.207 As you can see from those links, you are being attacked from all over the world. @ZiemaF Fix this NOW!!!

The rsync line is where the work is happening. If you have a share named photos, its path is /mnt/user/photos, a share named video has path /mnt/user/video. You could just duplicate the line and make the appropriate substitutions.

Go to Settings - Docker, disable dockers and delete docker image from that same page. Then Enable dockers to recreate docker image. The Previous Apps feature on the Apps page will reinstall your dockers just as they were. Not sure why you would need 600G for domains. You really only need to give the VMs space for their OS. They can access the rest of the Unraid storage as needed on the virtual network.

Is that the latest diagnostics? Those diagnostics don't have the cache settings for domains and system shares that I instructed. And they have Dockers and VMs enabled. Did you change these after moving but before getting diagnostics? Also, domains share is still on the array. Do you actually have any VMs? Don't worry about docker image for now.

WireGuard VPN is builtin to Unraid:

Settings - Docker, disable. Same for Settings - VM Manager. Set system and domains shares to cache-prefer. Main - Array Operation - Move Now Wait for it to complete and post new diagnostics.

Easier to type it than to look it up, but since I have typed it a few times recently I can give a link to something from my recent post history. Check all connections then https://forums.unraid.net/topic/94978-lost-1-data-disk-and-2nd-parity-disk/?do=findComment&comment=876877

Since we don't have syslog from when the problem occurred we can only guess what caused disk1 to be disabled, but SMART for disk1 looks OK. You must rebuild of course and are unprotected until you do. Do you know how to rebuild the disk to itself?

docker image is a vdisk formatted as btrfs. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Depends on your answer to this question