hugenbdd

Yup, backup somewhere else and just rename. If there is an issue you should be able to rename back to capital and I will try to come up with a solution in the plug-in.

Was the name ever changed? Check out this directory. ls -ltr /boot/config/shares/ There is probably a Media.cfg file instead of a media.cfg file. Make a backup someplace else and rename the file.

would be under /var/log directory. in syslog or possibly syslog.1 Without seeing the log it is hard to tell what caused it to move everything. I highly suggest using test mode with logging enabled to get the config how you want.

Need to see the logs and the associated find commands. You can run the find command (Minus the | /usr/sbin/mover piece) to see what files it will be/is moving. I have a release coming up in the next few weeks that changes to a file list, so when testing you can review the file list instead of logs. (also will support GUI if your willing to change internal files)

They go to the syslog, which you can see with the log icon (upper right). if you hover over it, it will say log. (Next to the ?) 85%, Update your "Move All from Cache-yes shares pool percentage:" from 80 to a higher % then. Probably around 90 or 95%. Or just don't use it.

You can also set a few things to review logs instantly. 1.) Enable Logs (top of page) 2.) Move Now button follows config: Yes (Near bottom) 3.) Test Mode: Yes (Last option at bottom) Then hit move now. Review the logs to make sure your options are acting how you expect. Once you have it set to your liking, set the test mode to No.

This was frustrating. Didn't notice it in the newletter, didn't see any posts even on reddit... No warning that if you have capitals in your email address, (like I usually type it out) then logging in probably won't work. At least didn't for me. I changed to all lowercase letters with my email after a password reset, auto generated by chrome, and it finally let me in. Hopefully others find this useful. Or unRaid can add a "tolower" in their code. FYI, more prominent "Contact Us" would have been helpful, even just an email address.

Looking for a few testers with the following. 1.) Basic understanding of bash/shell (To install the files and change their permissions. chown, chmod etc...) 2.) That have mover tuning plug-in installed. (Preferrable have been using it for a while) (Required as the GUI update file is created based off this plug-in). 2b.) Have unRAID 6.11.3 or above installed. 3.) That can test moving files off cache shares to the array. 4.) That can test moving files TO cache pool FROM the array. 5.) Bonus - if you have multiple pools to test with.

Looking for a few testers with the following. 1.) Basic understanding of bash/shell (To install the files and change their permissions. chown, chmod etc...) 2.) That have mover tuning plug-in installed. (Preferrable have been using it for a while) (Required as the GUI update file is created based off this plug-in). 2b.) Have unRAID 6.11.3 or above installed. 3.) That can test moving files off cache shares to the array. 4.) That can test moving files TO cache pool FROM the array. 5.) Bonus - if you have multiple pools to test with.

I think I'll be able to provide info that is needed for the GUI portion in an update to mover tuning to allow this. (Move based on a filelist instead of a "find") I still have a ways to go, but hopeful to have the base info needed in a few days. Implementing the GUI portion I will need help with though.

"Move All Cache Threshold: 5" Might be a bug somewhere so that the right value did not get saved in the config file. Try changing from 55% to 60% and hitting apply.

Yes, each rule is logged when it's triggered. If you have logging enabled, and run in test mode, you can then review the logs and change your rules accordingly. Also, if you set the "Move Now button follows Rules" then you can make lots of edits very quickly by hitting the move now button.

Would need to see some of the mover log entries. Mostly the individual find commands for each share.

Correct. Mover doesn't run until it's scheduled time. Once it is kicked off based on the schedule, the first thing it does it check the % used, if it reaches the threshold it will continue to move files, if the % used is less than the threshold, it will not move files.

You could setup a cron job to stop it with the command below. This should provide a "soft" stop of mover. mover stop