RAID 1 dual failure

Two RAID 1 members may be mirrors but not equally current or equally readable.

RAID 1 duplicates blocks across members, but degraded operation, bad sectors and interrupted rebuilds can leave two disks with different generations and different readable regions.

Understand the symptom

Mirror recovery compares freshness, readability and consistency across both members.

WHY

What is happening

A healthy mirror maintains matching writes, but once one disk drops out the surviving member becomes newer. If that member then develops errors or a rebuild partially copies data to another disk, no single device may contain the best version of every block. Imaging each independently allows a controlled composite rather than choosing blindly.

What you may see

Symptoms that change the recovery path.

01

Array is degraded and remaining disk errors

The only current member may be physically unstable or contain unreadable sectors.

02

Rebuild failed partway

The target may contain a mixture of copied and old or empty regions.

03

Both disks report healthy but files differ

One member may be stale, misidentified or written outside normal mirror operation.

04

Controller alternates preferred member

Boots or mounts may expose different data depending on which disk becomes active.

Protect the source

Actions that can make the situation worse.

01

Rebuild can overwrite a useful member

Selecting source and target incorrectly destroys an alternate generation.

02

Normal boot writes more changes

Applications and filesystem journals can widen differences between members.

03

Sector-by-sector copy may stall

A failing source needs controlled imaging that prioritizes readable regions.

Do this now

Safe steps before evaluation.

01

Stop the array

Prevent automatic rebuild, resync, boot and application writes.

02

Label source history

Record which disk failed first, which remained online and how far any rebuild progressed.

03

Preserve every member

Keep original, removed, replacement and target disks without reusing them.

04

Collect controller logs

Timestamps and serials help establish the data generation on each member.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Generation and health comparison

NEPFOSYS evaluates member timestamps, metadata, readability and failure sequence.

02

Independent imaging

Each mirror member is acquired separately with errors and unreadable ranges documented.

03

Best-block reconstruction

The most coherent current filesystem is assembled from the strongest available member data.

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.

Aren't RAID 1 drives identical?

Only while both receive every write. Degraded use, stale members and partial rebuilds can create different generations.

Should I clone the better-looking drive over the other?

No. That destroys the alternate copy. Image both to separate destinations before choosing or combining data.

Can two damaged mirrors improve recovery?

Potentially. Different members may read different weak regions, but generation consistency must be preserved.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case