| Previous | Next |
| STATUS_VOLMGR_PACK_LOG_UPDATE_FAILED | STATUS_VOLMGR_NUMBER_OF_DISKS_IN_MEMBER_INVALID |
STATUS_VOLMGR_NUMBER_OF_DISKS_IN_PLEX_INVALID
The plex-level disk count does not match the represented topology
STATUS_VOLMGR_NUMBER_OF_DISKS_IN_PLEX_INVALID points at the disk cardinality inside one plex. A volume can have multiple plexes, and each plex is itself composed of extents from one or more disks.
This status should be diagnosed at the plex boundary rather than by counting every disk in the pack. For example, a mirrored volume has multiple complete-copy plexes; a bad count in one plex is a different problem from an invalid number of plexes for the whole volume.
Dump the layout as a hierarchy: volume, plex index/type, member records, then disk/extents. That representation usually exposes whether the count field is stale, whether an entry was dropped, or whether the caller has confused pack-wide disk count with disks participating in one plex.
What to inspect
- Compare the plex disk-count field with the extents and disks actually referenced below that plex.
- Check each plex independently instead of validating only the volume-wide disk list.
- If layout data was cached, refresh after disk import, detach, or a failed recovery task before rebuilding the request.
References
- Microsoft VOLMGR entry for STATUS_VOLMGR_NUMBER_OF_DISKS_IN_PLEX_INVALID.
- Microsoft VDS hierarchy of volumes, plexes, and disk extents.
- MS-DMRP glossary definition of a volume plex.
Looking for a different code? Search another status or error code.