| Previous | Next |
| VDS_E_LAST_VALID_DISK | VDS_E_ONE_EXTENT_PER_DISK |
VDS_E_INVALID_SECTOR_SIZE
VDS disk properties expose bytes per sector, and the VDS error contract requires every disk holding extents for one volume to use the same valid sector size. This is a topology rule across contributing disks. It is not about NTFS cluster size, stripe interleave, or the allocation unit selected during formatting; those are separate layers and parameters.
Why this state matters
The error can surface when heterogeneous storage is combined or when a provider reports inconsistent geometry. Capture the sector size from every selected disk before volume creation or extension. If only one object reports an unexpected value, verify the provider and device state rather than normalizing the number in the client. VDS needs consistent physical-sector metadata for the volume layout it is asked to build.
Diagnostic focus
- Record bytes-per-sector for every contributing disk alongside its VDS object ID.
- Compare sector sizes across the complete volume input set before validating stripe or block sizes.
- Do not substitute file-system allocation-unit size or
ulStripeSizefor disk sector size. - If provider data changes after refresh, preserve both readings and investigate the storage stack rather than coercing the value.
Technical references
Disk Object · IVdsPack::CreateVolume · VDS_INPUT_DISK · VDS_DISK_EXTENT · VDS common return codes
Looking for a different code? Search another status or error code.