| Previous | Next |
| STATUS_VOLMGR_VOLUME_LENGTH_NOT_SECTOR_SIZE_MULTIPLE | STATUS_VOLMGR_VOLUME_NOT_RETAINED |
STATUS_VOLMGR_VOLUME_NOT_MIRRORED
The command needs a mirror, but the selected volume is not mirrored
STATUS_VOLMGR_VOLUME_NOT_MIRRORED means the requested operation is defined only for mirrored volumes. The current target might be simple, spanned, striped, or parity-based instead.
Mirror operations work with multiple complete-copy plexes. That is structurally different from a parity plex or a spanned set of extents, even though all of those layouts can involve several disks. A generic “multi-disk volume” check is therefore not sufficient.
Inspect the actual volume type and the caller’s operation selection. If the user intended to create a mirror, verify that creation completed before issuing follow-up mirror commands; if the layout is intentionally another type, route the request to the appropriate volume-management path.
What to inspect
- Query the volume type and plex count immediately before the mirror-specific operation.
- Check completion of any earlier mirror-creation task rather than assuming it succeeded after submission.
- Distinguish striped-with-parity from mirrored storage when dispatching recovery commands.
References
- Microsoft VOLMGR entry for STATUS_VOLMGR_VOLUME_NOT_MIRRORED.
- Microsoft VDS comparison of mirrored and other dynamic volume types.
- MS-VDS recovery behavior distinguishing mirror resynchronization from RAID-5 regeneration.
Looking for a different code? Search another status or error code.