| Previous | Next |
| STATUS_VOLMGR_PLEX_INDEX_DUPLICATE | STATUS_VOLMGR_PLEX_LAST_ACTIVE |
STATUS_VOLMGR_PLEX_INDEX_INVALID
The selected plex position is beyond the current volume layout
STATUS_VOLMGR_PLEX_INDEX_INVALID means the supplied plex index is greater than or equal to the number of plexes in the volume. The index passed validation as a number but does not identify a current plex.
This often matters in management code that caches an enumeration and later acts by array position. A mirror split, plex removal, import, or recovery can change the plex set between those two steps, leaving the old index outside the new count.
Re-enumerate the volume and log the returned plex count next to the rejected index. If the caller intends to follow one specific plex across state changes, use the stable object identifiers exposed by the management layer rather than assuming its ordinal position never moves.
What to inspect
- Read the current plex count from the same volume instance immediately before the operation.
- Check whether another task removed, added, or rebuilt a plex after the caller cached its index.
- Fix code that persists plex array offsets across refreshes or reconnects.
References
- Microsoft VOLMGR description of STATUS_VOLMGR_PLEX_INDEX_INVALID.
- Microsoft VDS volume object and plex hierarchy.
- MS-DMRP behavior around asynchronous volume-management tasks.
Looking for a different code? Search another status or error code.