erf89 Posted July 8 Share Posted July 8 (edited) I have the CA Mover Tuning plugin installed and setup to run at 85% full - was working no issue until today, I've updated to Unraid 7 beta, and now I can't get it work, and I also can't get manual mover to work either (I set "Move Now button follows plug-in filters" to No), also tried using the Move Now button inside the Share settings page, also no luck! Snip of syslog below, happy to provide any other diagnostics detail! Jul 8 00:55:21 emhttpd: shcmd (170): /usr/local/sbin/mover start |& logger -t move & Jul 8 00:55:21 root: Starting Mover Jul 8 00:55:21 root: Forcing turbo write on Jul 8 00:55:21 kernel: mdcmd (43): set md_write_method 1 Jul 8 00:55:21 kernel: Jul 8 00:55:21 root: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 0 0 0 '' '' '' '' '' '' '' '' 50 Jul 8 00:55:21 move: Log Level: 1 Jul 8 00:55:21 move: /usr/local/sbin/move does not exists, creating soft link Jul 8 00:55:21 move: ln: failed to create symbolic link '/usr/local/sbin/move': File exists Jul 8 00:55:21 move: mover: started Jul 8 00:55:27 move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 206: /usr/local/sbin/move: No such file or directory Jul 8 00:55:27 move: cat: write error: Broken pipe Jul 8 00:55:27 move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 119: /usr/local/sbin/move: No such file or directory ### [PREVIOUS LINE REPEATED 4 TIMES] ### Jul 8 00:55:27 move: mover: finished Jul 8 00:55:27 root: Restoring original turbo write mode Jul 8 00:55:27 kernel: mdcmd (44): set md_write_method auto I should add that as well as being on Unraid 7 as of today, a few days ago I also changed my cache pool to zfs from btrfs, however the Mover getting everything back onto the Cache at that point worked fine, and today is the first day I'm hitting my 85% again. Edited July 8 by erf89 Link to comment
MAM59 Posted July 8 Share Posted July 8 (edited) I would guess you need to wait for a plugin update. The path where "mover" is stored seems to have changed and the plugin is not able to find the program anymore. type "which mover" in a shell to see where the program is currently located. But from the logs you see, the plugin is trying to create a symlink and fails. Better deinstall it for now and wait for an update. Edited July 8 by MAM59 Link to comment
kelsiersghost Posted July 8 Share Posted July 8 (edited) I'm having the same issue on version 7 as well. When I type in > which mover It tells me /usr/local/sbin/mover It looks like a spelling error - move vs mover. When I look in the /sbin folder, there are files BOTH called move and mover. For some reason the call is looking for move, so changing the file name isn't going to work. Should I just downgrade? Edited July 8 by kelsiersghost Link to comment
SimonF Posted July 8 Share Posted July 8 51 minutes ago, kelsiersghost said: I'm having the same issue on version 7 as well. When I type in > which mover It tells me /usr/local/sbin/mover It looks like a spelling error - move vs mover. When I look in the /sbin folder, there are files BOTH called move and mover. For some reason the call is looking for move, so changing the file name isn't going to work. Should I just downgrade? there are two part move and mover. move location has changed. There is a work around on the plugin page. Link to comment
Recommended Posts