I recently upgraded my motherboard, processor, added an LSI 9211 as well as 2 drives. After the rebuild, I noticed that my 1 TB cache drive was nearly full. I thought there must have been files that hadn't been moved to the array from before the upgrade when my storage was nearly maxed out. I activated Mover and let it do its thing.

After returning to my computer, the cache drive was still nearly full but now the Docker page cycles with the Unraid loading symbol but does not fully load the page. I'm not sure what I did or how to undo it. Any help is appreciated.

tower-diagnostics-20250910-2109.zip

There appears to be a container constantly restarting and spamming the log. Check their uptimes to see if you can find the problem one and resolve that, then reboot and post new diags after array start.

5 hours ago, JorgeB said:

There appears to be a container constantly restarting and spamming the log. Check their uptimes to see if you can find the problem one and resolve that, then reboot and post new diags after array start.

Thanks, @JorgeB . I'm unsure about how to check container uptimes. Where would I go to do that?

Nevermind. It looks like it might be Cloudflare. That one had an uptime of 18 seconds. Is there a way to uninstall a container when the Docker page will not load?

Edited September 11, 2025Sep 11 by rockbox948

docker container stop <name> should do

@KilrahThanks!

The issue persists.  I've attached the logs from after the change but before rebooting and then after rebooting, just in case it makes a difference.

tower-diagnostics-20250911-0836.zip tower-diagnostics-20250911-0905.zip

Now enable mover logging, run the mover and post new diags, together with the share name you expected to be moved.

Activated Mover and it would be the Downloads share that I would expect to be moved.  It looks like the majority of the space taken on the cache is actually for my VMS.  That make sense now.  However, the Docker page still isn't loading properly.

tower-diagnostics-20250911-1917.zip

There's appadata on the array trying to be moved to cache and failing due to files already existing there. Because of that spam, nothing else is getting logged regarding the mover, recommend fixing that.

As for docker, it appears to be started. Post a screenshot from the docker page.

I believe I found the offending folders/files. However, some of them will not let me delete them using Krusader even after I have removed the docker container. Shouldn't the system let me delete the folder of the container is no longer active?

3 hours ago, rockbox948 said:

I believe I found the offending folders/files. However, some of them will not let me delete them using Krusader even after I have removed the docker container. Shouldn't the system let me delete the folder of the container is no longer active?

Try using the Dynamix File Manager built into Unraid 7 instead.

On 9/13/2025 at 4:34 PM, itimpi said:

Try using the Dynamix File Manager built into Unraid 7 instead.

Thanks. I did that to delete the extra appdata folders on the array but the Docker page still refuses to load properly. The containers are active and seem to be functioning, it's just that the Docker page is misbehaving.

Any other thoughts on what could cause this issue?

6 hours ago, rockbox948 said:

Docker page still refuses to load properly.

On 9/12/2025 at 8:26 AM, JorgeB said:

As for docker, it appears to be started. Post a screenshot from the docker page.

On 9/15/2025 at 1:26 AM, JorgeB said:

  On 9/14/2025 at 6:35 PM, rockbox948 said:

Docker page still refuses to load properly.

  On 9/12/2025 at 2:26 AM, JorgeB said:

As for docker, it appears to be started. Post a screenshot from the docker page.

lol, I missed the screenshot part.

So the issue is the Unraid logo, it keeps showing that?

On 9/17/2025 at 1:48 AM, JorgeB said:

So the issue is the Unraid logo, it keeps showing that?

Correct. It continues to show the page as loading but never stops. I let it run undisturbed to see if I just wasn't patient enough. Two days later it was still doing it.

With the loading screen active, I am unable to make any changes to anything on this page.

Try recreating the Docker image

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

Thanks. I will try to test this out this week.

@JorgeB Two months later...

I got really busy with work and could not get to addressing the docker image until now. I was planning to do this today but I had completely run out of room on my cache drive. I added a new 2 TB nvme and followed the instructions here:

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/cache-pools/#adding-disks-to-a-pool

I completed the instructions and the cache pool showed both drives with a total of 3 TB. However, the GUI started running slowly (taking minutes to show the array drives) and neither Docker nor my VMs were loading. I rebooted the system and now both cache drives are showing as unmountable.

When adding the new drive, I made sure to format it in btrfs to match the existing cache drive. I'm not sure where to go from here. Any help would be appreciated.

diagnostics-20251120-2122.zip

5 hours ago, rockbox948 said:

I made sure to format it in btrfs to match the existing cache drive.

You don't need to do this, it will be formatted when added.

The pool ran out of space, likely during the balance:

Nov 20 15:29:12 Cylon kernel: BTRFS: error (device nvme0n1p1: state A) in cleanup_transaction:2004: errno=-28 No space left

You can try canceling the balance to see if it can still mount:

mkdir /temp

mount -t btrfs -o skip_balance /dev/nvme0n1p1 /temp

If that works, then type

btrfs balance cancel /temp

umount /temp

Then stop the docker and VM services, start the array, and see if it mounts.

@JorgeB Thanks. To make sure I have the procedures right before I start:

1. Stop the array.

2. Try the first set of commands you provided.

3. If that works, try the second set of commands.

4. Stop docker and VM services.

5. Start the array.

6. If it mounts, restart docker and VM services.

Is that correct?

6 minutes ago, rockbox948 said:

If it mounts, restart docker and VM services.

Nope, don't start the services; just post the diags.

@JorgeB Everything is running extremely slowly. For example, the Main window took about 2 minutes to reload and show the array drives once I stopped the array and the terminal window took about a minute and a half to load.

I did the first set of commands and got this. I'm not sure if this "worked". Do I proceed with the second set?

Edited November 21, 2025Nov 21 by rockbox948

1 minute ago, rockbox948 said:

I did the first set of commands and got this. I'm not sure if this "worked"

It didn't because there's a typo; see the command above, but if it's that slow, recommend rebooting in safe mode first.

@JorgeB   In safe mode and without the typo I get this:

This is from using the command twice.