| Previous | Next |
| VDS_E_INVALID_STRIPE_SIZE | VDS_E_INVALID_EXTENT_COUNT |
VDS_E_INVALID_DISK_COUNT
Disk count is constrained by the operation and volume type. A simple volume uses one input disk; spanned, striped, mirrored, and parity volumes use one VDS_INPUT_DISK record for each contributing disk. CreateVolume2 also documents a hard array limit of 32 input objects because Windows permits no more than 32 disks in one volume.
Why this state matters
The error should be investigated at the request boundary. The number of array elements, the declared lNumberOfDisks, and the desired volume type must agree. It is possible to have a perfectly valid set of disk objects but an invalid count for the topology. Do not remove disks one by one until the call succeeds; that can silently produce a different storage layout.
Diagnostic focus
- Log the declared disk count and the actual number of initialized
VDS_INPUT_DISKrecords. - Compare the count with the selected simple, span, stripe, mirror, or parity volume type.
- Enforce the documented 32-input limit before entering
CreateVolume2. - Validate that filtered or failed disks did not leave the count field out of sync with the array.
Technical references
IVdsPack::CreateVolume · IVdsPack2::CreateVolume2 · VDS_INPUT_DISK · Volume Object · VDS_VOLUME_TYPE
Looking for a different code? Search another status or error code.
