itimpi

Do you have a “yes I want to do this” checkbox opposite the Start button? If so you need to check that to be able to start the array.

Have you rebooted since installing the paid for key? If not you will need to do so to activate the key. Probably also worth deleting the trial key first.

It might also be worth updating to the latest Unraid stable release (7.2.3) as the version you are running (7.0.1) is now quite old.

Glad to hear things are good, but a word of advice in that it would have been better to run the repairs from the GUI as it is easy to get the command wrong when using the CLI whereas the GUI ensures that the command run is correct.

Do the steps in the order recommended by @trurl as this means your array is still protected by parity2 while you are rebuilding parity1 just in case a data disk has problems during the parity1 rebuild. Although it is not necessary to preclear any drives you might decide you want to (optionally) do this on the new 28TB drive to act as a confidence check before using it on the array. The old 14TB parity drives should not need this as they have (presumably) been running reliably as parity drives, and the Unraid Clear process is faster than doing a preclear.

You should set a Minimum Free Space value for the 'cache' pool to set the limit at which it should overflow to the array rather than fill the 'cache' pool too far. In addition you also set the Minimum Free Space setting for shares (in particular the Media share) to set the conditions at which Unraid should switch to another array drive if one gets too full. Neither of the above will directly address why mover is not working so follow @JorgeB advice as well to help us with diagnosing why.

This sounds like an 'automatic' share that has been created because you have a top level folder with that name on one of your drives.

A share is of the ‘only’ type if it has primary storage set and no secondary storage set. Note, however, that Unraid will not automatically move any existing files that are in the wrong location when you remove a secondary storage option.

The attachment is not available! You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs and configuration information.

this. With Unraid 7.2 there is no requirement to have any drives in the main array, so you could instead put them into a pool where trim IS supported.

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs and configuration information.

You should put each rule on a separate line.

@digitaldoctor If I remember correctly you can change the docker vdisk size without disabling docker as long as you stop the array.

That will be parity2. You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

I would have said the opposite. You want to keep parity1 as it’s calculation puts less load on the system.

If the share is only on a single drive, and you have enabled Exclusive Access option under Settings->Global Share settings then the FUSE layer should be by-passed. This is the recommended way to do this rather than reference the physical path directly as it is less likely to cause issues if you later make changes to your setup.

If you have secondary storage set for a share then you are 'caching' it. We can confirm this if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs and configuration information.

Are the shares set to be cached on the Unraid side? If so this can cause problems when using NFS to access shares when mover runs to transfer files between the 'cache' pool and the main Unraid array. If you use SMB instead to access such shares then this issue does not occur.

It is when the “mirror to flash” option is set (which you have done).

Normally the best indication of whether a disk is OK is whether it can complete the Extended SMART test without error.

The location you have specified for the docker image is set to be "/mnt/cache/appdata/docker-xfs.img“,but you do not have a pool called ‘cache’ so that location is in RAM which is why it does not survive a reboot.

That is default Unraid behaviour. You have the Parity Check Tuning plugin installed but you have not set the option to try and continue array operations from last point reached on a reboot.

Have you tried disabling bonding for the 10Gb card?

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

It does. Unraid was changed some time ago to handle ‘shutdown’ correctly which is why ‘powerdown’ became deprecated. You can always try to confirm to yourself that this is the case.