So I've updated from 6.12.15 where mover was running great, tried 7.0 where my cache overfilled. Due to a lack of time on my part, I reverted to 6.12.15 just to get things going again. skip to now and I've done a bit of research regarding the issue, uninstalled the tuner plug-ins, updated unraid to 7.1.2 figuring some bugs may have been hammered out but once again I'm running into the same issue.
After scouring the forum I've seen folks have luck with a "rename shuffle" on my shares (change their name and then change back again to update the cdg) just in case it was due to share names being capitalized but that's not worked but that's not achieved anything either. Trying to run the mover from the terminal just gives the non-descript messge:
<disk_name> must match pattern 'disk[0-9]*' and /mnt/<disk_name> must be a mountpoint

Can anyone shed some light on where thing's are going wrong?

megavault-diagnostics-20250517-1015.zip

Update: so what I did was open the new file manager built into unraid, navigated the to cache, moved the files that were meant to be on the array over to one of the emptier array disks essentially doing the movers job for it... since then it's been behaving and my cache drives have been sitting between 4% and 50%.
I still have no idea if this was the actual thing that fixed this or if one of the hundred other things I did fixed it?

Edited May 24, 20251 yr by elstevo2
Update to show issue solved

enable mover logging, run the mover and post new diags, as well as the share name(s) you expect to be moved.

Done and done good sir,
I'm expecting my shares to do this:
I have two pools currently, one called App-data which is, as the name suggests, a pair of NVME drives for storing app data and the cache is a pair of 2.5" SSD's for everything else in use that's no on the array

 

megavault-diagnostics-20250517-1903.zip

Edited May 17, 20251 yr by elstevo2

According to the diagnostics once you removed the Mover Tuning plugin then mover started moving lots of files.  It eventually stopped with an error:

May 17 19:02:41 Megavault move: error: move, 335: No such file or directory (2): lstat: /mnt/cache/media/Audiobooks/Books/Anne Rice/The Vampire Lestat
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May 17 19:02:41 Megavault move: skip: /mnt/cache/system/libvirt/libvirt.img
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May 17 19:02:41 Megavault move: mover: finished

and it is not clear what that error is caused by.

 

If there are still files that you expect to be moved present on the cache it might be worth checking that they are:

• not open
• not duplicates of files already on the array

as either of these would stop them being moved.

Hi Everyone

anybody figure it out, I have same issue

I started noticing it after I uninstalled ZFS master plug-in

attaching diagnostics

Thanks In Advance

trooper-diagnostics-20250524-0113.zip

9 hours ago, captpower said:

I have same issue

On 5/17/2025 at 7:54 AM, JorgeB said:

enable mover logging, run the mover and post new diags, as well as the share name(s) you expect to be moved.

Update regarding my case

I didn't have Mover Tuner installed

it turned out my Unraid USB Flash had some issue after replacing it everything back to normal and mover started normally

Thanks