RAID 60 Virtual Disk Missing or the Wrong Size After Restart
If the RAID 60 virtual disk disappears or returns at the wrong capacity after a restart, the controller may be presenting an incomplete member set, different lower-group boundaries, or a changed top-level configuration. Do not treat the proposed volume as the original array.
Do not initialize, expand, shrink, format, or repair the volume. Record the expected capacity and the controller’s complete physical and logical view first.
What this condition means
Wrong capacity is useful evidence. It can show that members are missing, a lower group has been assembled differently, or the top-level stripe no longer includes the expected groups.
A restart may expose configuration, cache, controller, enclosure, or member problems that were already developing. It does not prove that the data was erased.
What to record
- Expected and currently reported capacity
- Controller, enclosure, firmware, and cache status
- Physical members and reported membership of each lower group
- Bay, serial number, and size of every drive
- Restart, replacement, import, rebuild, or configuration events
What not to do
- Initialize or format the wrong-size volume
- Create a new array using remembered settings
- Add missing members by trial and error
- Clear and re-import configuration repeatedly
- Run filesystem repair on the incorrectly presented volume
How ADR evaluates it
ADR compares the expected layout with the member set and controller evidence, then reconstructs each lower RAID 6 group independently.
The top-level stripe is tested for the expected capacity and filesystem before any data is recovered to separate destination storage.
What happens next
A missing or wrong-size virtual disk can still contain recoverable data across its members. ADR can begin from the drives without accepting the controller’s current presentation as correct.