| Previous | Next |
| ERROR_VOLMGR_PACK_INVALID | ERROR_VOLMGR_PACK_OFFLINE |
ERROR_VOLMGR_PACK_NAME_INVALID
Why this is narrower than a generic disk error: volmgr pack name invalid
ERROR_VOLMGR_PACK_NAME_INVALID has unsigned value 0xC0380032. In the volmgr layer, it rejects a specific contract because the proposed dynamic-disk pack name violates the accepted naming or encoding contract. Diagnosis of this result should follow dynamic-disk pack identity, quorum and replicated configuration log through one controlled state transition.
Dynamic volumes are represented as packs containing disks and volumes; each volume has one or more plexes, and each plex is assembled from members and extents. Indices and counts are relative to the submitted layout generation, while configuration logs are replicated across participating dynamic disks while diagnosing this result. This object model determines which identifiers, counts and ownership state are meaningful for it.
The standard message identifies the immediate condition, but this result also requires the producer API, object topology and attempted state transition. Capture them before an automatic refresh advances the storage generation for it.
Storage facts that change the diagnosis
| Storage diagnostic field | Value |
|---|---|
| Identity and generation | pack GUID and name, online state, primary flag, disk inventory, configuration-log sequence numbers, quorum view and failing transaction ID |
| Narrow experiment | serialize the exact VM_VOLUME_LAYOUT buffer, validate every count and Size field, and compare it with a layout produced by a known-good management API |
| Closest comparison | ERROR_VOLMGR_UNEXPECTED_DISK_LAYOUT_CHANGE |
| Owning object | dynamic-disk pack identity, quorum and replicated configuration log |
| Rejected invariant | the proposed dynamic-disk pack name violates the accepted naming or encoding contract |
Keep this HRESULT as the primary result if rollback or cleanup reports another code; those later values describe recovery, not the first rejected invariant while diagnosing this result.
A/B test for this HRESULT
- Associate it with one caller, one transaction and one target UniqueId.
- Save the pre-call and post-call inventories, including pack GUID and name, online state, primary flag, disk inventory, configuration-log sequence numbers, quorum view and failing transaction ID.
- Use this A/B case for it without touching unrelated storage: serialize the exact VM_VOLUME_LAYOUT buffer, validate every count and Size field, and compare it with a layout produced by a known-good management API.
- Validate both the HRESULT and the on-disk or provider state after the relevant reopen, remount or attach cycle for it.
Compare traces for ERROR_VOLMGR_UNEXPECTED_DISK_LAYOUT_CHANGE and it. The latter page covers a nearby storage boundary, whereas it rejects the proposed dynamic-disk pack name violates the accepted naming or encoding contract. A correct caller should be able to reproduce each case independently.
Mechanism-specific note
Validate the proposed name before beginning a metadata transaction. Record the original Unicode string, normalized form, length and any characters rejected by the management layer while diagnosing it. A display label produced by a UI can include punctuation or truncation that is legal for presentation but not for the pack metadata field.
Corrective action and regression check
Repair the pack configuration through supported dynamic-disk management, preserving GUIDs and the newest valid log sequence; avoid sector-level edits to replicated metadata. The result repair is incomplete until a fresh enumeration and new handle observe the corrected state.
- The original request now reaches success or a documented later status with the intended layout and access mode for it.
- A new enumeration reports internally consistent IDs, counts, geometry and ownership for the object corrected after it.
- The passing state survives the lifecycle transition relevant to it, such as reopen, remount, owner change or detach/attach for it.
- The application still distinguishes it from
ERROR_VOLMGR_UNEXPECTED_DISK_LAYOUT_CHANGEand has no unbounded retry loop.
Avoid broad rescans, forced failovers and metadata deletion until identities and generations are captured. Those actions can make a stale request appear to heal without fixing its caller.
Technical references
- Microsoft: COM error codes for VOLMGR, VHD and SDIAG — documents the supported management path relevant to it.
- Microsoft: Virtual Disk Service object model — defines the volmgr objects used to interpret it.
- Microsoft: Pack object — primary API or object-model reference for the boundary.
- Microsoft: Virtual Disk Service common return codes — use this source to verify volmgr state and parameters for it.
Looking for a different code? Search another status or error code.