Lots of regret here, but making the best of what I have to work with:

Recently (within the past 24 hours) completed a parity check on an Unraid 6.11.5 box. Zero errors, all good.

Went to replace an old drive with a larger, new drive, and system did not recognize the new drive.

Tried a second new drive, and system would not boot.

Tried to change boot order through BIOS, and could not select the flash drive as a boot option. Plugged the flash into my laptop, and it’s not recognized at all - totally dead.

I should be good on the key replacement (have a full flash backup from a couple of years ago, after upgrading to v6), but I’m struggling to find records identifying which two drives are Parity 1 and Parity 2. The flash backup had different (smaller) Parity 1 and Parity 2 drives at the time.

I DO have a diagnostic file from ~18 months ago that was captured at a time where Parity 1 and Parity 2 were the drives that are currently being used as Parity 1 and Parity 2.

Through the diagnostics, I’ve managed to figure out which two drives are the parity drives - but is there a way to confirm through the diagnostics which was operating as Parity 1 vs. Parity 2?

My best guess currently is that “disk0” (in an array naturally going up to disk18) was Parity 1, and “disk29” (with no disks identified between 19 and 28, with cache apparently being listed as 30?) was Parity 2, but I don’t feel confident about this at all without checking here first.

tower-diagnostics-20240620-1904.zip

Edited November 1, 2025Nov 1 by wheel
Uploaded Diagnostics

12 hours ago, wheel said:

My best guess currently is that “disk0” (in an array naturally going up to disk18) was Parity 1, and “disk29” (with no disks identified between 19 and 28, with cache apparently being listed as 30?) was Parity 2, but I don’t feel confident about this at all without checking here first.

That is correct.

Great - thanks for the confirmation!

I successfully set up a new flash drive (manual setup, copying entire flash drive backup config directory over, overwriting a fresh 6.11.5's existing config directory files), started up the system, got into the GUI, and re-assigned all the parity drives ("disk0" as Parity 1 and "disk29" as Parity 2) and data drives that had been added/replaced since the last full flash drive backup two years ago. So far, so good!

One weird problem I can't find a solution for by searching: on the main page, I get the "Invalid, missing, or expired Registration Key" error.

Under the registration tab, all of my old registration info (including the former Flash GUID) is listed.

Other posts discuss a "replace key" button that might be greyed out, but the only option available (and it's not greyed out) on my screen is a button that says "Fix Error."

I'm inclined to just click "Fix Error" under the assumption it will reconcile my new Flash GUID with the old one (since it's an original license from 2011 and has never been moved to a second flash drive since original purchase), but feel so close to the finish line here that I wanted to double-check before potentially messing something up that I can't search and find a confirmation post for (nothing showing up in results for "Fix Error" specifically, as a button).

I'd greatly appreciate anyone putting my mind at ease here before clicking the "Fix Error" button, and am incredibly thankful for confirmation I figured out the Parity 1 / Parity 2 situation through guesswork!

Edited November 2, 2025Nov 2 by wheel
Added details.

Click the fix button, and if you cannot make the transfer yourself, you can contact support.