Forum Discussion
MBR2GPT Disk layout validation failed
When i try to run
mbr2gpt /validate /disk:0 /allowFullOS
i get the following output
MBR2GPT: Attempting to validate disk 0 MBR2GPT: Retrieving layout of disk MBR2GPT: Validating ...
I had the same problem and here's what I did to fix mine problem. in short.
1) The drive must have 3 or less partitions.
2) I believe you need some free space at the end of the drive (guess only, not confirmed)
In my case my system drive happens to have 4 partitions. 2 of which are the recovery partition, one of which was a left behind from prior windows upgrade. I manually removed the unneeded recovery partition which happens to be the last partition in my drive, and leaving my system with only 3 partitions and almost 500M of space at the end.
The reason I 'guess' some space is needed at the end of the drive is because someone else on this thread has mentioned as the shrink their partition, the validation started working, and as my reading on GPT goes, it suggest GPT does write a backup partition table at the end of the drive. The space required should be very tiny IMO, but no space at all could 'maybe' a cause of the problem?
1) The drive must have 3 or less partitions.
2) I believe you need some free space at the end of the drive (guess only, not confirmed)
In my case my system drive happens to have 4 partitions. 2 of which are the recovery partition, one of which was a left behind from prior windows upgrade. I manually removed the unneeded recovery partition which happens to be the last partition in my drive, and leaving my system with only 3 partitions and almost 500M of space at the end.
The reason I 'guess' some space is needed at the end of the drive is because someone else on this thread has mentioned as the shrink their partition, the validation started working, and as my reading on GPT goes, it suggest GPT does write a backup partition table at the end of the drive. The space required should be very tiny IMO, but no space at all could 'maybe' a cause of the problem?
- I tried shrinking the drive as suggested in other posts by 200mb and 2gb then running the command again. Making those changes did not help I still got the same error.
