May 22, 20251 yr Morning all and thank you for your time.When I first updated to 7.0 mover didn't work and I rolled back to 6.15.12 and all was well.Fast forward to a couple days ago, updated to 7.1.1 and I thought it was good. Checked yesterday and cache was full, mover not moving. At the time it was scheduled for hourly moves with mover tuner uninstalled, same as it was on 6.15.12Saw the 7.1.2 and updated.Still nothing moving.Disabled docker. VM is and has been disabled throughout this issue. Reboot try again. Full cache, nothing moves.Here is the current diagnostic outputFor fun I installed mover tuner, turned off test mode, and gave it a try. That diagnostics is attached also, 0311Any ideas what I've mucked up? Thanks again for your time and expertiseunicorn-diagnostics-20250522-0846.zip unicorn-diagnostics-20250522-0311.zip Edited May 22, 20251 yr by troglodytis
May 22, 20251 yr Community Expert Enable mover logging, run the mover, post new diags and the names of the share(s) you expect to be moved.
May 22, 20251 yr Author Thanks for stepping up.Mover Logging was enabled for both of those moves. I triple checked that it is still enabled, tried to move again, and grabbed the attached diagnostics.I am expecting /data to moveunicorn-diagnostics-20250522-0932.zip Edited May 22, 20251 yr by troglodytis
May 22, 20251 yr Community Expert Solution It's a case issue, delete /boot/config/shares/Data.cfg, then click on the data share, reapply the settings and re-run the mover
May 22, 20251 yr Author Followed your instructions and mover is now doing its thing.Thank you so much!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.