Forum Discussion
MBR2GPT Disk layout validation failed
RAJUMATHEMATICSMSC This is not what i wanted, i wanted to convert the disk while keeping all of my stuff. (See the /allowFullOS switch)
I was facing similar problem as my disk partition was in MBR format but I need it to be GPT format.
Disk validation failed.
Easiest way is solve this problem is as given below.
Go to Disk Manager -> Select disk (0 or 1 ) you want convert and select the partition eg. C -Drive
Right click --> Shrink the disk and put shrink value to 200MB ->OK
Go to CMD with admin mode run the below command
mbr2gpt /validate /disk:0 /allowFullOS -> Enter
Validation is success
Run below command to convert
mbr2gpt /convert /disk:0 /allowFullOS
Disk will be converted to GPT
Go to BIOS and change Legacy to UEFI mode and change boot sequence
Your system will boot with mfg logo
NO Data loss
- markr580Jul 09, 2024Copper Contributor
Palani Samy had to say thx I worked on this all day and though I read this fairly early on I kept looking for an easier way. This was it though.
- allansplaceMay 19, 2024Copper Contributor
Palani Samy I know this post was long ago. I'm having trouble with this. I'm really hoping someone out there can help out!
Background: Windows 10 Pro, use it as web server, need it working and online! Something happened, and it would not boot. Sabotage by someone out there wanting Bitcoin money. After hours of trying to diagnose, I used EasyRE Professional, and it worked. The system boots.
Now, however, I cannot make any backup (clone using Clonezilla). Clonezilla's error message states,
"The disk contains mismatched GPT and MBR partition: /dev/nvme0n1",
"It will confuse Clonezilla and might make the saved image useless or fail to close the disk."
and
"The directory for this inputted image name does NOT exist: /tmp/ocs_onthefly_scr.Pw91VG/d2d-pseudo"
etc. I know this is not a Clonezilla forum. But it seems to me that my system now boots form MBR and not GPT as it has always done previously.
In using MBR2GPT, I get the same error, "Disk layout validation failed for disk 0".
Maybe long-winded, but a little background.
Now the question - your advice states to shrink the drive c: to 200MB. But my entire OS, with website and everything else, is 141GB of 237GB. How could this be shrunk to 200MB?
I'll spend two weeks rebuilding my server if I screw this up, and I now have NO clone as a backup.
Hope someone can help! Thanks! -Allan
- WhyOhWhy1785Oct 14, 2021Copper Contributor
Palani, you're advice caused my windows 10 to corrupt, and for me to lose all of my C drive data as it corrupted as well. Thanks, for absolutely ruining most of my project files.
- Naeem86Oct 15, 2021Copper ContributorThis process should not corrupt your windows installation. You must have done something wrong.
Regardless, it is your responsibility to make sure you know what you are doing, and always take a backup before performing changes at this level.
Please learn to be respectful, we are all community members trying belp each other in absense of Microsoft.- Stefan_MocellinOct 17, 2021Copper Contributor
Thank you for all the help you provided to solve this problem. I have the same message of disk validation failed (see screenshot). And I get this message absolutely regardless from where I try it, within Windows, PE, or recovery. The message WILL REMAIN THE SAME. I even copied the whole HDD to an USB HDD and tried to change that to GPT running the mbr2gpt command, still got the same result. Shrinking the partition and deleting one partition did not help either. not did shrinking the 2nd partition after deleting the 3rd. Are there any further ideas how I can get this to work?
If there are any information missing, please let me know, I will give them to you, as soon as I can and thank you very much for your support!
P.S.
Yes, I deleted the recovery partition years ago and Windows 10 is running just like that in Legacy mode. And also yes, my HW is pretty recent for this PC and supports both UEFI and BIOS, if a detailed information on motherboard/HDDs used is needed, please let me know, though I doubt it is due to the type of mainboard/harddisk that I get this error message.
- Naeem86Sep 22, 2021Copper ContributorI was having this issue, this solved the issue. I shrinked my volume by 2 gb just to be safe.
thanks a bunch!