RAID 50 failure triage
Recover RAID 50 by rebuilding each RAID 5 group before joining them.
RAID 50 has two recovery layers: the members inside each lower RAID 5 group, and the stripe that joins those groups into one virtual disk. ADR preserves the complete set, establishes each group independently, and validates the upper stripe before accepting recovered data.
Record the controller and enclosure, total member count, original bay order, drive sizes, displayed group state, and every replacement or rebuild already attempted.
Recognize the RAID 50 condition
Controller status describes the array it can assemble now—not necessarily the best recoverable state.
A RAID 50 can disappear when a lower group is incomplete, group membership changes, a foreign configuration appears, a rebuild encounters unreadable data, or the completed array contains corruption. Preserve the evidence before asking the controller to choose another state.
A controlled RAID 50 recovery path
Establish the members, reconstruct each RAID 5 group, then validate the stripe across them.
- 1
Document the complete set
Preserve member identity, bay order, group assignments, replacements, controller state, and the sequence of events.
- 2
Protect unstable sources
Image members that cannot sustain reliable reads before parity or reconstruction work proceeds.
- 3
Reconstruct the lower groups
Determine membership, order, offsets, stripe geometry, parity rotation, and the best available member state for each RAID 5 set.
- 4
Join and verify the groups
Validate the upper stripe, filesystem, and priority data, then recover to separate destination storage.
Before another RAID 50 operation
Describe the group states and everything that changed.
An ADR technician can review the complete member set, controller messages, rebuild history, custody requirements, and the safest way to begin protecting the array.