I've been trying to use Mover to move some shares off my cache drive so I could upgrade it. I ended up with some duplicate files in both the share and cache drive, so I was manually trying to remove duplicates from the cache drive. I enabled mover logging to see what file it was getting stuck on, and my workflow was like this:
Start mover from GUI and watch logs until it stops
terminal: mover stop
terminal: rm /mnt/cache/[file that is stuck]
Start mover from GUI and watch log
Not sure if it's relevant, but the share I was working through is docker and the files I was removing were called either fifo or control. Docker is currently disabled.
This was working for a while, but after stopping and removing a file, mover wouldn't start from the GUI. I rebooted the server which came back normally, but mover still wouldn't start. Digging more, I've noticed I cannot access /mnt/user in the terminal, but I can access /mnt/diskX or /mnt/cache and see files. I tried to run a parity check but get the same issue as mover - it won't start. The GUI just hangs after clicking the button.
I tried to grab a diagnostics zip file, but that has been running for about 30-45 mins and hasn't completed (it did start and show progress, not sure if it takes that long to run or not).
I'm a bit out of my depth here with recovery and don't want to make the situation worse. Currently running version 6.12.3