| Previous | Next |
| VDS_E_DISTINCT_VOLUME | VDS_E_PARTITION_NON_DATA |
VDS_E_VOLUME_NOT_FOUND_IN_PACK
Volumes are created within a pack and IVdsVolume::GetPack exposes the containing pack relationship. Pack-scoped topology operations must use volumes from that disk group. A volume GUID can identify a real VDS object and still be invalid for a method invoked on another pack. This HRESULT marks that ownership mismatch.
Why this state matters
Stale selections are a common source of the problem after disk migration, mirror changes, or reenumeration. Do not match a volume to a pack by drive letter: access paths can change and are not pack identity. Enumerate the pack volumes or resolve the volume's containing pack, then compare VDS object IDs immediately before constructing the request.
Diagnostic focus
- Record the target volume ID and the pack object ID used to issue the operation.
- Resolve the volume's current containing pack instead of relying on a cached UI grouping.
- Check recent migration or topology changes that could have invalidated the original selection.
- Do not substitute volume names, GUID pathnames, or drive letters for the VDS pack relationship.
Technical references
Volume Object · IVdsVolume · Pack Object · MS-VDS storage object relationships · IVdsPack::MigrateDisks
Looking for a different code? Search another status or error code.