RAID Virtual Disk Missing After Reboot: What to Do
When a RAID virtual disk disappears after reboot, the controller is no longer presenting the member set as the logical volume it previously recognized. The members may still contain the array data, but the controller state, detected drive set, or on-disk metadata has changed.
Do not create a new virtual disk or initialize the members. Record the controller and drive status before another reboot or configuration change.
What this condition means
A reboot can expose a drive that is slow to identify, a cabling or backplane problem, foreign metadata, lost controller cache or configuration, or a member that was already weak before shutdown.
The absence of the virtual disk does not establish whether the fault is physical or logical. That requires checking each member and the configuration evidence.
What to record
- Controller model, firmware, and cache or battery status
- Virtual-disk and physical-disk messages
- Slot and serial number of every member
- Events before the reboot and any earlier degraded state
- Imports, clears, force-online actions, or attempted recreations
What not to do
- Create a virtual disk with guessed settings
- Initialize or fast-initialize the member set
- Clear foreign metadata before documenting it
- Change drive order
- Run filesystem repair on a volume produced by uncertain settings
How ADR evaluates it
ADR reviews controller information, member identity, readability, and RAID metadata to determine the last consistent array state. Unstable members are protected before reconstruction.
A candidate virtual array is validated through filesystem and file structures before it is used for recovery. The original controller is not used as a trial-and-error reconstruction tool.
What happens next
Many missing-virtual-disk cases remain recoverable when the original members are available and no new configuration has overwritten them.