| Previous | Next |
| STATUS_VOLMGR_MEMBER_INDEX_DUPLICATE | STATUS_VOLMGR_MEMBER_MISSING |
STATUS_VOLMGR_MEMBER_INDEX_INVALID
The caller selected a member position that does not exist
STATUS_VOLMGR_MEMBER_INDEX_INVALID means the numeric member index is greater than or equal to the number of members described for the plex. Unlike the duplicate-index status, the problem is range validation rather than two entries colliding.
Member numbering belongs to the current volume topology. It can become stale after a disk is detached, a foreign pack is imported, or a recovery operation changes which members are represented. A cached index should not be treated as a permanent physical-disk identity.
Re-enumerate the volume before retrying and log the member count that Volume Manager reports alongside the rejected index. If an application translates UI positions into member indices, verify that filtering missing members has not shifted the numbering.
What to inspect
- Capture the rejected member index and the member count from the same topology snapshot.
- Refresh enumeration after import, detach, regeneration, or disk disappearance before issuing another member operation.
- Use stable disk or volume identifiers for correlation; do not persist a member array offset as if it were a disk ID.
References
- Microsoft VOLMGR description for STATUS_VOLMGR_MEMBER_INDEX_INVALID.
- MS-DMRP glossary entry explaining volume members.
- Microsoft guidance on refreshing and recovering dynamic-disk state.
Looking for a different code? Search another status or error code.