You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Scotch_Brawth Author

Level 3

827 points

Repairing Boot Camp after creating new partition

I'm running OS X 10.8 and Windows 7 x64 Pro.

After properly setting up Boot Camp to dual-boot Windows on my Mac mini, I decided to test whether or not it was true that creating another partition (a data partition for OS X) would interfere with Boot Camp. Wikipedia claims it does interfere but without citing a source, whilst the Boot Camp documentation itself only specifies that the disk must be a single partition _prior_ to setup - there's no mention of whether the disk must be _kept_ that way afterwards.

I opened Disk Utility, reduced the size of my OS X parition from 420GB to 80GB, and created a new partition in the unallocated space. Here's how it looks now:

When I attempted to proceed with the process, I did receive a warning that doing this (and I quote), "may" cause problems with Boot Camp. Seeing as it was inconclusive, I thought I'd give it a shot - nothing ventured…

Of course, it borked Boot Camp, otherwise I wouldn't be posting here. Whilst OS X boots just fine, the Boot Camp partition now no longer shows up in the Startup Manager, though it does in the Startup Disk prefPane. If I do attempt to boot into Boot Camp, I receive the following message on a black screen:

No bootable device --- insert boot disk and press any key

The advice given to someone who had this same problem was, "fix your damaged Boot Camp volume." But I'm at a loss as to how to do that.

So, anyone know how to proceed now so that I can keep my partitions as is, whilst fully restoring normal Boot Camp functionality?

Mac mini (Mid 2011), Mac OS X (10.7.4)

Posted on Jul 26, 2012 11:28 PM

1,534 replies

Dec 11, 2012 1:44 PM in response to Coffeecoco

@Coffeecoco

You read the wrong response. There's a response for you and one for Alex Senkevich and it looks like you've got them mixed.

Dec 11, 2012 1:52 PM in response to Christopher Murphy

Could you please assist me sir?

I dont feel they are able to assist because my setup is so unique with the raid and all

Is the reason why my BOOTCAMP wont boot due to the identifier ?

All i get is a blackscreen when booting Windows 7

Dec 11, 2012 2:03 PM in response to Coffeecoco

The RAID has nothing to do with this, the Windows volume is on another disk entirely.

This entry in the MBR appears to have an incorrect type ID, it should be 07:

*3: 0C 859 181 27 - 1010 15 29 [-1429741568 - 351989760] Win95 FAT32L

But I don't know if that's what's preventing it from booting or not. That can be fixed with gdisk by creating a new hybrid MBR from the recovery menu, and in your case you'll add partitions 2 3 4 and make 3 bootable. Then write out the new partition tables with the w command.

You could also report the result from:

sudo dd if=/dev/disk0 count=1 2>/dev/null | hexdump -C

Dec 11, 2012 2:09 PM in response to Christopher Murphy

sh-3.2# sudo dd if=/dev/disk0 count=1 2>/dev/null | hexdump -C

00000000 33 c0 8e d0 bc 00 7c 8e c0 8e d8 be 00 7c bf 00 |3.....|......|..|

00000010 06 b9 00 02 fc f3 a4 50 68 1c 06 cb fb b9 04 00 |.......Ph.......|

00000020 bd be 07 80 7e 00 00 7c 0b 0f 85 0e 01 83 c5 10 |....~..|........|

00000030 e2 f1 cd 18 88 56 00 55 c6 46 11 05 c6 46 10 00 |.....V.U.F...F..|

00000040 b4 41 bb aa 55 cd 13 5d 72 0f 81 fb 55 aa 75 09 |.A..U..]r...U.u.|

00000050 f7 c1 01 00 74 03 fe 46 10 66 60 80 7e 10 00 74 |....t..F.f`.~..t|

00000060 26 66 68 00 00 00 00 66 ff 76 08 68 00 00 68 00 |&fh....f.v.h..h.|

00000070 7c 68 01 00 68 10 00 b4 42 8a 56 00 8b f4 cd 13 ||h..h...B.V.....|

00000080 9f 83 c4 10 9e eb 14 b8 01 02 bb 00 7c 8a 56 00 |............|.V.|

00000090 8a 76 01 8a 4e 02 8a 6e 03 cd 13 66 61 73 1c fe |.v..N..n...fas..|

000000a0 4e 11 75 0c 80 7e 00 80 0f 84 8a 00 b2 80 eb 84 |N.u..~..........|

000000b0 55 32 e4 8a 56 00 cd 13 5d eb 9e 81 3e fe 7d 55 |U2..V...]...>.}U|

000000c0 aa 75 6e ff 76 00 e8 8d 00 75 17 fa b0 d1 e6 64 |.un.v....u.....d|

000000d0 e8 83 00 b0 df e6 60 e8 7c 00 b0 ff e6 64 e8 75 |......`.|....d.u|

000000e0 00 fb b8 00 bb cd 1a 66 23 c0 75 3b 66 81 fb 54 |.......f#.u;f..T|

000000f0 43 50 41 75 32 81 f9 02 01 72 2c 66 68 07 bb 00 |CPAu2....r,fh...|

00000100 00 66 68 00 02 00 00 66 68 08 00 00 00 66 53 66 |.fh....fh....fSf|

00000110 53 66 55 66 68 00 00 00 00 66 68 00 7c 00 00 66 |SfUfh....fh.|..f|

00000120 61 68 00 00 07 cd 1a 5a 32 f6 ea 00 7c 00 00 cd |ah.....Z2...|...|

00000130 18 a0 b7 07 eb 08 a0 b6 07 eb 03 a0 b5 07 32 e4 |..............2.|

00000140 05 00 07 8b f0 ac 3c 00 74 09 bb 07 00 b4 0e cd |......<.t.......|

00000150 10 eb f2 f4 eb fd 2b c9 e4 64 eb 00 24 02 e0 f8 |......+..d..$...|

00000160 24 02 c3 49 6e 76 61 6c 69 64 20 70 61 72 74 69 |$..Invalid parti|

00000170 74 69 6f 6e 20 74 61 62 6c 65 00 45 72 72 6f 72 |tion table.Error|

00000180 20 6c 6f 61 64 69 6e 67 20 6f 70 65 72 61 74 69 | loading operati|

00000190 6e 67 20 73 79 73 74 65 6d 00 4d 69 73 73 69 6e |ng system.Missin|

000001a0 67 20 6f 70 65 72 61 74 69 6e 67 20 73 79 73 74 |g operating syst|

000001b0 65 6d 00 00 00 63 7b 9a 06 4a 00 00 00 00 00 00 |em...c{..J......|

000001c0 02 00 ee 7f 0e 19 01 00 00 00 27 40 06 00 00 7f |..........'@....|

000001d0 0f 19 af 4a df 4b 28 40 06 00 78 99 bd aa 80 b5 |...J.K(@..x.....|

000001e0 db 5b 0c 0f dd f2 00 e0 c7 aa 00 f0 fa 14 00 0f |.[..............|

000001f0 de f2 af f8 d4 ac 00 d0 c2 bf 88 b8 1d 29 55 aa |.............)U.|

00000200

sh-3.2#

Dec 11, 2012 2:30 PM in response to Christopher Murphy

I did as you said now please view the changes

Recovery/transformation command (? for help): p

Disk /dev/disk0: 3907029168 sectors, 1.8 TiB

Logical sector size: 512 bytes

Disk identifier (GUID): 7E4EFAC0-0F27-43D9-B1AE-DC690095B4A7

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 3907029134

Partitions will be aligned on 8-sector boundaries

Total free space is 263789 sectors (128.8 MiB)

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

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 2864961951 1.3 TiB AF00 Untitled 1

3 2865225728 3217215487 167.8 GiB 0700 BOOTCAMP

4 3217215488 3907029127 328.9 GiB AF00 Apple_HFSX_Untitled_2

Recovery/transformation command (? for help): o

Disk size is 3907029168 sectors (1.8 TiB)

MBR disk identifier: 0x00004A06

MBR partitions:

Number Boot Start Sector End Sector Status Code

1 1 409639 primary 0xEE

2 409640 2864961951 primary 0xAF

3 * 2865225728 3217215487 primary 0x07

4 3217215488 3907029127 primary 0xAF

Recovery/transformation command (? for help):

sh-3.2# sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: -1539437/4/63 [-387938128 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 0 0 2 - 25 127 14 [ 1 - 409639] GPT

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

*3: 07 1023 254 63 - 1023 254 63 [-1429741568 - 351989760] NTFS

4: AF 1023 254 63 - 1023 254 63 [-1077751808 - 689813640] HFS+

sh-3.2#

P.S i spoke to wineclone support they told me apple dont support my setup ( dvd drive missing ) and they cant support what i have done they requested that i re install the DVD drive.

Dec 11, 2012 2:29 PM in response to Christopher Murphy

Hello Christopher,

sorry for bothering but i have another question.
I made everything like you wrote in steps 1 and 2 and got my Windows disappeared from boot menu.

So i had no chance to get to the step 3.

Here is what i have now

==============================================================================

sh-3.2# gpt -r -vv show disk0

gpt show: disk0: mediasize=256060514304; sectorsize=512; blocks=500118192

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 500118191

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 382258864 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

382668504 296

382668800 117448704 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

500117504 655

500118159 32 Sec GPT table

500118191 1 Sec GPT header

==============================================================================

sh-3.2# fdisk /dev/disk0

Disk: /dev/disk0 geometry: 31130/255/63 [500118192 sectors]

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 - 382258864] HFS+

*3: 07 1023 254 63 - 1023 254 63 [ 382668800 - 117448704] HPFS/QNX/AUX

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

==============================================================================

sh-3.2# gpt -r -vv show disk1

gpt show: disk1: mediasize=240057409536; sectorsize=512; blocks=468862128

gpt show: disk1: Suspicious MBR at sector 0

gpt show: disk1: Pri GPT at sector 1

gpt show: disk1: Sec GPT at sector 468862127

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 467182912 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

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

468862088 7

468862095 32 Sec GPT table

468862127 1 Sec GPT header

==============================================================================

sh-3.2# fdisk /dev/disk1

Disk: /dev/disk1 geometry: 29185/255/63 [468862128 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 - 467182912] HFS+

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

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

==============================================================================

sh-3.2# dd if=/dev/disk0 count=1 2>/dev/null | hexdump -C

00000000 fa 31 c0 8e d8 8e c0 8e d0 bc 00 7c fb fc 89 e6 |.1.........|....|

00000010 bf 00 06 b9 00 01 f3 a5 ea 1d 06 00 00 88 16 00 |................|

00000020 08 b4 08 cd 13 31 c0 88 f0 40 a3 f0 06 80 e1 3f |.....1...@.....?|

00000030 88 0e f2 06 be be 07 31 c0 b9 04 00 f6 04 80 74 |.......1.......t|

00000040 03 40 89 f7 83 c6 10 e2 f3 83 f8 01 75 73 8a 16 |.@..........us..|

00000050 00 08 b8 00 41 bb aa 55 31 c9 30 f6 f9 cd 13 72 |....A..U1.0....r|

00000060 23 81 fb 55 aa 75 1d f6 c1 01 74 18 57 be e0 06 |#..U.u....t.W...|

00000070 8b 5d 08 89 5c 08 8b 5d 0a 89 5c 0a 8a 16 00 08 |.]..\..]..\.....|

00000080 b4 42 eb 2a 57 8b 45 08 8b 55 0a f7 36 f2 06 42 |.B.*W.E..U..6..B|

00000090 89 d1 31 d2 f7 36 f0 06 88 c5 d1 e8 d1 e8 24 c0 |..1..6........$.|

000000a0 08 c1 88 d6 8a 16 00 08 bb 00 7c b8 01 02 cd 13 |..........|.....|

000000b0 72 16 5e 81 3e fe 7d 55 aa 75 08 fa ea 00 7c 00 |r.^.>.}U.u....|.|

000000c0 00 77 05 be f4 06 eb 03 be 0f 07 ac 20 c0 74 0c |.w.......... .t.|

000000d0 b4 0e 8a 3e 62 04 b3 07 cd 10 eb ef eb fe 00 00 |...>b...........|

000000e0 10 00 01 00 00 7c 00 00 00 00 00 00 00 00 00 00 |.....|..........|

000000f0 00 00 00 00 4d 69 73 73 69 6e 67 20 6f 70 65 72 |....Missing oper|

00000100 61 74 69 6e 67 20 73 79 73 74 65 6d 0d 0a 00 4f |ating system...O|

00000110 70 65 72 61 74 69 6e 67 20 73 79 73 74 65 6d 20 |perating system |

00000120 6c 6f 61 64 69 6e 67 20 65 72 72 6f 72 0d 0a 00 |loading error...|

00000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

000001c0 02 00 ee 7f 0e 19 01 00 00 00 27 40 06 00 80 7f |..........'@....|

000001d0 0f 19 af fe ff ff 28 40 06 00 b0 ce c8 16 80 fe |......(@........|

000001e0 ff ff 07 fe ff ff 00 10 cf 16 00 20 00 07 00 00 |........... ....|

000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|

00000200

==============================================================================

sh-3.2# dd if=/dev/disk1 count=1 2>/dev/null | hexdump -C

00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe |................|

000001c0 ff ff ee fe ff ff 01 00 00 00 27 40 06 00 80 fe |..........'@....|

000001d0 ff ff af fe ff ff 28 40 06 00 40 a5 d8 1b 00 fe |......(@..@.....|

000001e0 ff ff ab fe ff ff 68 e5 de 1b 20 5f 13 00 00 00 |......h... _....|

000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|

00000200

==============================================================================

Please help me and Dec 21 i will save your life ;-)
Thank you.

Alex

Dec 11, 2012 2:34 PM in response to Coffeecoco

OK so you've already written out the change, you should reboot and hold down option and see if you get a Windows icon, and then what happens if you choose it.

Dec 11, 2012 2:40 PM in response to Christopher Murphy

I appologise if you wanted me todo something before hand

Windows Icon has always been there

i tried it did the same thing black screen

but parallels can boot the same partition perfectly

Dec 11, 2012 2:38 PM in response to Alex Senkevich

@Alex

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

*3: 07 1023 254 63 - 1023 254 63 [ 382668800 - 117448704] HPFS/QNX/AUX

This is wrong you set both partitions to be bootable (asterisk means active flag is set). So go back to gdisk, recovery menu, add paritions 2 3, make sure 2 is NOT bootable and 3 is.

Dec 11, 2012 2:56 PM in response to Alex Senkevich

@Alex

Another issue is that your boot loader doesn't appear to be a Windows boot loader. Yours starts with this line:

00000000 fa 31 c0 8e d8 8e c0 8e d0 bc 00 7c fb fc 89 e6 |.1.........|....|

And a Windows boot loader should be this line:

00000000 33 c0 8e d0 bc 00 7c 8e c0 8e d8 be 00 7c bf 00 |3.....|......|..|

So invariably it seems you will need to boot from a Windows installer, and use startup repair. If that doesn't work you get to go down the bootrec rabbit hole from command prompt.

Dec 11, 2012 2:57 PM in response to Christopher Murphy

Yuppie!
you made it! Don't think i'm kid! I'm 30 but i'm just happy!
i got win menu and entered it.

then i got screen:

i i'm starting to think what can i do. Because i don't have CDROM because my 2nd SSD is placed insted of it.
And i can't boot from USB stick with Windows 7 install. Because Apple doesn't allow to boot Macbook Pro in this way.

Dec 11, 2012 3:02 PM in response to Coffeecoco

WAIT Windows Boots now!!! I think i had a sneaky usb cable pluged into a device that was screwing it up

anyway i get bluescreens now so thats another story i assume

Dec 11, 2012 3:05 PM in response to Alex Senkevich

@Alex

There's a way to do this with a VM, so that you boot the VM with a Windows 7 ISO, while the disk is a real whole disk (the one you're trying to fix) instead of a VM, and run bootrec or startup repair from there.

Dec 11, 2012 3:07 PM in response to Coffeecoco

@Coffeecoco

Same situation as Alex. You'll need to use a VM to boot a Windows 7 installer ISO, while also having the real full disk available to that VM, and run Windows startup repair. I don't know how to do this in any VM except VBOX.

Dec 11, 2012 3:09 PM in response to Christopher Murphy

Thank you Christopher!
That's what i'm doing now from Parallels. Trying to mount iso and use it as a CD.
Thank you very much again! How can i add points to your level? Where i need to vote?

Also feel free to contact me if you need any help with php web development especially with Drupal.

Repairing Boot Camp after creating new partition