| Previous | Next |
| VDS_E_PLEX_IS_HEALTHY | VDS_E_PLEX_MISSING |
VDS_E_PLEX_LAST_ACTIVE
Only mirrored volumes have multiple plexes, and each plex contains a copy of the volume data. Removing a plex releases its extents. Microsoft documents that IVdsVolume::RemovePlex cannot remove the last plex of a volume at all; the VDS error catalog separately protects the last healthy plex when other plexes are stale, missing, or otherwise unusable. The remaining active copy is therefore a data-availability boundary.
Why this state matters
The correct diagnosis starts with plex status and health. A mirror may still enumerate several plex objects while only one is usable. Count healthy active plexes, map each to its extents, and identify the exact plex ID selected for removal or break. If the goal is to delete the entire volume, use the volume deletion workflow rather than dismantling its final surviving plex.
Diagnostic focus
- Enumerate all plexes and capture each plex ID, status, health, transition state, and size.
- Identify stale or missing plexes before targeting the only healthy copy.
- Confirm whether the intended action is mirror maintenance or complete volume deletion; the APIs have different semantics.
- Do not choose a plex by enumeration order after health changes; select the verified plex ID from current properties.
Technical references
Volume Plex Object · VDS_VOLUME_PLEX_PROP · MS-VDS IVdsVolume::QueryPlexes · IVdsVolume::RemovePlex · IVdsVolumePlex
Looking for a different code? Search another status or error code.