thedotlair

Thanks @trurl . I didn't realise that I had that configuration set as I always name my arrays 'store'. I've just cleaned up the configurations and run mover manually, a 1GB file that I created using DD and then manually invoking mover still resolved to the file remaining on the cache. All settings checked and reapplied as you suggested. Solved: I did though notice that the configuration on the USB was capitalised whereas the share configuration was all lowercase. Deleted the CFG, recreated the share and then ran mover when everything kicked into life. Now I feel totally dumb!! Thank you so much for your guidance though @trurl - very much appreciated your help on this one 👍 prometheus-diagnostics-20251128-1438.zip

I've recently swapped back to Unraid and having issues with Mover not doing it's job from CACHE to ARRAY. I've gone through a lot of threads, checked my config and ensured that things are as per the documentation (including TRASH guides) but to no avail. Hopefully kind souls (and with the patience of a saint!) can assist in resolving the issue. CACHE pool is 2x Intel DC Enterprise SSDs in RAID-1 (btrfs) - referred to as CACHE set as primary for the 'Store share' ARRAY is 4x Toshiba 18TB drives - referred to as 'ARRAY' and set as secondary storage using default settings I've gone through the config of MOVER as well as used MOVER logging plus tried to manually make files on the CACHE and then force mover to start (both GUI and CLI using mover start) but at no point does the cache move to the array, leaving the files unprotected. I'm not using the mover tuning plugin as I understand that's broken in 7.x and using Mover manually provides nothing in Syslog to indicate an error. Diagnostics attached and sincere thanks in advance for any posts/help provided. prometheus-diagnostics-20251128-1359.zip