Hi again,

I originally posted here:
https://forums.unraid.net/topic/197838-drive-configuration-list/#comment-1613687
My issue was that my jump drive died and I didn't have a recent backup. Most of my disks had been upgraded to larger ones since then so the disk config was no longer valid.

Anyway, I tried to follow the guide that the mod linked to me:
https://docs.unraid.net/unraid-os/troubleshooting/common-issues/boot-and-startup-failures/#recovering-from-a-lost-boot-drive-and-unknown-parity-drives.

The issue is that neither of the outlined approaches are working. When I try option #1, assigning all drives as data drives and mounting it won't let me start the array as it says: "You may not add new disk(s) and also remove existing disk(s)."
So I went for option two but I am unable to mount any of the disks as it says it fails. In the logs it shows:
"unassigned.devices: luksOpen result: Error: Passphrase or Key File not found."

I know the passphrase but I am not sure where to go from here as it doesn't give me the option to mount it using the passphrase.

Am I completely hosed at this point or is there still a method to get back up and running?

Thanks in advance for anyone who can help me.

Tools - New Config -Apply

Then assign all previous array disks as data (NO PARITY), start the array, and post the diagnostics.

edinburgh-diagnostics-20260322-0742.zip

Ok! I was able to do as you outlined. And here are the diagnostics.

Disk3 and disk6 didn't mount, I assume you had dual parity?

Correct. I had dual parity. So now I just need to assign those two disks to parity (parity will need to be rebuilt most likely) and keep the rest as data disks and start the array?

5 minutes ago, itsmepetey said:

So now I just need to assign those two disks to parity (parity will need to be rebuilt most likely) and keep the rest as data disks and start the array?

Correct, it is not possible to know which one was parity 1 and 2, and they are not interchangeable, so you can do another new config to reassign those as parity, then start the array to sync parity. Double-check you assign the correct disk to the parity slots; if you assign a data disk, all data on that disk will be lost after array start.

Thanks very much for your patience and helping me. I have followed your steps and it seems to be back up and running. So far I think I picked the correct two parity disks. Some of my docker containers aren't functioning but I imagine that should be fixable with just redoing them.

Thanks again!