| Previous | Next |
| VDS_E_UNABLE_TO_FIND_BOOT_DISK | VDS_E_GET_SAN_POLICY |
VDS_E_INCORRECT_BOOT_VOLUME_EXTENT_INFO
This HRESULT is not a generic “bad partition table” code. The VDS catalog says multiple disk extents were reported for the boot volume where the boot-volume discovery path expected a different topology. A volume extent describes a byte range on a disk; a volume that spans disks or has unexpected extent reporting can therefore break code that is trying to associate the current boot volume with one disk role.
Why this state matters
The diagnostic target is the extent map returned for the boot volume and the VDS disk-role flags. Do not repair the MBR or GPT merely because the word extent appears in the message. First verify whether the volume is actually multi-extent, whether storage virtualization is presenting an unusual mapping, or whether the VDS/provider view is stale.
Diagnostic focus
- Capture the complete volume extent list, including disk IDs, starting offsets, and extent lengths.
- Identify which disk carries
VDS_DF_BOOT_DISKand compare that role with the reported extent map. - Refresh or reenumerate VDS after storage topology changes before concluding that on-disk metadata is damaged.
- Distinguish this system-discovery failure from
VDS_E_VOLUME_SPANS_DISKS, which is an explicit operation precondition for a general volume.
Technical references
VDS_DISK_FLAG · VDS_DISK_PROP · IVdsService::Refresh · IVdsService::Reenumerate · MS-VDS error codes
Looking for a different code? Search another status or error code.