Faceman

You have mover tuning plugin running, so you can check for files with symbols in their names using the validation option, Top Gear US S02 has an episode called "The $500 Challenge" which will fail to move due to the '$' symbol. the default unraid mover should move it though, you can configure move tuning to use that if needed.

either rename them, or move them manually.

Is your docker image full?

The logs look like that might be the case.

One of the new mods there is going a bit far, I've been noticing it since they were added earlier this year.

once two of the old 2TB disks are upgraded to 4TB through the normal disk replacement/upgrade procedure for each disk one at a time, you should have more than enough free space to run the Unbalance plugin to scatter the data from the remaining 2TB disks to the new ones, then you can run a disk removal procedure.

Those steps are just as you have mentioned in the original post, but it is easier and safer to upgrade the existing disks first, less risks that way as we keep the parity valid and protecting you through the whole process. You can also upgrade a single disk, then unbalance to clear one old disk, then remove that old disk, then upgrade the second disk and repeat if you wanted to do reuse the old disks slightly faster in something else.

There are two ways to remove disks from the array once they are empty and the data is confirmed safely on the new disks, the easy way is to go to tools>new config then just don't map the old disks when you re-assign the disks, but that will require a parity rebuild. the other method zeroes out the disks to ensure the parity stays valid. both are details in the link above.

if the shares are set to "array" only the mover wont do anything, even though there are files in /mnt/cache/share it ignores them.

You need to set the shares to Cache>Array, so set primary as cache, secondary as the array, then the mover action to cache>array, then the mover knows it needs to clear the cache. now when you force run the mover it will notice there are files to be moved.

You CAN move them manually, but you need to ensure everything goes to the right spot and you are writing INTO the folders and not overwriting them, and you need to maintain permissions.
I would recommend not using --remove-source-files until you have copied everything and verified it is all good then format the disk. just in case something goes wrong.

Disable filename validation in the Mover Tuning settings to skip the filename validation checks.
 
$ and other special characters in filenames cause all sorts of havoc in Bash scripts and are best avoided if possible, but it is actively talked about in the plugin support thread.

Pretty sure that's just the containers own /dev/shm, the /transcode is there and the fact that it says 16G means its likely correctly mapped to the hosts /dev/shm, assuming you have 32gb ram?
 
Then in your plex transcode settings you have /transcode as the temp directory, so it should be working.

Not yet, that is a feature of OpenZFS2.3 which is still very, very new for public use. TrueNas got it included first because they helped the OpenZFS team get it to production.
ZFS expansion does still have a few caveats attached to it, it's not a magic bullet solution to ZFS's drawbacks but it does help massively.
 
It could be in Unraid 7.1 , but no guarantees on that as a lot of testing has to be done before jumping to that version.
 
 
For now, if you ahve a small ZFS pool and want to add a single disk, your best plan of attack is to dump the pool to the array or another pool, delete and rebuild the pool with the new disk, then move the data back. for small cache pools that is still pretty easy.

You should only put HDDs in the main array, SSDs should go in separate pools (standard cache setup as you mention), no you wont be able to have the SSD parity protected without adding at least one more matching SSD, or setting up the CA Appdata backup plugin for your containers which will backup that data to the array on a schedule, there are also ways to backup VMs in a similar manner.
 
Just keep in mind that if you want a parity protected array you will have to sacrifice the 14TB and only be able to use the 2x 4Tb and 2x500gb drives for data until you add more disks.
 
 

next to the path for Host Path 3, what does it say the container path is?
/data? /media?

well, it's pretty much as per that reddit post.
Get the executable sas2flash from here
 
get the firmware file 9207-8.bin from here (its in /Firmware/HBA_9207_8i_IT/ )
 
put them onto your boot USB, then boot up and either log in to the terminal on an attached monitor, or open the terminal from the webUI.
The unraid terminal is always root so be very careful to double check commands as you can do a lot of damage with it.
 
change directory to boot, which is the unraid usb
cd /boot here you can type 'ls' for a file listing to make sure the files are there if you want to check
copy the files sas2flash and 9207-8.bin from the current directory to /tmp (just a place to stick things)
cp sas2flash 9207-8.bin /tmp  
now we go to the /tmp directory
cd /tmp  
make sas2flash executable
chmod +x sas2flash  
now we can use sas2flash to flash the firmware
./sas2flash -c 0 -o -f 9207-8.bin  
That should do it, after a reboot you should be good to go assuming that known firmware bug was your issue, and i think it was.
 

the worrying lines are :
 
5 Reallocated_Sector_Ct PO--CK 093 093 010 - 17272 187 Reported_Uncorrect -O--CK 001 001 000 - 5725 197 Current_Pending_Sector -O--C- 098 097 000 - 1448 198 Offline_Uncorrectable ----C- 098 097 000 - 1448  
They should all be 0
 
shame to see a drive die at only 30k hours, but she's well cooked mate. stop trying to rebuild onto a broken drive, throw a new one in and rebuild onto that.
 

without a parity disk you cant do the standard disk swap procedure as there is no way to rebuild the data onto the new disk.
 
Definitely need to go the New Config route to get it to forget that 40gb disk ever existed and not have to replace it with a new disk.
 
Alternatively, add a parity disk now, let it rebuild, then you will be able to replace the 40gb with a proper disk after that.