RAID 6 with Two Failed Drives: What to Do Next
RAID 6 is designed to tolerate two missing members, but that does not make every two-drive event safe to rebuild. The array may be operating at its limit while another member has unreadable sectors, intermittent timeouts, or inconsistent metadata.
Stop nonessential writes and do not start another rebuild until the two reported failures and the remaining member health are understood.
What this condition means
Two failed statuses can represent physical failure, timeouts, a controller event, or members that were excluded at different points in the array history. RAID 6 parity helps only when the surviving data is sufficiently readable and consistent.
If one drive dropped during a rebuild of another, the array may contain a mixture of old and newly written stripes. The sequence determines which member states should be used for reconstruction.
What to record
- RAID level, member count, controller, and enclosure
- Slot and serial number for every member
- Which drive dropped first and whether a rebuild began
- Rebuild percentage and all controller messages
- Read errors, timeouts, power events, or replacements
What not to do
- Replace both reported members at once
- Force members online by trial and error
- Restart a stalled rebuild
- Initialize or recreate the virtual disk
- Run consistency or filesystem repair before validation
How ADR evaluates it
ADR reviews the member history and protects unstable drives before testing reconstruction. The correct array state may require selecting member generations rather than accepting the controller’s current set.
Reconstruction and parity checks are performed against protected sources. The resulting volume is validated before file or application recovery proceeds.
What happens next
RAID 6 with two dropped members is often recoverable, but the margin for another unreadable region or incorrect write is small. Early preservation matters.