| Previous | Next |
| STATUS_VOLMGR_PACK_CONFIG_ONLINE | STATUS_VOLMGR_PACK_LOG_UPDATE_FAILED |
STATUS_VOLMGR_NOT_PRIMARY_PACK
The selected pack does not have the primary-pack role
STATUS_VOLMGR_NOT_PRIMARY_PACK is a pack-role mismatch. Volume Manager received an operation that is valid only for the primary pack, while the supplied pack identifier refers to another pack.
A dynamic provider can manage packs containing multiple dynamic disks. The public VOLMGR error table defines the primary-pack condition but does not document a rule that lets callers infer the primary pack from disk order, drive letters, or the first pack returned by enumeration.
Resolve the pack identity from current Volume Manager state and log the pack identifier passed to the failing call. This is especially important after foreign-disk import or migration, where assumptions carried from the source computer can point management code at the wrong pack.
What to inspect
- Enumerate current packs and record the identifier and state of the pack selected by the operation.
- Check whether a migration or foreign-disk import changed which pack the caller intended to manage.
- Do not choose a primary pack by disk number or drive-letter order unless the documented interface explicitly returns that relationship.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_NOT_PRIMARY_PACK.
- Microsoft VDS pack object and dynamic-provider pack membership.
- Microsoft guidance for importing Foreign dynamic disks.
Looking for a different code? Search another status or error code.