| Previous | Next |
| VDS_E_UNABLE_TO_FIND_SYSTEM_DISK | VDS_E_SYSTEM_DISK |
VDS_E_INCORRECT_SYSTEM_VOLUME_EXTENT_INFO
This status is specifically about VDS system-volume discovery. The catalog reports multiple disk extents where the role-resolution path expected a topology suitable for determining the system disk. It is not a universal diagnosis of volume corruption, nor does it say which partition table field is wrong.
Why this state matters
The useful evidence is the complete extent map and the VDS disk-role flags. Software-defined storage, dynamic volumes, stale provider state, or an unexpected layout change can all make a high-level “one system volume, one disk” assumption fail. Before repairing metadata, determine whether the extent map itself is real and stable and whether VDS has been refreshed after the topology change.
Diagnostic focus
- Capture every extent for the current system volume with disk ID, offset, and length.
- Compare the extent owners with disks carrying SYSTEM_DISK and dynamic-disk flags.
- Check for recent mirror, migration, clone, or provider operations that changed volume layout outside the current VDS client.
- Refresh the VDS state and preserve both the pre-refresh and post-refresh maps for diagnosis.
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.