RAID 10 Disks Show OK but No Virtual Disk Appears
A controller may communicate with every RAID 10 member while failing to present the virtual disk. The drives can be readable even when pair membership, stripe geometry, configuration metadata, or the selected write history no longer produces the expected volume.
Do not create or initialize a replacement virtual disk. Record the controller view, member order, and expected capacity before changing configuration.
What this condition means
An OK drive label usually confirms communication with the device. It does not prove that the controller has identified the correct mirror pairs or assembled the stripe across them.
The condition may follow power loss, controller replacement, cache or firmware trouble, an enclosure change, member movement, or configuration metadata the controller no longer accepts.
What to record
- Server, controller, enclosure, firmware, and expected capacity
- Every physical-disk and virtual-disk status screen
- Bay, serial number, size, and displayed state of every member
- The last successful mount and first missing-volume event
- Power, controller, import, clear, recreation, or member-movement history
What not to do
- Create a new RAID 10 using remembered settings
- Initialize or format a newly presented disk
- Clear or import configuration by trial and error
- Move members between bays while testing
- Run filesystem repair before the RAID layout is validated
How ADR evaluates it
ADR identifies mirror-pair membership, member generation, readable coverage, and the stripe relationship across the pairs.
A candidate reconstruction is checked for expected capacity, filesystem structures, and priority data before recovery to separate storage.
What happens next
The server does not need to present the virtual disk before ADR begins. The complete member set can be evaluated independently without creating a replacement array.