Masterwishx

You can get debug.zip in help menu of plugin or in cli by "mover debug"

Yep after 70% move threshold

First you need more gap between thresholds if have big files. If you say it move after 40%, enable logs and debug wait when mover run then post debug.zip

Post your config

Not sure what Javascript function runned when move now button pressed not founded in php. IIRC when checked in htop there is no parametr (parent proccess) howere it should be (emhttp, shcmd) sended with mover.php when mover button pressed, so you can see in syslog when debug enabled (bash,crond or button pressed (if blank parametr ) in code.

You can see all parameters by "mover help". So you can run "mover start" it will call age_mover start or mover.old start whatever setting you have. Similar like cron run it or mover button when pressed. Also you can run age_mover or mover.old directly by start parameter.

This plugin rename mover to mover.old for it can be runned by mover , that's all. Unraid mover also had/has bugs that was/will be fixed so... Just try it.

You can check Rsync or move what work better for you. But folders deleted after files was moved and if only empty folders...

This should not happen, I will check your debug.zip

Check new version

What is current settings?

2025.06.14 version Update - fix: Fix age_mover is missing the "start" parameter in the cron schedule when force move is enabled. **_(masterwishx)_** - fix: Remove renaming of "mover.cron" to "mover.cron.disabled". No longer necessary with previous version.

Every update im trying to fix bugs and add new futures so ....

Some old code + new code coused issue ... i pushed to github if interesed : https://github.com/masterwishx/ca.mover.tuning/pull/71/files

will be fixed in new version

Yep I got it, this should not happen, I will check it

This should run mover.old not related to age_mover

I will check it

Just in case maybe you tryed reset settings?

So if you install new version with current settings you have error? Anyway I will fix it in new version and maybe will remove this part (with renaming cron file) as another fix avaliable in last version for crond

if you see cron error message : Error: Mover cron file does not exist this mean: you have disabled the plugin on shedule mover.cron.disabled) then you changed mover schedule time -> that recreated file to mover.cron and then you have enabled schedule but file was already mover.cron So just enable schedule for plugiun and change cron time for Mover it will recreate `boot/config/plugins/mover.cron` or rename it manually and run update_cron

Changing mover scheduling will recreate cron file

I will check it

Users on 6.x was complain that emhttp calling mover without start parameter

No other users was complaining for it, but good to know what /how it's broken in your case...