| Previous | Next |
| STATUS_VOLMGR_VOLUME_MIRRORED | STATUS_VOLMGR_NO_VALID_LOG_COPIES |
STATUS_VOLMGR_PLEX_NOT_SIMPLE_SPANNED
The selected plex lies outside the simple-or-spanned layout set
STATUS_VOLMGR_PLEX_NOT_SIMPLE_SPANNED is more permissive than the simple-only status: the operation accepts simple and spanned plexes, but the selected plex is neither.
Spanned volumes concatenate extents across disks without striping, while striped, mirrored, and parity layouts have different placement or redundancy rules. The rejected operation evidently relies on the linear extent model shared by simple and spanned layouts.
Inspect the actual plex type and the command dispatch logic. A generic “multi-disk volume” branch is insufficient because a spanned plex and a striped/parity plex can both involve several disks but require different management semantics.
What to inspect
- Query the plex type and verify it is simple or spanned before issuing this operation.
- If the volume is striped, mirrored, or parity-based, select the layout-specific management path.
- Review caller logic that classifies volumes only by disk count because that does not distinguish spanning from striping.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_PLEX_NOT_SIMPLE_SPANNED.
- Microsoft VDS semantics for simple and spanned volumes.
- Microsoft dynamic-disk feature list for spanned and striped layouts.
Looking for a different code? Search another status or error code.