Nested RAID recovery

RAID 50 and RAID 60 failures must be solved at both the parity-set and outer-stripe layers.

RAID 50 stripes across RAID 5 groups, while RAID 60 stripes across RAID 6 groups. Whether multiple failures are survivable depends on which inner group each failed disk belongs to, plus unreadable sectors, stale members, and rebuild history.

Start a recovery case Call 682-325-7712

Understand the symptom

Nested arrays require reconstruction of inner groups before the outer stripe.

WHY

What is happening

Each parity set has its own member order, parity rotation, stripe size, and failure tolerance. The outer layer then combines those virtual groups. Recovery identifies group membership, offsets, stale generations, and unreadable regions before assembling the higher-level address space.

What you may see

Symptoms that change the recovery path.

Several disks show failed or foreign

Controller state may no longer reveal which disks belonged to each span.

Array failed during rebuild

Another member or parity group could not complete sustained reads.

Replacement controller sees multiple arrays

Imported metadata is incomplete, stale, or interpreted differently.

Some volumes mount and others fail

Damage may affect only outer ranges or specific inner parity sets.

Protect the source

Actions that can make the situation worse.

Force-online can cross generations

Bringing back stale members may create inconsistent parity groups.

New configuration overwrites nested metadata

Initialization can erase offsets and member-group evidence.

Rebuilds amplify second-failure risk

Every survivor in the affected group is read intensively.

Do this now

Safe steps before evaluation.

Stop controller operations

Cancel rebuild, consistency check, initialization, patrol read, and write activity.

Map every disk and span

Record serial, bay, status, event order, replacements, and any known group membership.

Export configuration and logs

Save stripe sizes, parity type, span width, offsets, cache state, and firmware.

Retain failed and replaced drives

Older members may supply sectors missing from newer degraded copies.

NEPFOSYS process

How a data-first evaluation proceeds.

Inner-group mapping

NEPFOSYS determines group membership, age, geometry, and failure ranges.

Nested virtual assembly

Candidate RAID 5 or 6 groups are reconstructed before testing the outer stripe.

Volume verification

Partition, filesystem, VM, and database evidence confirms the most consistent layout.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

How many disks can RAID 60 lose?

Up to two per inner RAID 6 group in ideal conditions, not simply any number across the full array.

Is RAID 50 safer than RAID 5?

It can tolerate failures in different inner groups, but multiple failures within one RAID 5 group can still stop the array.

Should I replace every failed disk and rebuild?

Not before preserving all members and confirming group layout and surviving-disk health.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case