I let the mover run overnight and only 40GB moved. I have another 140GB to move. But now it seems that hours can go by and only a few hundred MB will have moved. I tried to load up "unbalanced" to move it that way. But no luck. It wont get pas this:

Eventually that screen will be blank (the large dark box with "planning started"). I was able to move other data from one place to another, But trying to move data from the Cache to the array. Wont happen. I tried restarting unbalanced.

What have I tried on the server so far?

I rebooted more then once. I have all docker and VM stuff off. I have downloaded and reviewed the logs to no avail. I tried some googling and AI support. But nothing turns up why "my" issue is happening. The best I could track down was some folks saying that many small files on the cache can "just take forever" and "its the nature of the mover".

My cache pool is 2 disks (each 250GB) in raid 1. I checked the smart on the main drive. Its reported it was fine.

One final note. I have docker setup as a "filesystem" not the image file. This is the section that is taking forever to move. Its the only thing left on the cache. There is nothing above this folder.

My docker settings:

nachoserver-diagnostics-20250624-1837.zip

Edited June 24, 20251 yr by cardNull
Added docker information.

7 hours ago, cardNull said:

I have docker setup as a "filesystem" not the image file.

That's easily recreated, so no need to move it, and I would recommend recreating as an 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

10 hours ago, JorgeB said:

That's easily recreated, so no need to move it, and I would recommend recreating as an 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

Thanks JorgeB. I will try this tonight. Are you suggesting using a docker image file always or just this once? I moved to the "filesystem" because my image file kept filling up then throwing errors.

Just now, cardNull said:

I moved to the "filesystem" because my image file kept filling up then throwing errors.

This is normally a sign of something being written internally to a location in an image that should instead ideally be mapped instead to a location on the host.

Just now, itimpi said:

This is normally a sign of something being written internally to a location in an image that should instead ideally be mapped instead to a location on the host.

I went through every single container. I could not for the life of me to figure out how to find what was doing it. Is there a clear guide to solving that? Is there a reason that the "image" is a better solution?

16 minutes ago, cardNull said:

Is there a reason that the "image" is a better solution?

I've seen some strange issues happening with docker folders multiple times, like some containers not starting without a visible reason, etc., hence why I recommend an image

Just in case anyone was tracking this. I dumped everything on the cache. It was all "docker" image junk like @JorgeB and @itimpi said. Once I booted with the new cache disks I just configured docker again and added all my containers via "previous apps". I am good to go. Just need to figure out why my server keeps crashing now.