JorgeB

Just set the correct primary, secondary storage and mover direction for that share and run the mover, also make sure the file are not in use, you can enable the mover logging to see why files are failing to be moved:
 
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
 
 

Jul  5 12:14:11 PlexServer kernel: sd 1:0:7:0: device_unblock and setting to running, handle(0x0020) Jul  5 12:14:12 PlexServer kernel: sd 1:0:7:0: Power-on or device reset occurred Jul  5 12:14:13 PlexServer kernel: sd 1:0:6:0: device_block, handle(0x001f) Jul  5 12:14:13 PlexServer kernel: mpt3sas_cm0: log_info(0x31120100): originator(PL), code(0x12), sub_code(0x0100) Jul  5 12:14:14 PlexServer kernel: sd 1:0:6:0: device_unblock and setting to running, handle(0x001f) Jul  5 12:14:15 PlexServer kernel: sd 1:0:6:0: Power-on or device reset occurred  
These "Power-on or device reset occurred" errors happening for multiple disks usually mean a power/connection problem, so could still be PSU, cables, etc, or bad backplane for example.

This is usually not a problem, except for some early Ryzen CPUs, most boards come with this enabled by default.
 
Your issue appears to be this:
 
 

Run it again without -n, and if it asks for -L use it.

They should be automatically created when you enable the docker and VMs services, those services come disabled by default, for a clean 7.0.0 install.
 
You can, and this will help performance, like folder listing or any other metadata intensive works, but a 120 GB SSD would be enough, unless you use many small files, in that case you can make the small files, up to a size, go to the special vdev, but like mentioned by @Kilrah it should have the same redundancy as the main pool, in this case a mirror, if you lose the special vdev, you lose the whole pool.
 
 
 

Yes if you also delete the user-templates folder from the flash drive
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
 
They will be in the image, and the data in appdata, but you you'd need to re-add them to see them again.

Usually there's also a summer sale, though it's not always for all types of licenses, but I don't have any official knowledge or confirmation if there will be one this year.

Yes.

We can try to re-enable the dropped disks, but it will only work if parity is still valid:
 
-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed, including the new disk2, replacement disk should be same size or larger than the old one
-IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)
-Stop array
-Unassign disk2
-Start array (in normal mode now) and post new diags.
 
 

With parity1 it's possible, just do a new config, re-assign the disks and check "parity is already valid" before array start.

Change to ipvlan or if you really need macvlan disable bridging.

https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/

That would suggest more a hardware issue, did you enable the syslog server to see if there's something there?

Can't help with SCP, but it might be easier to enable an SMB/NFS share in Openmediavault and then use UD to connect to it.

https://docs.unraid.net/unraid-os/manual/users/reset-password/

https://forums.unraid.net/topic/113037-docker-advanced-view-reflect-memory-limit/?do=findComment&comment=1029211
 
No ATA errors so far.

Try recreating the docker image:
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Known issue, fixed for beta.2, but it's only visual, it will still create a stripe or mirror if you apply that before formatting.

Errors continue, if you replaced both cables it could be a bad disk, you can swap cables with a different disk to make sure, see where the problem follows.

The Sandisk should be the first option here:

 
Then save setting and reboot
 
 

Syslog rotated, and is missing the start of the problem, type reboot in the CLI then post new diags after array start.

Looks like there were some lost writes, likely to the underlying device.
 
If the vdisk is OK, you should be able to use a new libvirt image, then create a VM with the same settings and point to the existing vdisk.
 
Recommend keeping a backup of that file for the future.

There are errors in most disks, so Unraid cannot emulated them, reboot and post new diags after array start.

Yes.

If it's a refurb I do at least an extended SMART test or precelar to confirm it's good.