Hi

I had issues earlier today with some docker containers throwing weird errors.

Tried restarting docker, worked for a few minutes and back to broken.

After a reboot (Which ended up being unclean as it could not unmount devices) my cache shows up as: Unmountable: wrong or no file system

Attached a diagnostics.

unraid-diagnostics-20260309-1424.zip

Edited March 9Mar 9 by cnrd

There's a problem with the log tree, type this:

btrfs rescue zero-log /dev/sdd1

Then restart the array and post new diags.

Canceled the parity check, which now for the first time ever shows errors.

The cache seems to have come back to life.

Docker seems to complain about a read-only filesystem.

unraid-diagnostics-20260309-1515.zip

Edited March 9Mar 9 by cnrd

Btrfs is detecting some data corruption in all pool devices. It's a good idea to run memtest.

After that, recreate 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

I did install some new memory a few weeks ago, so that sounds like it could be a likely culprit.

If it is a memory problem and it is resolved, should the pool be able to heal itself?

It will depend, after memtest scrub the pool and see if there are any uncorrectable errors.

Are you referring to both the array and cache pool?

Any specific commands?

Thanks for the help by the way. :-)

The pool , you can scrub it by clicking on the first pool device, then scroll down to the scrub section.

Ended up with some uncorrectable errors.

I have copied all files that I could to the array and formatted the pool, now in the process of copying everything back. Nothing important was lost.

Thank you for your help

If you didn't have Docker and VM Manager disabled in Settings while you were without cache, they have probably created their files in system share on the array.