| Previous | Next |
| STATUS_VOLMGR_MEMBER_INDEX_INVALID | STATUS_VOLMGR_MEMBER_NOT_DETACHED |
STATUS_VOLMGR_MEMBER_MISSING
The member targeted for regeneration is not currently present
STATUS_VOLMGR_MEMBER_MISSING says that the specific member named by the operation is absent. The built-in description also makes the consequence explicit: a missing member cannot be regenerated in its present state.
That differs from a member that is detached but still represented as a replaceable topology object. Missing dynamic disks commonly appear after path loss, power loss, controller failure, or removal; Microsoft Disk Management guidance treats Offline and Missing as storage-visibility states that must be investigated before recovery.
Map the member back to its physical disk or LUN and determine whether the device can return. If the hardware is permanently lost, establish the redundancy and remaining plex health before using an operation intended to remove or replace the missing component.
What to inspect
- Identify the disk or LUN that owns the missing member and verify whether it is visible to the operating system.
- Check the containing volume for Failed or Failed Redundancy state before starting another repair.
- Distinguish a truly missing member from a detached member because Volume Manager exposes different state checks for replacement workflows.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_MEMBER_MISSING.
- Microsoft troubleshooting for Offline and Missing dynamic disks.
- MS-VDS pack recovery behavior for missing disks and redundant volumes.
Looking for a different code? Search another status or error code.