Ran mover to try and move everything off my cache drive onto my array.

Did not stop Docker service before doing so.

All of my containers show stopped now and icons are gone for them. Unable to restart them as it cannot find.

I also still have ~23GB of stuff still on my cache drive that did not move. When I try to run mover again, it says file exists and then eventually gets to a point where it hangs and I have to manually stop it.

My current state is that I have the Docker service disabled now, have not done anything else.

2 problems I am trying to solve are:

1. Figure out how to move the rest of the files off the cache drive onto the array safely.

2. Fix all of my containers that broke and get them running again off the array only.

Diagnostics are attached. Many thanks for the help in advance.

erasmus-diagnostics-20250822-1927.zip

1. Go to settings->Docker and delete the docker.img file.

2. If mover won't move the files off the cache drive, do it manually from the file manager in the web ui or use Midnight Commander (mc) in the terminal. I personally prefer mc. Overwrite any existing files.

3. When everything is moved, go to settings->Docker again and start the docker service, it will recreate the docke.img file. If you want it on the array you need to change the location first.

4. Go to Apps -> Previous Apps and reinstall all your containers.

But why do you want your docker containers running on the array anyway? Performance will suffer, it's highly recommended to have it on the cache drive.

Thank you for the reply and guidance @strike . I am reinstalling the containers now.

As for your question why I want them running on the array - it is a temporary measure. I am setting up a new Unraid system side by side as I have made many changes over the years on the existing one and want to have a fresh start. I needed to empty this cache drive from the current system so I can add it to the new system. Once I migrate data over there I will continue to use cache pools again.

Ah, I see :)

Oh, I forgot one thing. You also need to update the config mappings in your container templates, where the appdata for the containers is since they are now on the array. And any download loactions for your downloaders/*arrs.

Edited August 23, 2025Aug 23 by strike

@strike I think in my case I am good and dont need to do that.

I had appdata set before as cache primary and array secondary storage using the path mnt/user/appdata. I think due to this the path already existed in both locations.

After I moved everything off the cache drive I changed to array as primary storage and no secondary storage.

Once I restored the containers everything was already pointing to the correct place. Checking everything out now and it all generally looks good - just have to make a few fixes due to something happening with my custom network.

Awesome, then you're good.