| Previous | Next |
| VDS_S_EXTEND_FILE_SYSTEM_FAILED | VDS_S_DISK_IS_MISSING |
VDS_S_MBR_BOOT_MIRRORED_TO_GPT
VDS can create a mirrored dynamic volume across disks with different partition styles, but data redundancy and firmware bootability are not the same property. This warning says the primary boot volume originated on an MBR disk and the new plex is on GPT. The mirror can protect volume data while the machine still lacks a boot path that firmware and Windows Boot Manager can use from the secondary disk.
Why this state matters
Diagnosis should separate mirror health from boot-environment preparation. Query the volume and plex state to confirm that synchronization completed, then inspect firmware mode and the system partition on the secondary disk. Microsoft documents additional steps for booting from GPT mirrors, including boot files and BCD configuration. Do not call the secondary plex bootable merely because VDS reports the mirror online.
Diagnostic focus
- Confirm both plexes are online and no regeneration remains in progress.
- Identify whether the machine boots through BIOS/MBR or UEFI/GPT firmware paths.
- Inspect the secondary disk for the system partition and required boot-environment files.
- Test a documented secondary-disk boot path before relying on the mirror for boot recovery.
Technical references
MS-VDS error codes · Set up dynamic boot partition mirroring on GPT disks · BCDBoot command-line options · VDS_VOLUME_PLEX_PROP · VDS_VOLUME_STATUS
Looking for a different code? Search another status or error code.