RAID 60 Will Not Mount Although Every Drive Looks Healthy
Every drive may respond normally while the RAID 60 volume remains unavailable. At that point, ADR must determine which drives belong to each RAID 6 group, whether those groups can be reconstructed consistently, and how they were striped together.
Do not create, initialize, format, import, or repair a replacement virtual disk. Preserve the controller view, member order, and expected capacity first.
What this condition means
Healthy usually means the controller can communicate with a drive. It does not prove that the drive is assigned to the right lower group or that the controller is presenting the original RAID 60 layout.
The problem may be lost configuration, changed member assignments, an incomplete lower group, controller or enclosure trouble, or filesystem damage after the RAID is assembled.
What to record
- Server, controller, enclosure, firmware, and expected capacity
- Every physical-drive and virtual-disk status screen
- Bay, serial number, size, and reported group membership of each drive
- The last normal mount and the first missing-volume event
- Reboots, replacements, imports, recreations, rebuilds, and filesystem repairs
What not to do
- Create a new RAID 60 using remembered settings
- Initialize or format the newly proposed volume
- Clear or import configuration without reviewing the full member set
- Force members online in trial combinations
- Run filesystem repair before the two RAID layers are validated
How ADR evaluates it
ADR reviews the controller information, member order, drive sizes, and failure history, then protects any source that cannot be read reliably.
Each RAID 6 group is reconstructed and the stripe joining those groups is tested. Recovered data is written to separate destination storage, not back to the failed array.
What happens next
If the drives can be accessed safely, ADR can begin by identifying and protecting the members. The failed server does not need to mount the volume or bring the RAID 60 online first.