August 19, 2025Aug 19 I've been having an issue recently with this error - This will result in all of my docker containers failing to start or stop.This is what happens when I try to start a container:I've tried to expand the size of my docker image which hasn't helped. It's now at 50Gb but it seems the docker image is corrupt, not full.I stopped the docker service and then deleted the docker image. Then re-imported all my containers. Overnight I get the same error message in the morning.Does this suggest the disk is failing? It's a 1Tb SSD that is less that a year old 😒 or could it be something else?The only way to get it working again temporarily is to reboot the server, or stop and start the array, then the docker service.Here are my diagnostic logs if anyone can take a look:tower-diagnostics-20250819-0951.zipWhat are my next steps here? Memtest?Thanks 😁 Edited August 19, 2025Aug 19 by clownstyle
August 19, 2025Aug 19 Community Expert Pool filesystem is corrupted; you will need to copy what you can and reformat, but before doing that, I recommend running memtest.
August 19, 2025Aug 19 Author 2 hours ago, JorgeB said:Pool filesystem is corrupted; you will need to copy what you can and reformat, but before doing that, I recommend running memtest.Thanks - I'd already started moving everything from the cache to the array. I've just formatted but used xfs as the file system (I only plan to use one cache drive).Mover is now moving everything in appdata / domains / system back to the cache drive.Once that is done I'll do a memtest but hopefully formatting the cache drive will do the trick!
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.