RAID Controller Sees the Drives but Not the Volume
When the physical members appear but the virtual disk does not, the controller is no longer willing or able to assemble the expected logical volume. The missing presentation is not a diagnosis of the member data.
Do not recreate the virtual disk, initialize the members, or cycle through imports and force-online combinations merely to restore visibility.
What this condition means
The cause may be inconsistent metadata, a missing or slow member, controller or cache failure, an interrupted rebuild, a backplane problem, or a configuration from a different generation.
Even a volume that reappears can be wrong if it was assembled with the wrong member order, offset, stripe geometry, or generation.
What to record
- Controller, enclosure, firmware, and expected volume capacity
- Virtual-disk and physical-disk status screens
- Slot and serial number of every original and replacement member
- The event immediately before the volume disappeared
- Every import, rebuild, force-online, clear, or create action
What not to do
- Create another virtual disk over the members
- Initialize drives presented as available
- Import or clear configuration by trial and error
- Force members online in different combinations
- Repair a filesystem before validating the array
How ADR evaluates it
ADR verifies member identity, readability, metadata, and history before testing order, offset, stripe geometry, and parity.
The controller can be removed from the recovery path. A virtual reconstruction is checked before files are recovered to separate destination storage.
ADR can access the members independently and determine why the volume is missing without requiring the controller to import, recreate, or mount it first.
What happens next
The member set may retain a coherent recoverable state even when the controller presents no volume. Preserve it before another controller write.