I can't get this to work on my array. It "starts", but immediately ends. Is this dependent on any other plugins, like CA Mover Tuning? I'm guessing something is failing, but unsure where to check to diagnose.

Automover session finished - 2025-10-06 11:30:01
Mover finished
Starting mover
Usage exceeds threshold!
cache usage:  87% (Threshold: 70%)
Automover session started - 2025-10-06 11:30:01

The syslog has nothing helpful.

Oct 6 11:30:01 AERIS root: 🔄 Automover Wrapper: Starting mover
Oct 6 11:30:01 AERIS root: ✅ Automover Wrapper: Mover finished

@foamy it might be worth posting your system’s diagnostics zip file and the name of a share you expect to move. Quite frequently issues of the sort you describe are caused by incorrect share configuration.

23 minutes ago, itimpi said:

@foamy it might be worth posting your system’s diagnostics zip file and the name of a share you expect to move. Quite frequently issues of the sort you describe are caused by incorrect share configuration.

curious on what this comment is in reference too as apart of my plugin? i don't see foamy having written messages here

Possible to add age related moving and to disable size thresholds?

2 minutes ago, Seraphys said:

Possible to add age related moving and to disable size thresholds?

disabling is essentially already allowed by just putting 0 for the threshold %, age related i looked into at one point and struggled with it but i might give it another go at some point as it would be an addition i'd like as well

That would be nice. Tbh mover tuning at this point has become so big and bloated it gets very borky after a while.

24 minutes ago, Seraphys said:

That would be nice. Tbh mover tuning at this point has become so big and bloated it gets very borky after a while.

yea it's what got me started with this plugin actually. my wants are threshold, it's own scheduler, logging, move by age, and exclusion list. not sure if i'll get age or exclusion or not but gonna try

Edited October 6, 2025Oct 6 by jcofer555

1 hour ago, jcofer555 said:

i don't see foamy having written messages here

He did (probably hidden initially) !

Looked to me as if it was possibly a share not configured correctly to be moved rather than a plugin issue.

28 minutes ago, itimpi said:

He did (probably hidden initially) !

Looked to me as if it was possibly a share not configured correctly to be moved rather than a plugin issue.

ah yea must have been hidden, i see it now and agree likely share not configured correctly.

Not sure why my post was alluded to at the same time it was not visible...

So yeah, attempting to use Auto Mover. It "starts" mover, but nothing happens and the mover process ends in the same second. The share I expect it to evacuate is "media", the m----.cfg config file. I tried installing CA Mover Tuning as well, but don't think I should have. I'm unsure if removing it will completely reverse whatever it tuned.

I'm attaching the diagnostic export (anonymized).

aeris-diagnostics-20251006-2120.zip

Edited October 7, 2025Oct 7 by foamy

4 hours ago, foamy said:

Not sure why my post was alluded to at the same time it was not visible...

So yeah, attempting to use Auto Mover. It "starts" mover, but nothing happens and the mover process ends in the same second. The share I expect it to evacuate is "media", the m----.cfg config file. I tried installing CA Mover Tuning as well, but don't think I should have. I'm unsure if removing it will completely reverse whatever it tuned.

I'm attaching the diagnostic export (anonymized).

aeris-diagnostics-20251006-2120.zip

you don't have the share setup correctly to use mover, you need to have primary storage set as cache, secondary storage set as array and mover direction cache -> array. mover tuning being uninstalled will reverse whatever was tuned, best to reboot unraid after removing it though

This forum won't let me edit my recent post. I'm guessing my issue here is that the mover binary got nuked as part of this plugin install/troubleshooting effort. Both the backup and the in-use one are 0 bytes...

root@AERIS:/usr/local/sbin# ls -al *mover*

-rwxr-xr-x 1 root root 0 Oct 6 23:33 mover*

-rwxr-xr-x 1 root root 0 Oct 6 23:30 mover.automover*

16 minutes ago, jcofer555 said:

you don't have the share setup correctly to use mover, you need to have primary storage set as cache, secondary storage set as array and mover direction cache -> array. mover tuning being uninstalled will reverse whatever was tuned, best to reboot unraid after removing it though

It is set up that way, and that never changed. Unless the mover binary is supposed to be 0 bytes, that's my issue. Something in this setup/t-shoot 0'd that, otherwise.

12 minutes ago, foamy said:

This forum won't let me edit my recent post. I'm guessing my issue here is that the mover binary got nuked as part of this plugin install/troubleshooting effort. Both the backup and the in-use one are 0 bytes...

root@AERIS:/usr/local/sbin# ls -al *mover*

-rwxr-xr-x 1 root root 0 Oct 6 23:33 mover*

-rwxr-xr-x 1 root root 0 Oct 6 23:30 mover.automover*

what version of automover?

6 minutes ago, jcofer555 said:

what version of automover?

The one released on October 6. I'm going to do a reboot of the server, to see if that will restore the base binary.

1 minute ago, foamy said:

The one released on October 6. I'm going to do a reboot of the server, to see if that will restore the base binary.

it should fix it if you reboot, if it doesn't let me know

Edited October 7, 2025Oct 7 by jcofer555

8 minutes ago, jcofer555 said:

it should fix it if you reboot, if it doesn't let me know

Yeah, it restored the Unraid stock mover script on reboot. I had to manually clean the automover plugin from USB, then reinstall it. It seems happy now, and I see content being moved to the array. I didn't realize that the whole base linux OS is basically just running in memory, not form the flash itself. Learned a few things, today, so, all's good. Thanks!

4 hours ago, foamy said:

Yeah, it restored the Unraid stock mover script on reboot. I had to manually clean the automover plugin from USB, then reinstall it. It seems happy now, and I see content being moved to the array. I didn't realize that the whole base linux OS is basically just running in memory, not form the flash itself. Learned a few things, today, so, all's good. Thanks!

added some safety checks for modifying the schedule to hopefully prevent future 0kb mover binaries

am i right that this will move every data on every share which is set to cache->array? how about an option for selecting which share should be moved or should be movey on which threshold?

thanks for that nice and clean plugin. mover tuning was getting just too overloaded.

3 hours ago, mloTek said:

am i right that this will move every data on every share which is set to cache->array? how about an option for selecting which share should be moved or should be movey on which threshold?

thanks for that nice and clean plugin. mover tuning was getting just too overloaded.

this uses the built in mover so when it "moves" it moves all shares based on the shares settings just like if you used the regular mover, what this plugin does is offers the ability to prevent the mover from running unless the selected pool meets the threshold and then offers logging for which files were moved on or off the selected pool. i don't think there is a way i can offer to pick which shares to move with how the plugin uses the built in mover it would have to be a customized mover using rsync like mover tuner uses to do that which i don't plan to dive into

is it possible to get the mover running on just one cache pool instead of my two. I have a smaller one for downlaods (500GB) a bigger one (1TB) for vm, dockers and so on. Currently I am running 2 user scripts with different threshold levels but when the mover is triggred it runs on both pools. One script checks my zfs maybe this can help you to check the right %level of the zfs pools from the other comments.

Thanks

9 minutes ago, Bob@unraid said:

is it possible to get the mover running on just one cache pool instead of my two. I have a smaller one for downlaods (500GB) a bigger one (1TB) for vm, dockers and so on. Currently I am running 2 user scripts with different threshold levels but when the mover is triggred it runs on both pools. One script checks my zfs maybe this can help you to check the right %level of the zfs pools from the other comments.

Thanks

that's how the new version i put out the other day does it actually :) so if you are on the newest version then that's how it'll work for ya

15 hours ago, Bob@unraid said:

is it possible to get the mover running on just one cache pool instead of my two. I have a smaller one for downlaods (500GB) a bigger one (1TB) for vm, dockers and so on. Currently I am running 2 user scripts with different threshold levels but when the mover is triggred it runs on both pools. One script checks my zfs maybe this can help you to check the right %level of the zfs pools from the other comments.

Thanks

just added age based moving as well, working on more stuff too

Hi,

I checked the "Disable Unraid Mover" box, but the normal mover keeps moving the files into the array, even though the cache fill level hasn't been reached, nor are the files old enough.

I've had the mover write the files back to the cache several times, but during the nightly run, it pushes them back even though Automover is enabled.

2 hours ago, cnvscgn said:

Hi,

I checked the "Disable Unraid Mover" box, but the normal mover keeps moving the files into the array, even though the cache fill level hasn't been reached, nor are the files old enough.

I've had the mover write the files back to the cache several times, but during the nightly run, it pushes them back even though Automover is enabled.

the removal of unraid mover has been removed from this plugin due to the complexities of how it needs to be implemented

Edited October 20, 2025Oct 20 by jcofer555