Business-critical storage failure?1-800-228-8800
ADRADR Data RecoveryRAID · Server · NAS · Virtualization Start Emergency Triage

RAID 60 failure triage

Recover RAID 60 by understanding both RAID 6 groups and the stripe above them.

RAID 60 combines two layers: each lower group has dual parity, and the upper layer stripes data across those groups. ADR preserves the complete member set, establishes each group independently, and then reconstructs the relationship between them.

Call a RAID recovery technician Start emergency triage

Record the controller and enclosure, total member count, original bay order, drive sizes, displayed group state, and every replacement or rebuild already attempted.

Group awareEach RAID 6 set is established separately
Stripe awareThe upper RAID 0 relationship is validated
Sources protectedOriginal members remain unchanged
Controller optionalThe failed array need not be brought online

Recognize the RAID 60 condition

A healthy-drive count does not prove that both groups and the top-level stripe are correct.

A RAID 60 can disappear because one lower group is incomplete, member identity or metadata changed, a rebuild introduced a different state, the controller lost the compound layout, or the filesystem can no longer use the reconstructed volume.

Power eventRAID 60 degraded after power lossPreserve cache, group membership, member status, and controller evidence before repair.Review this failure → Missing volumeAll drives look healthy, but RAID 60 will not mountHealthy labels do not validate the two group layouts or the stripe joining them.Review this failure → Rebuild stoppedRAID 60 rebuild is stuckRecord the exact percentage, source group, target member, and controller errors.Review this failure → Both groups degradedNo RAID 60 array is foundEach lower group must be reconstructed before their top-level relationship can be tested.Review this failure → Post-rebuild corruptionCorruption appeared after drive replacementKeep the original member and replacement; they may represent different array states.Review this failure → Wrong presentationVirtual disk is missing or the wrong sizeDo not initialize the proposed volume or accept a guessed compound layout.Review this failure → Array offlineRAID 60 dropped offline although drives still respondPhysical-drive status does not prove that the compound virtual disk is assembled correctly.Review this failure → Drive order changedRAID 60 became unreadable after a drive swapStop changing bays and preserve both the original and current member order.Review this failure → Group conflictThe lower groups do not produce one clear layoutIdentify whether the disagreement begins inside a group or in the stripe joining them.Review this failure →

A controlled RAID 60 recovery path

Establish the members, reconstruct each RAID 6 group, then validate the stripe across them.

  1. 1

    Document the full set

    Preserve member identity, bay order, controller state, lower-group membership, replacements, and the sequence of events.

  2. 2

    Protect unstable members

    Image sources that cannot sustain reliable reads before parity or reconstruction work proceeds.

  3. 3

    Reconstruct the lower groups

    Determine membership, order, offsets, stripe geometry, parity rotation, and the most defensible member generation for each RAID 6 set.

  4. 4

    Join and verify the groups

    Validate the top-level stripe, filesystem, and priority data, then recover to separate destination storage.

See how ADR begins outside the controllerReview RAID recovery services

Before another RAID 60 operation

Describe both group states and everything that changed.

An ADR technician can review the member set, controller messages, rebuild history, custody requirements, and the safest way to begin protecting the array.

Call 1-800-228-8800Start emergency triage