Then typeĬode: bootsect /nt60 X: /mbr where X: is the driver letter for your BOOTCAMP disk. Run EasyBCD -> Useful Utilities -> EasyBCD Power Console.
You can boot Bubba and use Windows to add the MBR boot code for BOOTCAMP. Use fdisk to change the boot partition to partition 2 (BOOTCAMP). The MBR is set to boot the EFI partition which is wrong (the boot code in the EFI partition's VBR only displays "Non-system disk.Press any key to reboot."). Converting may delete whatever is within the first blocks of the disk before the first partition (but there shouldn't be anything there) and there won't be any space for an EFI partition (which is not necessary anyway).ĭisk3, Bay 2, "WDC WD3200AAKS-00L9A0" "BOOTCAMP", has a single Windows partition that has BOOTMGR in its VBR so it is probably bootable, but there is no boot code in the MBR so the disk itself will not be bootable. Are you able to select this disk in Parallels? If not, you could use iPartition or gpt fdisk to convert it from an MBR disk to a hybrid GPT/MBR disk. Both the "System Reserved" and "Bubba" partitions have BOOTMGR in their VBR and are therefore probably bootable. Not a problem.ĭisk2, Bay 1, "WDC WD1002FBYS-02A6B0", "Bubba" has just an MBR - it has no GPT. It looks like standard MBR code but I don't think it came from Windows. The -u option of fdisk will erase MBR code but you don't really need to.ĭisk1, Bay 3, "WDC WD1002FBYS-02A6B0", "Big Momma" has some code in the MBR also. Disks that don't have legacy OS's (Windows/Linux) probably don't need MBR code. I don't know what it does - something about EFI, udf, and GPT. dumpvols.sh 2>&1 | cat > dumpvols_result.txtUse the above command to get the state of your disks before making any changes to your partitions.ĭisk0, Bay 4, "WDC WD1001FALS-00J7B0", "Big Daddy" has some code in the MBR that I haven't seen before.
0 kommentar(er)
