I suspect I'm having issues with my SATA cache SSD because I have spotted errors in the log here and there recently. I ran a short smart test and it says OK, though I did not run an extended test. Moving files on and off the drive is still working fine for now. I installed a new NVME SSD, (it's still unassigned currently) and want to set it up to be the new cache drive.

I set all my shares to use the array, however mover isn't moving anything to the array. Docker and VM is disabled. Mover logs just say start, and stop. Am I missing a step?

zeus-diagnostics-20250613-1403.zip

Nevermind! Figured it out.

Had to set to use cache as primary, and move to the array. Setting save location to array doesn't move files apparently.

4 minutes ago, moose1207 said:

however mover isn't moving anything to the array.

For mover to move anything you need the pool set as primary storage, the array as secondary storage and mover direction as pool->array.

If you only have primary storage set (as seems to be the case) then mover takes no action and leaves files where they are.

Just now, itimpi said:

For mover to move anything you need the pool set as primary storage, the array as secondary storage and mover direction as pool->array.

If you only have primary storage set (as seems to be the case) then mover takes no action and leaves files where they are.

Yea, the options are not super intuitive. After clicking around I finally saw it list the mover actions. Is there a reason why mover ignores files that list the array as primary location?

Thanks for the assist!