| Previous | Next |
| STATUS_VOLMGR_MEMBER_NOT_DETACHED | STATUS_VOLMGR_ALL_DISKS_FAILED |
STATUS_VOLMGR_MEMBER_REGENERATING
A second operation collided with an active member rebuild
STATUS_VOLMGR_MEMBER_REGENERATING means the member already has regeneration in progress. Volume Manager rejects another request that assumes the member is idle or ready for a new state transition.
Regeneration is a recovery activity for fault-tolerant storage. Microsoft models rebuilding as a distinct health condition, and the VDS recovery protocol can resynchronize mirrors or regenerate RAID-5 data. While that work is active, topology-changing or duplicate recovery commands can conflict with the same member.
Use the task and health state as the synchronization mechanism. A retry loop that resubmits regeneration after a timeout can create this status even when the original job is still running normally in the storage stack.
What to inspect
- Check whether an earlier asynchronous recovery task is still active and retain its task identifier.
- Read current member and volume health before treating a client-side timeout as a failed regeneration.
- Only schedule another repair after the previous rebuild has completed, failed, or been explicitly canceled by the owning workflow.
References
- Microsoft VOLMGR entry for STATUS_VOLMGR_MEMBER_REGENERATING.
- Microsoft VDS rebuilding health state.
- MS-VDS recovery behavior for redundant dynamic volumes.
Looking for a different code? Search another status or error code.