RAID 60 Dropped Offline While Every Drive Still Looks Healthy
When every drive still responds but the RAID 60 is offline, the controller has lost confidence in the virtual disk or can no longer assemble it from the configuration it sees. The member data may still be present even though the volume is unavailable.
Do not clear the configuration, force the virtual disk online, or recreate it. Save the controller screens and preserve every drive in its present bay.
What this condition means
Physical-drive health and virtual-disk availability are different questions. The controller may see each device while rejecting a lower RAID 6 group, the top-level stripe, or the stored configuration.
Power, firmware, cache, enclosure communication, member metadata, or an earlier rebuild can all change how the controller presents the array.
What to record
- Server, controller, enclosure, firmware, and expected capacity
- Physical-drive, lower-group, and virtual-disk status screens
- Bay, serial number, and size of every drive
- The last normal access and the first offline event
- Power events, updates, replacements, imports, rebuilds, or force-online attempts
What not to do
- Force the virtual disk or members online
- Clear and re-import the configuration by trial and error
- Create a replacement RAID 60 over the existing drives
- Move drives between bays while testing
- Run filesystem repair before the array layout is verified
How ADR evaluates it
ADR compares the controller report with the identity and readable metadata of every member. Each lower RAID 6 group is established before the top-level stripe is tested.
If the controller is no longer a safe recovery environment, the members can be accessed independently and the array reconstructed from protected sources.
What happens next
An offline virtual disk does not mean every drive failed. ADR can review the complete set and determine whether recovery can begin without bringing the original controller or server online.