| Previous | Next |
| VDS_E_MEMBER_MISSING | VDS_E_UNEXPECTED_DISK_LAYOUT_CHANGE |
VDS_E_PLEX_REGENERATING
This status applies to the plex as a whole. It differs from VDS_E_MEMBER_REGENERATING, which identifies a specific member already in recovery. A plex-level regenerating state can block operations because the redundant copy or parity layout has not reached a stable health state. VDS exposes plex transition state separately from status and health for exactly this kind of lifecycle decision.
Why this state matters
Query the plex properties and the containing volume, then follow the existing asynchronous repair or recovery result. If regeneration stalls, enumerate the plex extents to locate storage errors. Do not remove or break the rebuilding plex merely because another plex is online; doing so can reduce redundancy or discard the copy VDS is currently reconstructing.
Diagnostic focus
- Capture the target plex GUID, health, status, and transition state.
- Check the asynchronous recovery result that initiated regeneration.
- Inspect all plex extents and participating disks if progress stops.
- Wait for a terminal rebuild state before starting another plex topology operation.
Technical references
MS-VDS error codes · VDS_VOLUME_PLEX_PROP · IVdsVolumePlex · IVdsVolumePlex::Repair · VDS Volume Object
Looking for a different code? Search another status or error code.