| Previous | Next |
| VDS_E_INVALID_PLEX_TYPE | VDS_E_NO_HEALTHY_DISKS |
VDS_E_INVALID_PLEX_BLOCK_SIZE
This HRESULT is plex-specific. The VDS catalog requires a nonzero plex block size, while plex properties separately expose stripe interleave size and the number of members. The status should not be conflated with VDS_E_INVALID_BLOCK_SIZE, whose published text describes failure to find a nonzero stripe-size or disk-sector-size basis. Similar names point to different validation boundaries.
Why this state matters
The diagnostic path should identify the plex object and its layout first. Query plex properties and extents, then compare the provider-reported block geometry with the disk sector sizes and stripe semantics relevant to that plex. If the value is missing from provider state, changing file-system format settings will not repair the lower-level plex metadata.
Diagnostic focus
- Log the plex ID, type, size, stripe size, member count, and every contributing extent.
- Keep this HRESULT distinct from the volume-level
VDS_E_INVALID_BLOCK_SIZEin telemetry and remediation. - Compare disk sector-size reports across the disks contributing to this plex.
- Investigate provider or topology metadata before changing file-system allocation-unit settings.
Technical references
VDS_VOLUME_PLEX_PROP · IVdsVolumePlex::QueryExtents · Disk Object · VDS_VOLUME_PLEX_TYPE · VDS common return codes
Looking for a different code? Search another status or error code.
