| Previous | Next |
| STATUS_VOLMGR_MAXIMUM_REGISTERED_USERS | STATUS_VOLMGR_MEMBER_INDEX_DUPLICATE |
STATUS_VOLMGR_MEMBER_IN_SYNC
Regeneration was requested for a member already considered current
STATUS_VOLMGR_MEMBER_IN_SYNC is a state mismatch, not a media error. The selected member is already synchronized with the other active members, so Volume Manager has no regeneration work to perform for it.
Microsoft describes rebuilding health separately from healthy storage: mirrored plexes resynchronize and RAID-5 parity regenerates when redundancy needs repair. A member reported in sync is already on the healthy side of that transition, even if another member or plex in the volume still requires attention.
Check why the caller selected this member. Stale UI state, delayed notification processing, or retry logic that does not re-read health after completion can cause a second regeneration request to target an object whose state has already changed.
What to inspect
- Query current health and transition state immediately before scheduling regeneration.
- Confirm that the intended degraded member was not replaced by an array index from an older enumeration.
- If a recovery job retries automatically, make completion idempotent by rechecking state after each task result.
References
- Microsoft VOLMGR entry for STATUS_VOLMGR_MEMBER_IN_SYNC.
- Microsoft VDS health values for healthy and rebuilding objects.
- MS-VDS recovery sequence for resynchronizing redundant volumes.
Looking for a different code? Search another status or error code.