I recently upgraded my server with a new Motherboard, Processor, Etc. Because the new motherboard has M.2 slots I also upgraded my Cache pool drive to a 1TB NVME Drive.

 

I thought everything was fine until I had an incident where my Cache drive filled up. It was then that I realized that Mover isn’t working. I have not been able to get Mover to start no matter what I have tried. I have tried to troubleshoot this problem online but there seems to have been a recent change to the mover settings page and the advice on how to trouble shoot this problem is based on the old screens.

 

Any help trouble shooting this problem would be appreciated. I have included a troubleshooting file and the shares in question are pretty much all of them.

enterprise-diagnostics-20241120-1622.zip

you are running beta 4 this is a known issue.
 

 

Edit your go file at: /boot/config/go and add:

rm /usr/local/sbin/move

ln -s /usr/libexec/unraid/move /usr/local/sbin/move

I am using Beta 4 but this did not seem to solve my problem! I saw that Removing Mover tuning would fix the problem. Do I need to those line I add to the go file if I remove Mover Tuning?

 

Edited November 21, 20241 yr by Captain351

its hit an miss. i recomend having the mover tuner plugin installed and have this in teh go file at each boot. this has been the fix for every issues I have seen when people have posted about problems wioth mover. JorgeB claims this isn't a problem if you don't have the plugin installed. It is noted in the support forum on teh mover tuner plugin as well probaly burried now...

IDK the ramafication of removing the plugin and restart as beta seems to have some presiten confgs. There are quite a few beta 7 bug reports on this as well.

hit and miss trial and error. sorry

I removed Mover Tuning and removed the new lines from the go file and it works now.

 

bmartino1 Thanks for your help. I wouldn't have known to was a bug without you.

Edited November 21, 20241 yr by Captain351