Repairing Boot Camp after resizing existing partitions and creating new partition

Question

Level 1

0 points

Repairing Boot Camp after resizing existing partitions and creating new partition

Hi,

I installed Windows on my MBPr yesterday and had it working fine. Unfortunately, I made the mistake of messing with the partitions. I originally had the Macintosh HD one and the Bootcamp one but created another, later deleted that one, and have resized my Macintosh HD one a couple of times. I cannot get my Macintosh HD partition to expand completely--I can't use all of my free space.

When I hold the "option" key while booting, I can only boot to Macintosh HD or Recovery. If I use Startup Disk, I can choose to restart and boot to Bootcamp (Windows). When I do this though, I get a black screen that says "No bootable device - insert boot disk."

I have done my research, have realized my mistake, and have gdisk installed.

Any help would be really appreciated.

MacBook Pro (Retina, 13-inch, Late 2013), OS X Mavericks (10.9)

Posted on Nov 1, 2013 11:03 AM

Reply

Answer 1

Nov 1, 2013 2:22 PM in response to wertjake

A lot has been written on how to solve this problem so if you can't figure out how to do that then it's definitely easier to just start over.

Reply

Answer 2

Nov 1, 2013 2:25 PM in response to wertjake

There are a number of related yet shorter threads on Mac Rumors that might be useful.

Reply

Answer 3

wertjake Author

Level 1

0 points

Nov 1, 2013 3:49 PM in response to Christopher Murphy

I'm not sure that I can truly "start over." But I'm starting to consider it.

I made an interesting observation though as I was reading some of your posts about this sort of problem. I'm using interactive gdisk, the recovery/transformation set of menus, and I printed my protective MBR data.

Number Boot Start Sector End Sector Status Code

1 1 409639 primary 0xEE

2 409640 693905727 primary 0xAF

3 693905728 695175263 primary 0xAB

4 742731776 977104895 primary 0x0C

That last partition is the Boot Camp (Windows) one. Shouldn't its code be 0x07?

Is there a way to correct that? Correct me if I am wrong, but what I have taken away from the reading I have done is that it that since it is 0x0C, it is likely that it is being mistaken as a FAT. It really is NTSF because it is Windows and this (and the fact that it isn't flagged) may be causing my problems.

The reason I am adamant about not starting over and carefully correcting this issue is that my MBPr has no CD/DVD drive and I have all of my software I need on DVDs. It was a long process getting it installed. If that is my only option though I will have to do it again. If there is anyway you can help me or send me in the right direction, I would be very grateful.

Reply

Answer 4

wertjake Author

Level 1

0 points

Nov 1, 2013 7:42 PM in response to wertjake

RESOLVED

Open terminal and enter the following:

sudo fdisk -e /dev/disk0

(there will be an error saying, "fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory

Enter 'help' for information." Ignore this and proceed.)

p

(you should see something that looks like this:

Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]

Offset: 0 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 - 693496088] HFS+

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

4: 0C 1023 254 63 - 1023 254 63 [ 742731776 - 234373120] Win95 FAT32

)

edit 4

07

n

(this number will be different for you, look where I got it from) 742731776

(this number will be different for you, look where I got it from) 234373120

flag 4

p (to check if the solution worked; there should be an asterik [*] in front of the 4, and Win95 FAT32 should now say HPFS/QNX/AUX)

quit

y

Reply