rockbox948

@JorgeB Thanks so much for all of your help with this. I am back up and running, my data was not lost, and the issue with the docker page not loading has been resolved!

@JorgeB Perfect! The cache pool is back and at 3TB. Is there anything else I should do before moving my domains and appdata folders back to the cache?

@JorgeB Thanks! I was able to copy the files to an external drive. I rebooted into normal mode and started the array. Both nvme drives were shown as unmountable and the option to format them was available. When I clicked the "Yes, I want to do this" checkbox in the Format section and got this warning about updating the parity. I thought the parity was unaffiliated with the cache pool.

@JorgeB Thanks so much for your help. I'm obviously not well versed on all of this. In my case, would the command from the FAQ be the following since this is the 1 TB drive that is full (I didn't see an sdX indicator for the drive)? mount -o rescue=all,ro /dev/nvmen1n1 /temp

This is from using the command twice.

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

@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?

@JorgeB Thanks. To make sure I have the procedures right before I start: Stop the array. Try the first set of commands you provided. If that works, try the second set of commands. Stop docker and VM services. Start the array. If it mounts, restart docker and VM services. Is that correct?

@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

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

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.

lol, I missed the screenshot part.

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?

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?

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