| Previous | Next |
| VDS_E_DISK_NOT_FOUND_IN_PACK | VDS_E_LAST_VALID_DISK |
VDS_E_DUPLICATE_DISK
VDS_INPUT_DISK.diskId identifies each contributing disk. Some layouts contain multiple extents and multiple members, but duplicating a disk record is not a valid way to describe those relationships. Microsoft also documents that a disk cannot contribute more than one plex to the same volume. The topology must use member and plex information rather than repeating one disk as if it were several physical contributors.
Why this state matters
This is usually a request-construction bug, especially when selections from several UI or discovery lists are concatenated. Deduplicate by VDS object ID, not by device pathname or display name. If the design intentionally wants multiple regions from one disk, verify that the called API and volume type support the arrangement instead of encoding it as duplicate disk entries.
Diagnostic focus
- Log the full ordered disk-ID array and detect duplicate GUIDs before calling VDS.
- Trace which discovery or selection list contributed each duplicate entry.
- Distinguish repeated disk IDs from multiple extents already represented by provider allocation policy.
- After deduplication, revalidate disk count, member indexes, and requested topology rather than submitting the shortened array blindly.
Technical references
VDS_INPUT_DISK · IVdsPack::CreateVolume · Disk Object · VDS_DISK_EXTENT · MS-VDS error codes
Looking for a different code? Search another status or error code.