February 17, 20251 yr Hey everyone, I hope you can help, I was getting notifications that my cache was getting full so I tried to run the mover manually and in the logs it just shows : Feb 17 09:17:21 emhttpd: shcmd (1576155): /usr/local/sbin/mover start &> /dev/null & I'm getting some errors about the [Appdatabackup] and when I check the Fix Common Problems I see it says "Unable to write to Docker Image" - Docker Image either full or corrupted, I hope you can help. This is 7.0.0 diagnostics-20250217-0922.zip
February 17, 20251 yr Community Expert Delete and recreate the docker image: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Then: https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks Ten reboot, enable mover logging, run the mover and post new diags together with the name of the shares you expect to be moved
February 17, 20251 yr Author I did all of that, things are looking a bit better, but the mover still seems to not be moving things. I enabled the logging and started the mover. As an example one share I expected to be moved is called "Cloud" diagnostics-20250217-1323.zip
February 17, 20251 yr Community Expert Solution That share doesn't have a pool in the cfg file, probably was created with an older Unraid version and never updated, click on it, set primary=cache, secondary=array, apply and rerun the mover.
February 17, 20251 yr Author Thank you, that looks like that fixed it, I went and updated a bunch of shares that were also set incorrectly from the upgrade
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.