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

RAID 60 Group-Level Inconsistency: Identify Which Layer Is Wrong

Group-level inconsistency means the available member evidence does not support one obvious RAID 60 layout. One lower RAID 6 group may be incomplete or reconstructed differently, or the stripe joining the groups may not match the expected volume.

Preserve the current state.

Do not synchronize parity, rebuild another member, or force the groups together. Preserve each group and its members as separate evidence.

What this condition means

The first task is to determine whether the conflict exists inside a lower RAID 6 group or in the relationship between otherwise usable groups.

Member replacements, interrupted rebuilds, lost configuration, controller changes, and stale metadata can leave more than one plausible array state.

What to record

What not to do

How ADR evaluates it

ADR tests member identity, readability, metadata, and parity within each lower group, then compares candidate groups at the top RAID 60 layer.

The expected capacity, filesystem structures, and priority data are used to distinguish a defensible reconstruction from a merely mountable one.

What happens next

ADR can evaluate the two RAID layers separately. That makes it possible to identify where the disagreement begins before any recovery output is accepted.