| Previous | Next |
| STATUS_VOLMGR_DISK_LAYOUT_PARTITIONS_TOO_SMALL | STATUS_VOLMGR_DISK_LAYOUT_TOO_MANY_PARTITIONS |
STATUS_VOLMGR_DISK_LAYOUT_PRIMARY_BETWEEN_LOGICAL_PARTITIONS
STATUS_VOLMGR_DISK_LAYOUT_PRIMARY_BETWEEN_LOGICAL_PARTITIONS is specific to the old MBR extended-partition model. Logical drives are described through an Extended Boot Record chain inside one extended partition, whereas primary partitions are top-level MBR entries. A primary entry inserted into the logical-drive sequence is structurally invalid for this check.
This is not a request to delete a primary partition. It means the intended MBR and EBR relationships must be reconstructed and verified before any layout-writing operation is retried.
Safe diagnostic steps
- Map the primary entries, the extended-partition boundary, and every EBR/logical-drive link from a read-only copy of the disk.
- Confirm that the migration or recovery tool did not flatten logical partitions into primary entries or reorder them.
- Use a partition-table backup before repairing EBR structures; logical-drive metadata can be the only map to existing data.
Microsoft: MBR layouts with more than four partitions
Microsoft: IOCTL_DISK_SET_DRIVE_LAYOUT_EX
Microsoft: Volume Manager error codes
Looking for a different code? Search another status or error code.