| Previous | Next |
| VDS_E_BAD_BOOT_DISK | VDS_E_VOLUME_MIRRORED |
VDS_E_LOG_UPDATE
This error occurs at the configuration persistence boundary. In a dynamic pack, topology changes must be reflected in volume-manager metadata on participating disks. The published VDS message states that at least one disk failed the log update, so the operation may have reached further than a simple validation error. The immediate concern is inconsistent metadata generations across pack members.
Why this state matters
Capture the complete pack membership and identify disks with I/O or read-only failures. Requery pack, disk, volume, and plex state before repeating the operation. A blind retry can write another generation of metadata and make the original partial update harder to analyze. If the pack remains online, do not assume every configuration copy is healthy solely because volumes are currently accessible.
Diagnostic focus
- List every disk in the affected pack and record online/read-only state.
- Collect storage I/O and volume-manager driver events for the log update interval.
- Requery the pack topology and compare current volume and plex state with the requested change.
- Avoid repeated metadata-changing operations until the failing disk or path is identified.
Technical references
MS-VDS error codes · VDS Pack Object · Basic and Dynamic Disks · VDS_VOLUME_PROP · VDS_VOLUME_PLEX_PROP
Looking for a different code? Search another status or error code.