RAID 6 double failure

A RAID 6 with two unavailable members has no remaining fault margin during rebuild.

RAID 6 can ordinarily reconstruct two missing blocks per stripe, but a two-drive-degraded array is at its designed limit. A weak sector, disconnect, wrong member, or additional failure during rebuild can create unrecoverable stripe gaps.

Understand the symptom

Dual parity protects two missing blocks only when the remaining stripe members are readable and correctly ordered.

WHY

What is happening

A rebuild reads nearly every required block from every surviving disk. Latent sector errors or a member that intermittently drops can turn a tolerable two-disk loss into a three-block gap. The newest failed member may still have valuable readable regions, so recovery evaluates all disks rather than assuming two are absent.

What you may see

Symptoms that change the recovery path.

01

Array reports two failed members

The RAID remains online or degraded but has exhausted normal redundancy.

02

Rebuild stops on a read error

A surviving member cannot provide a block required to reconstruct the target.

03

Controller marks another disk predictive

Additional media risk appears before or during full-array reading.

04

Filesystem errors follow rebuild

Some stripes may have been reconstructed from incomplete or stale source data.

Protect the source

Actions that can make the situation worse.

01

Full rebuild stresses every survivor

Continuous reads can accelerate marginal disks and expose latent errors.

02

Wrong target or order corrupts stripes

Controller assumptions can write reconstructed data to the wrong member role.

03

Discarding failed disks removes partial data

Each may still supply readable blocks missing from other stripe locations.

Do this now

Safe steps before evaluation.

01

Stop nonessential workloads

Pause applications, backups, scrubs, patrol reads, and rebuilds when data preservation is the priority.

02

Export controller state

Save member serials, slots, RAID parameters, event logs, failed LBAs, and rebuild history.

03

Label every disk

Preserve failed, surviving, spare, and replacement members with exact bay and timeline.

04

Protect members before reconstruction

Acquire readable regions independently rather than rebuilding onto the only original set.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Failure chronology

NEPFOSYS maps member state, order, parity rotation, sector errors, and prior rebuild writes.

02

Member-level imaging

Every readable disk is preserved with unstable ranges recorded.

03

Virtual RAID reconstruction

Dual-parity geometry is tested on copies and priority filesystems are validated.

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.

Is RAID 6 safe after two drives fail?

It may remain accessible, but it has no protection against another unreadable block in a stripe. Reduce activity and preserve the set.

Should I rebuild one drive at a time?

Not before assessing and imaging all members. A rebuild is a full-array stress event and writes a new state.

Why keep both failed disks?

They can contain different readable regions and may reduce stripe gaps during reconstruction.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case