hi. my unraid system suddenly has errors on my drives. can anyone help me on what to do next? i have done xfs repair on disk1, the status said done. and now my files have returned and can be accessed from unraid and from windows explorer. what should i do to return parity2 and disk1 to the green dot state? hovering mouse over both X's says Parity - "Parity device is disabled. Click to spindown." and Disk1 - "Device is disabled. Contents emulated. Click to spindown".

i have attached the diagnostic zip and photos that i think are relevent to the case.

cjeserver-diagnostics-20260615-1413.zip

Edited June 15Jun 15 by dimsum
added screenshot for chronology when the array passed and failed

Disks were already disabled at boot, so we can't see what happened, but they look healthy, so most likely a power/connection issue.

If you are happy with the emulated disk1 contents, check/replace cables for those disks, especially if they share something like a power splitter, then rebuild:

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

i have swapped to new sata cables and divided the power cables to be 2 drives sharing 1 powere cable. disk1 is accessible now with all my data and files. its just that it is now on X and not the green dot

17 minutes ago, dimsum said:

its just that it is now on X and not the green dot

You need to rebuild to resolve that, see the link above.

i've rebuilt it. and now all docker is gone. and its docker.img is corrupted. now i have to reinstall and reconfigure all docker again.

1. ❌ parent transid verify failed

2. ❌ failed to load root csum

3. ❌ open_ctree failed

4. ❌ btrfs check --readonly could not even open the filesystem

I assume that is the cache pool, so unrelated to the rebuild, but post new diagnostics.

but why is docker.img saved in cache? i thought it will be in hdd? so in the end it was the settings that got mixed up and saved in cache?

i've done extended smart test on all 4 hdd and 1 nvme. all came back "completed with no error". why did it corrupt in the first place....?

It's typically (and by default) saved on a pool, but if that is the Docker image, not the cache filesystem, you can just recreate it:

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