What does HRESULT 0x80042525 (VDS_E_INVALID_STRIPE_SIZE) mean?

 
Previous Next
VDS_E_INVALID_MEMBER_ORDER VDS_E_INVALID_DISK_COUNT

VDS_E_INVALID_STRIPE_SIZE

Stripe size is not a generic tuning parameter for every VDS volume. VDS_VOLUME_PLEX_PROP.ulStripeSize is meaningful only for striped and parity plexes; for other plex types it should be zero. IVdsPack2::CreateVolume2 is even more explicit for volume creation: the stripe size must be 65536 bytes for VDS_VT_STRIPE or VDS_VT_PARITY, and zero for other volume types.

Why this state matters

This makes the HRESULT a parameter/topology mismatch, not a disk-performance diagnosis. A caller that carries a previous RAID stripe value into a simple or mirrored volume request can fail before any extents are allocated. Record both the volume type and raw stripe-size argument so configuration-layer unit conversions or stale defaults are visible.

Diagnostic focus

  • Capture the exact byte value supplied as stripe size and the selected VDS_VOLUME_TYPE.
  • For CreateVolume2, verify 65536 bytes for stripe/parity and zero for all other types.
  • When inspecting an existing plex, read ulStripeSize together with the plex type rather than alone.
  • Check configuration code for sectors, KiB, or blocks being passed where the API requires bytes.

Technical references

IVdsPack2::CreateVolume2 · VDS_VOLUME_PLEX_PROP · VDS_VOLUME_PLEX_TYPE · VDS_VOLUME_TYPE · IVdsPack::CreateVolume


Looking for a different code? Search another status or error code.