Repairing Boot Camp after creating new partition

Probably. Because that Windows only utility would have only updated the MBR, which you just nuked with gdisk when you created a new hybrid MBR. You didn't tell me until now that you used a Windows utility to do the resizing, or I wouldn't have told you to create a new hybrid MBR.

I think that Windows volume is SOL unless you have a copy of the MBR reported from fdisk, before it was replaced by gdisk.

Whatever you do, don't let chkdsk try to repair the NTFS volume.

What is the result from

sudo fdisk /dev/disk0

Ok, here's the output from fdisk:

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>

2: AF 25 127 15 - 1023 254 63 [ 409640 - 585937496] HFS+

3: AB 1023 254 63 - 1023 254 63 [ 586347136 - 1269536] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [ 587618304 - 389154831] HPFS/QNX/AUX

and the GPT from gdisk:

Disk /dev/disk0: 976773168 sectors, 465.8 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): E2BACA2E-849F-4BCF-B5FA-A79C88CFFA86

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 976773134

Partitions will be aligned on 8-sector boundaries

Total free space is 1638 sectors (819.0 KiB)

Number Start (sector) End (sector) Size Code Name

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 586347135 279.4 GiB AF00 Untitled

3 586347136 587616671 619.9 MiB AB00 Recovery HD

4 587618304 976773134 185.6 GiB 0700 Microsoft basic data

and finally the MBR from gdisk:

Disk size is 976773168 sectors (465.8 GiB)

MBR disk identifier: 0xBBC11FA9

MBR partitions:

Number Boot Start Sector End Sector Status Code

1 1 409639 primary 0xEE

2 409640 586347135 primary 0xAF

3 586347136 587616671 primary 0xAB

4 * 587618304 976773134 primary 0x07

I don't know how to help you when this sort of thing happens:

3:15pm

Disk identifier (GUID): E2BACA2E-849F-4BCF-B5FA-A79C88CFFA86

4 587618304 683321343 45.6 GiB 0700 WIN8

5 683321344 976773134 139.9 GiB 0700 Microsoft basic data

45 minutes later

Disk identifier (GUID): E2BACA2E-849F-4BCF-B5FA-A79C88CFFA86

4 587618304 976773134 185.6 GiB 0700 Microsoft basic data

Your GPT has changed inside of 45 minutes. So I don't know what you did, or how you got here, and I can't tell you a thing about whether the state of your partition schemes will work or not.

Ok, sorry I've been jumping around alot with the steps I took. I took your suggestion to blow away the MBR and create a fresh one. However, I couldn't figure out how to merge the two partitions in the GPT (4 and 5) which were "left over" after I merged my two windows partitions into one using a windows utility. So I blew the entire GPT away and made a new one using gdisk taking care to keep the exact same sector #s as the original (and merging 4 and 5 into one new partition to reflect the one Windows partition). That's how the GPT changed and I then blew away the MBR and created a fresh one based on that new GPT with only 4 entries. I really jumped the gun on a few of these steps, but does that GPT/MBR setup look like it'll be stable?

I can't answer your question.

When you use Windows utilities to resize NTFS, it only updates the MBR. Often this will also corrupt the GPT primary table, and the backup GPT is nerfed. And then when the GPT is replaced, it nerfs the tail end of the NTFS volume often corrupting it. So I have no idea what the state of the Windows volume is in, or whether the entries in either GPT or MBR are even remotely correct.

There's an easy, risky way of finding out if the NTFS volume is OK, which is to try and start Windows from it. If it's not right, it's possible Windows will corrupt the file system in the process of starting up from it.

Also possible is to run chkdsk (not chkdsk /f) while booted from a Windows DVD, and see what it finds. If there are no problems then try chkdsk /f.

Not easy, but much safer is booting from a Linux livecd that has current ntfs-3g utilities on it, like Fedora 18. Run

ntfsresize -i

ntfsresize -c

ntfsresize -n

Those are: get info, check if ready for resize, and attempt to resize without actually make changes (dry run).

If the volume is OK, check won't report anything, and resize will basically say the current size is the max size for the partition. Then you can run a chkdsk /f from the Windows DVD.

You the man Murphy, you the man!! (...you too OP) This thread solved my problem!

Dear All,

I have a very similar problem and after having made a lot of attempts to solve it and research on how to do this I think it suits well to this this thread (… hope I'm not wrong).

The situation on my MacBookPro (6,2) is as follows:

BEFORE: I had 320 GB disk with two partitions:

• one OSX Snow Leopard (10.6.8)

• one Windows 7 BOOTCAMP partition of about 34 GB (I could run windows either via Virtual Box directly out of OSX or when rebooting and holding down the alt-key).

AFTER(Now actually): I have a 1000 GB disk with two partitions:

• one OSX Mountain Lion (10.8.2)

• one Windows 7 BOOTCAMP partition of about 65 GB

For OSX I reinstalled everything from scratch with the new OSX version whereas for the BOOTCAMP partition I copied (I really DON'T want to reinstall all the Window stuff, I have so many things already nicely configured on there so…NO :)) the existing BOOTCAMP partition from my old drive as follows:

1. I used the bootcamp assistant in my new OSX (10.8.2) to create the 65 GB partition but instead of installing win7 at reboot I used clonezilla to transfer the old partition's content onto the newly created 65GB partition.
2. This didn't startup yet, so I booted the mac with my Win7 DVD and fixed to MBR and everything else possible … (cmd line: bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd)
3. The partition is now recognized at startup when I hold the alt key (I can choose to start from the BOOTCAMP partition) but when booting from it it gives me the error: "BOOTMGR is missing"
4. Furthermore when I attempt to choose a startup volume in system settings the BOOTCAMP partition is also listed.
5. The windows 7 installation/repair CD also nicely detects the partition and also doesn't complain about any errors.

I think the data is perfectly copied, the partition is present but there must still be a small mistake in the partition table which I can't figure out.

Any ideas?

Thank you very much in advance!

Best regards,

Fab

BOOTMGR is missing means it got stuck at the boot sector of the VBR. It's unlikely this problem is partitioning related but you can post:

sudo fdisk /dev/disk0

sudo gpt -r -v show disk0

The BCD probably needs to be completely rebuilt. From the Windows install DVD, command prompt:

• bcdedit /export C:\BCD_Backup
• c:
• cd boot
• attrib bcd -s -h -r
• ren c:\boot\bcd bcd.old
• bootrec /RebuildBcd

hi christopher,

thanks for your quick reply!

here we go, the two outputs in the command line you requested:

sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 121601/255/63 [1953525168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>

2: AF 1023 254 63 - 1023 254 63 [ 409640 - 1826171904] HFS+

3: AB 1023 254 63 - 1023 254 63 [1826581544 - 1269536] Darwin Boot

*4: 0B 1023 254 63 - 1023 254 63 [1827852288 - 125671424] Win95 FAT-32

sudo gpt -r -v show disk0

gpt show: disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168

gpt show: disk0: Suspicious MBR at sector 0

start size index contents

0 1 MBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 1826171904 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

1826581544 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

1827851080 1208

1827852288 125671424 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1953523712 1423

1953525135 32 Sec GPT table

1953525167 1 Sec GPT header

As you suggested I also executed the commands in the Win7 install DVD command prompt but unfortunately without success. I mean yes I was sucessful in executing the commands but after a reboot the error message still remains the same: "BOOTMGR is missing".

Message was edited by: fab.b

Message was edited by: fab.b

Also, the ID for the partition type is incorrectly set to 0B. It should be 07. I don't know if this is related to the boot problem.

*4: 0B 1023 254 63 - 1023 254 63 [1827852288 - 125671424] Win95 FAT-32

OS X's 'fdisk' can be used to change it. Type this:

sudo fdisk -e /dev/disk0

You'll see this:

fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory

Enter 'help' for information

fdisk: 1>

At that interactive prompt type

fdisk: 1> setpid 4

You'll see:

Partition id ('0' to disable) [0 - FF]: [EE] (? for help)

Type:

07

write

okay this is changed, now the partitions look as follows:

sudo fdisk /dev/disk0

[...]

*4: 07 1023 254 63 - 1023 254 63 [1827852288 - 125671424] HPFS/QNX/AUX

but unfortunately without any change in the failure to boot 😟

See post from 3 days ago with the bullet list including "bcdedit".