I've included a screenshot taken in a disk editing program of my GPT system drive C. It is just the data partition not the EFI partition. Notice that it makes reference to MIBRL. My other non-bootable GPT drives have the normal NTLDR in sector 0. I'm curious as to those folks with a bootable GPT data partition have in their sector 0. Googling for MIBRL shows only a couple of entries which are no help at all.
Are you having issues with booting? Those are just canned error messages built into the code.
I'm actually trying to shoot a problem I am having using StorageCraft's Virtual Boot (VB) process. This allows me to boot a backup disk image to be opened up in VirtualBox or HyperV. The Virtual Boot process is supposed to create an MBR since the bootloader is on the EFI partition which is not on the data backup image. I'm thinking that my sector 0 is screwed up which might be the cause of VB failing.
I've been working with the StorageCraft tech guys and they can't figure out my problem. They did send me one of their GPT data images which does boot fine using VB. Looking at their sector 0 it is a normal sector 0 with NTLDR. This is what I see when I mount their backup, it hasn't been modified by VB at this point.
So all I need to ascertain is if anyone with a GPT disk has the same MIBRL in their sector 0 on their data partition.
Here are a couple of mine. Both of these are system drives that boot Windows. The first is pure GPT with protective MBR.
The second is hybrid MBR/GPT disk and I copied in the first 440 bytes manually (up to position x1B8). This was to force AHCI mode when booting in Legacy (not UEFI mode) on the same disk based on this [HOWTO] Boot Macs with Intel Chipset in AHCI Win7 Vista XP Linux
After the first 440 bytes is the MBR partition table. In the pure GPT one above there is only one partition type EE (x01C2) covering the whole disk.
As you can see in both cases the beginning of Sector 1 contains the start of the first GPT partition table.
Here is the beginning of Data partition :
Only examine the data partition on your disk. It looks like you examined the physical disk which is why the EFI stuff shows up. I use the same program you use btw. Disk edit the partition your OS is on. As I mentioned I'm only asking for this info to see if it might be affecting Virtual Boot. VB might see the MIBRL string and get confused if it's expecting something else.
Yep. Notice the difference between yours and mine? Is yours a Windows partition?
Yes it is my C drive. I really don't think these messages are interesting - it depends what you used to partition the drive and will only be displayed if you boot in legacy mode and the code before fails for some reason. So it doesn't matter if it says "MIBRL not found" or "BOOTMGR not found" etc.
In fact to add the enabling of AHCI the guy who wrote the bootloader I use shortened these messages and just put "missing operating system" and dropped the "press ctrl + alt + delete" stuff so he could fit in his code (see my second picture).
Quote
