| Previous | Next |
| STATUS_VOLMGR_MEMBER_MISSING | STATUS_VOLMGR_MEMBER_REGENERATING |
STATUS_VOLMGR_MEMBER_NOT_DETACHED
Replacement is blocked because the old member is still attached
STATUS_VOLMGR_MEMBER_NOT_DETACHED is specific to replacement state. Volume Manager refuses the replace-member operation because the selected member is still attached to the volume layout.
The error should not be interpreted as proof that the member is healthy. A disk can be failing or a volume can be degraded while the logical member object remains attached. The important distinction is whether the topology has entered the detached state expected by the replacement operation.
Inspect the preceding management sequence and the member state from a fresh enumeration. If a detach task was asynchronous, confirm its task result and resulting notification before issuing replacement; merely waiting a fixed amount of time is not a reliable state transition check.
What to inspect
- Verify the member selected for replacement is the same object that the detach operation targeted.
- Wait for the detach task to complete and refresh topology instead of relying on cached state.
- If detachment itself failed, diagnose that failure rather than repeatedly submitting the replacement request.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_MEMBER_NOT_DETACHED.
- MS-DMRP notes on asynchronous storage-management tasks.
- Microsoft VDS health and transition-state concepts.
Looking for a different code? Search another status or error code.