Repairing Boot Camp after creating new partition

Hi all, i have this issue too.

Will Chris be able to assist me?

I have recently partitioned my MacOS to allow more space to be partitioned away from Macintosh HD.
(this is so i can have more space to be given to partition to bootcamp)

My bootcamp was running fine in Windows 8.

given what i have read, i would need help for the MBR to detect the new partition created (5th) due to the resizing?

This is probably the single greatest answer I've ever read. This problem has haunted me for years and I've used a variety of hacks to get around it. Your's is by far the best solution. I wish I had found it sooner. Thanks.

Hi Christoper,

I am having the same issue. I tried to extend by bootcamp partition and it wouldn't boot again. I have tried to follow the this thread to fix mine, but it looks so steps are missing.

Here is a print of protective MBR data

Disk size is 490234752 sectors (233.8 GiB)

MBR disk identifier: 0x00004774

MBR partitions:

Number Boot Start Sector End Sector Status Code

1 1 409639 primary 0xEE

2 409640 274257479 primary 0xAF

3 274257480 275527015 primary 0xAB

4 353243136 490233855 primary 0x0C

what do you do before you get to this section below

------

Found valid GPT with protective MBR; using GPT.

Command: r <enter>

Recovery/transformation command: h <enter>

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N):

Hey can you help me..

I have a problem like this.

Thanks before.

Please start a new discussion in Boot Camp . This is an old and long discussion and maintaining context on specific issues is well nigh impossible.

Please do not post any new questions/issues on this specific discussion. Start a new discussion in Boot Camp.

This discussion is very long and old and can only address very specific issue(s).

Restore your disk to a single OSX partition and use Boot Camp to create a partition for Win7 or 8, XP is not supported on Mountain Lion, or Lion.

Yes I know how to fix this without starting over from scratch, but it requires committment to the command line and most people turn into wimps and bail out. So unless you commit to the process I'm not going to put in the investment. In the meantime you can provide the output from the following to comfirm/deny what I think is the likely problem and solution:

sudo gpt -r -vv show disk0

sudo fdisk /dev/disk0

These are read only commands, no modification to the disk is made.

The easiest solution would be to recover the Boot Camp partition with your Winclone image backup.

If you haven't done this then consider doing it after things are working correctly. It can save a lot of inconvenience, pain, and suffering.

http://twocanoes.com/winclone.php

Winclone can't help in this case. Even if it backs up, and can restore both the MBR and GPT, he's already altered the GPT by resizing/splitting a Mac OS partition. What's happened is Disk Utility shouldn't merely warn, it should have disallowed this because while it looks like he has only three partitions, he actually has five:

EFI System, Mac HD, Recovery HD, Internal Storage, Bootcamp. Two of those are hidden. Five partitions. MBR can only hold four. So with GUI tools, he's actually hosed. He'll have to use something like gdisk to create a new hybrid MBR, stuffing GPT partitions 1-4 into MBR partition 1. And then he can put Bootcamp, GPT partition 5, into MBR partition 2 and mark it bootable. Then his computer will boot both systems again.

But that's my speculation until I see both partition maps.

The GUIDs you redacted are not private data, they are partition type GUIDs,However based on the partition start, sizes, and sequence, I'm reasonably certain the GPT is intact. The MBR has been totally obliterated, however. In my opinion this constitutes severe data loss, and I think I'll report this in the Apple dev bug reporter. It should be disallowed, or at least not be so vague as to what will happen and give you the option of effectively losing access to your Windows partition.

Yes a repair is possible. Yes it's easy. If you can format those results with a monospaced font, you can do this.

1. Download the Mac OS X binary of gdisk, a.k.a. GPT fdiskand install it.

2. Tell me how you formatted your partition results with monospaced font so I can more clearly write out the command line sequence for you to follow to create a new hybrid MBR to fix this problem.

3. Tell me the build number of Mac OS X from the About this Mac Window.

Please confirm the GUID for the 5th partition (under index) is EBD0A0A2-B9E5-4433-87C0-68B6B72699C7.

Please confirm the 5th entry for disk0 is BOOTCAMP with this command:

diskutil list