I'm not sure what I'm doing wrong.  I've been using Unraid for serveral years now, and it's never really choked like this.  My cache pool is completely full, and whenever I try to run the mover the log says "mover is running" but clearly it's not.  When I watch my "MAIN" tab, I can see the activity on the pool, and there is no data being read or written on either the array or the cache pool.

 

I was using a CA that added some mover tweaks.  I disabled that app so I'm using just the default mover.  I also enabled the mover log.  It definitely reports that it's running but nothing is actually happening.  I thought maybe I had some docker or VM that could be interfering so I stopped all that and disabled the docker/vm managers.  Still same results.  I then decided to try and just do a reboot, thinking maybe there is some stale file in use that's locked things up.  When the system came back it wanted to do a parity check (odd also).  I cancelled the parity check, attempted to run the mover manually again with the same results.

 

That's when I decided to come here and post a thread seeking help.  Any ideas?  Attached is my complete diagnostics support package.kyber-diagnostics-20250116-1741.zip

 

 

Well shucks.  I uninstalled the ca.mover.tuner app, rebooted, and tried to manually start the mover again.  And wouldn't you know.. it's working now?  Not sure what's going on.  I'll try to let this go and if I see a problem (or not) I'll report it.