I have read through the support topics I could find here and on Reddit. This is a common issue it seems, and the common solutions are not working for me. I do not have the mover tuning plugin(s), never have (I tried installing one to see if it would fix the issue, it didn't, and I removed it). I have triple checked that all of my share names match the share.cfg file names on the flash drive. I double checked that useCache is enabled on all of the shares in the .cfg files. I turned on mover logging and it just says started and then finished immediately. I have tried rebooting the server several times in this process as well.

Despite my best efforts, my cache drive is still sitting at 97.7% full and won't accept new files, nor will the mover clear the cache disks no matter how many times I try. Any other suggestions?

Please post the diagnostics and the name of the share(s) you expect to be moved

Thanks for the response. I believe diagnostics are attached.

Cache/Cache2 pool is supposed to auto move all of its' contents at 2am every day to all of the other non-default shares (the ones I created anyway) - Bryan, Saralyn, Shared, and Cloud Backuptower-diagnostics-20250707-0759.zip

1 hour ago, albrittbrat91 said:

Bryan, Saralyn, Shared, and Cloud Backup

From these, only Shared has data on the pool, the share is set to cache=yes, but it doesn't have the pool name, reapply the share settings, or updated to 7.1.4, it includes a fix for older shares.

I appreciate the responses.

The data in the cache pool is waiting to be written to Shared only, sure, that makes sense.

'it doesn't have the pool name, reapply the share settings' - no clue what this means.

I updated to 7.1.4 and rebooted, and then hit move, and now the mover is running correctly, so that is the solution as far as I can tell.

Thanks for the help!!!

On 7/7/2025 at 12:20 AM, JorgeB said:

Please post the diagnostics and the name of the share(s) you expect to be moved

hello i am having this issue also. my mover randomly stopped working on 7.0.0 and is not working even after i updated to 7.1.4.

for some context, i just had an issue with a docker container bulk moving files from my hdd array into my ssd. i stopped the docker before my ssd filled and was able to trigger the mover last night. this morning i let the docker continue its move operation (there is no way to cancel it) and stopped it again prior to filling my ssd. im trying to trigger the mover again and getting this error:

emhttpd: shcmd (191): /usr/local/sbin/mover start &> /dev/null &

and i have attached my diagnostics zip

randy-unraid-diagnostics-20250718-0903.zip

10 minutes ago, Randyd718 said:

and the name of the share(s) you expect to be moved

5 minutes ago, JorgeB said:

  16 minutes ago, Randyd718 said:

and the name of the share(s) you expect to be moved

i am expecting my data share to be moved from cache/ssd to array/hdd. i have just now flipped my data share to primary array in order to stop filling the cache drive while this docker operation finishes itself off

35 minutes ago, Randyd718 said:

i am expecting my data share to be moved from cache/ssd to array/hdd.

# Share exists on disk1, disk2

It only exists on disks 1 and 2, so there is nothing to move.

Just now, JorgeB said:

# Share exists on disk1, disk2

It only exists on disks 1 and 2, so there is nothing to move.

hmm ok. so i guess docker shoving all my files from array -> appdata means they are on cache, but unraid thinks that everything on cache belongs on the cache. i guess that is obvious now that you say that.

ive triggered a move manually from cache/appdata back over to the array. thank you!

Edited July 18, 20251 yr by Randyd718