Kilrah

Why not use the appdata backup plugin?

Type the path manually, it's the directory picker in unraid having a bug and not allowing to select /mnt/remotes. Nothing to do with the appdata backup plugin.

Remove config/vfio-pci.txt on the flash drive.
 
Passing through is for using them in a VM, not what you want. Unraid doesn't have a sound system so you can't do what you want. 

Try rebooting first.
 
If that doesn't help recreating the docker image is just clicking the button to delete it, starting, recreating any custom networks you may have had, then go to apps->previous apps and select your apps to reinstall, they'll be back with all your settings.

CRC errors are communication issues between drive and controller, they get corrected by retries so no issues with data.

1 per license.

Disk5 showing yellow means it's above the utilization warning that either you set or is the default one in disk settings

Yes the message isn't suppressed invalid when "parity is already valid" is checked. It won't be overwritten then.
 
With dual parity I think you need to do both separately.

Yes once the shrink procedure is done the array will be operating normally. 

Set those 2 drives as encrypted as part of the array and set up the share you want encrypted to only use those 2 disks. 

No need to look further, unexpected power loss is always likely to cause corruption. 

No problem, it'll just have stopped and restarted immediately since there was activity.

Open the file manager from here.
 

Click the + to add a 2nd. 
 

Nothing looks wrong, you just have a bunch of stuff for which the images are big.

You probably have a container path mapped directly to /mnt/cache_ssd/whatever instead of /mnt/user/whatever, that will bypass any share settings.
 
disk to disk is fine, share to share is fine, it's mixing the 2 that isn't. 

Well that's the point, if you don't want them turn that off.
 
But yes setting primary ssdpool, secondary array, mover array->ssdpool would disable exclusive for that share and never actually use the array unless the pool is full.

You've put the HBA in a x1 slot? That's going to be maxed out by 2-3 drives...

Split level? Post the share's settings

Because /tmp is not itself a tmpfs, it's just a folder in the rootfs. Would have to  "mount -o remount,size=12G /"
But you should rather use /dev/shm which is a separate tmpfs (could resize it the same way) with the difference that if you fill it you won't make the system crash because of a full rootfs.
 
Still need to be careful to leave enough RAM for the apps and system.

Both screenshots show a parity-check in progress with sync errors. A disk rebuild will not show any sync errors, only a parity check. In your first post you mentioned the steps you did but that did not mention starting a parity check.
 
2nd post mentions stopping parity checks but again nothing mentions why or when any was even started, so again what the screenshots show doesn't match the description of what was done.
 
Your syslog is full of spam from XFS corruption so hard to read, assuming it's for that new disk 6 but you cropped the main page screenshots showing whehter it showed unmountable.
 
No since once parity is built from the array it'll just get updated as you format the drive/copy data to it as it always does.
 
Parity is useless at this point anyway. IMO B is safer since should your old disk 6 fail part way through the copy what's already been copied will be safe, with plan A you get nothing if the parity build fails to complete.

Then you can't make snapshots, it's "layering" vdisks. 

Select Ubuntu or Debian template since that's what Mint is based on.
Custom means "I'm writing the whole XML myself".

You also need to have secondary set as array, and mover action set to Array->Cache.

"+" hier: