Masterwishx

Do you have /tmp on flash drive? In next version will be option to change parent folder logs location + age for logs and list files

Looks fine will move after 75% until 0%

What the path of ignore file?

Post logs and debug logs

I think only primary and the secondary

Is this dataset or folder on zfs? Post the logs

Asus answered today after a couple mails: ``` Hello again, Based on your description, it seems that the issue might be related to the external speaker rather than the firmware of a specific motherboard. In any case, we will look into this matter, and if such a bug exists, it will be fixed in future updates. We recommend keeping your BIOS updated regularly to ensure the proper functionality and stability of your motherboard. Thank you, and have a great day! ```

Did you got any answer from vendor? Seems they can't help in such issue.

The original version broken if you have unraid connect plugin, new author fixed but still no update on CA, only install from github. It's best to read a couple of last pages to be updated what's going on 😉

@Squid @VladoPortos still no plugin in Ca ? can be added maybe as xml file availible in github?

Thanks i will post also here, hope it can be fixed in it

It's also count array files if moved/synced

Check the log file it's what you have in it.

If you have cache:only for shares you don't need to move data then?

This mean you don't have user0 as diskX, only cache and one pool only

you can already : Disable Mover running on a schedule =yes then run `/usr/local/emhttp/plugins/ca.mover.tuning/age_mover start`

Check the new version

You can download age_mover file and copy to /usr/local/... and `chmod 755 age_mover` or you can wait I will push new version today I hope...

Fixed issue with wrong thresholds for cache:yes , you can check it by download and test : https://github.com/masterwishx/ca.mover.tuning/blob/dev-new-fixes-4/source/ca.mover.tuning/usr/local/emhttp/plugins/ca.mover.tuning/age_mover

That's will be really amazing

Do you have this issue with cache:yes when primary cache- > secondary cache2 ?

If you still have this issue please open issue in github I will try to solve it

I meaned to make global threshold for cache prefer like now fill up upto 95% but users maybe want change it?

Without mover logs debug log it's impossible to know whats wrong