Two drives are failed or missing
RAID 6 can tolerate two unavailable members only when the remaining set is readable and represents one consistent array state.
Review this condition →RAID 6 data recovery
A RAID 6 may be offline even when several members remain readable. ADR evaluates each drive independently, protects unstable sources, and reconstructs the array away from the failed controller before recovered data is written elsewhere.
The array does not need to be forced online, rebuilt, or mounted before ADR can begin evaluating the member set.
Start with the symptom
RAID 6 protects against two member failures during normal operation. Recovery becomes a different problem when failures occurred at different times, a rebuild changed one member, or additional drives are readable only in part.
RAID 6 can tolerate two unavailable members only when the remaining set is readable and represents one consistent array state.
Review this condition →Stop the rebuild and protect the available sources before overlapping read errors reduce the remaining recovery options.
Review this condition →Keep the removed member and partial rebuild target. Do not restart the process merely to see whether it advances.
Review this condition →Stop before additional reads or writes compound an already inconsistent member set.
Review this condition →Healthy drive labels do not prove the controller has assembled the correct member set or geometry.
Review this condition →Preserve every original and replacement member and record each rebuild, import, force-online, or repair action.
Review this condition →Do not recreate the RAID 6 from memory. Order, offsets, stripe geometry, and parity behavior can be tested virtually.
Review this condition →The recovery path
ADR works from the evidence on the individual drives. Candidate layouts are tested without asking the controller to rewrite the only available member set.
Record the enclosure, controller, RAID level, bay order, serial numbers, failures, replacements, and exact sequence of events.
Image members that are slow, inconsistent, unreadable in regions, or rejected by the controller.
Establish member generations, order, offsets, stripe geometry, and dual-parity behavior outside the controller.
Validate the reconstructed filesystem and recover the files, databases, or virtual machines needed first to separate storage.
We can get started now
Start with the controller or NAS model, member count and capacities, current status of every drive, rebuild or replacement history, and the systems or data the business needs first.