Repairing Boot Camp after creating new partition

WarthogARJ wrote:

I need to have TWO Terminal sessons going for this...excellent.

Awesome.

The second terminal window was suggested if syntax or sub-commands for fdisk command were needed. It is really not necessary.

Can someone please help me with recovering my system? I can't see the windows boot at the launch screen, here's my relevant info. I'm not a big command line geek so if you could tell me exactly what to type in to fix this...

anomaly:~ ape$ sudo gpt -r -vv show disk0

gpt show: disk0: mediasize=1000555581440; sectorsize=512; blocks=1954210120

gpt show: disk0: PMBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 1954210119

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

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

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

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

1753632328 440

1753632768 200577024 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1954209792 295

1954210087 32 Sec GPT table

1954210119 1 Sec GPT header

anomaly:~ ape$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 121643/255/63 [1954210120 sectors]

Signature: 0xAA55

Starting Ending

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

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

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

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

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

May I suggest

1. If you are inclined to follow steps at this link, you can try these... https://discussions.apple.com/thread/5679023?answerId=24172151022#24172151022

I would suggest running the following two non-destructive commands to ensure there is a backup of the current disk information available either in this thread or somewhere where you have access to it (if there are issues later).

or

2. Create a new thread, put a reference here, and post the output that you currently have in that thread

Hi Loner T,

I read the threads you suggested as well as the link about hybrid MBR:

http://www.rodsbooks.com/gdisk/hybrid.html

Can I confirm the steps please? (and I'll be really anal-retentive about it: I've already made a mistake with fdisk once!)

And I think this would be a useful procedure to have since it seems lots of people have this issue.

(1) Backup everything (I use TimeMachine and CCC as well as WinClone)

(2) Download gpt if required

http://sourceforge.net/projects/gptfdisk/

(3) Start Mac Terminal

(4) Run these two commands to check my partitions:

And post results somewhere safe so I can be helped if problems (that's a clever idea):

sudu fdisk /dev/disk0

sudo gpt -r -vv show disk0

Alans-MacBook-Pro:~ arjarvis_mbp$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 116737/255/63 [1875385008 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 31 20 [ 409640 - 1698931968] HFS+

3: AB 1023 31 21 - 1023 118 44 [1699341608 - 1531680] Darwin Boot

*4: BF 1023 133 52 - 1023 70 5 [1700874240 - 174510080] <Unknown ID>

Alans-MacBook-Pro:~ arjarvis_mbp$ sudo gpt -r -vv show disk0

gpt show: disk0: mediasize=960197124096; sectorsize=512; blocks=1875385008

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 1875385007

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

1699341608 1531680 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

1700873288 952

1700874240 174510080 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1875384320 655

1875384975 32 Sec GPT table

1875385007 1 Sec GPT header

(5) Based on this info, my 4th Partition (BootCamp) has the id "BF".

It SHOULD be "07" in order for BootCamp to bootup on startup.

So I need to run a series of fdisk commands to change that.

(6) sudo fdisk -e /dev/rdisk0

(which seems to return an error: I'm not sure why we are running it if it gives an error??)

Alans-MacBook-Pro:~ arjarvis_mbp$ sudo fdisk -e /dev/rdisk0

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

Enter 'help' for information

fdisk: 1>

So is there a better command to run here?

Is this just a way to get fdisk to start running?

After this I'm a little bit confused.

The thread you sent me has two DIFFERENT sequences of Terminal commands:

https://discussions.apple.com/thread/4144252?answerId=23681966022#23681966022

Can you please confirm that these are correct?

(7) From the last part of this post:

setpid 4

07

write

Y

flag 4

write

Y

print

quit

(8) Or from the more dertailed instructions to RamosWipout earlier in that post:

help

print

setpid 4?

07

flag 4

write

I think (7) looks better. Correct?

Then I think you tell your system to restart.

(9) then you type in the following to check that it all worked:

sudo fdisk /dev/rdisk0

(10) And obviously check that your system DOES bootup into BootCamp at startup.

So can you please confirm these steps?

Especially if we should be using (7) or (8).

The other less competent users like myself really appreciate the help of you guys in this!

Alan Jarvis

You can use Step 7. In step 6, the "-e" puts fdisk in prompt mode. The "1>" indicates that fdisk is working on partition 1 (by default). stepid command should change it "4>" or "*4>".

Christopher,

Thank you very much. You have saved my data! Testdisk worked like a charm and provided me on the past to recovery and being able to boot into my Windows Bootcamp partition. I truly appreciate everything you have done for us all.

God Bless You,

Laurence

Is that Christopher guy still around here helping people? I just got my macbook pro and have spent the last 4 days configured bootcamp to the way I wanted Windows, I went and tried to extend the bootcamp partition with a windows tool like an idiot.

If anyone around here can walk me through repairing the MBR via terminal I will seriously paypal you some money.

I'm not bad with windows command line but I am a total noob to OSX. Please Help!

Do you want to post a new thread with a reference here and the output of the following commands in the new thread?

The assumption is that your OSX and Bootcamp are on the same disk (/dev/disk0). Please use OS X Terminal (found in Applications -> Utilities)

diskutil list

sudo gpt -r -vv show disk0

sudo fdisk /dev/disk0

For the GPT command, please try

sudo gpt -r -vv show /dev/disk0

Ok, this is precisely the output I got:

gpt show: /dev/disk0: mediasize=320072933376; sectorsize=512; blocks=625142448
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: error: bogus map
gpt show: unable to open device '/dev/disk0': Undefined error: 0

It is strange to see such an error which makes me suspicious of the GPT. Please try

sudo gpt -r -vv show /dev/rdisk0

It's more or less returning the same result:

gpt show: /dev/rdisk0: mediasize=320072933376; sectorsize=512; blocks=625142448

gpt show: /dev/rdisk0: Suspicious MBR at sector 0

gpt show: /dev/rdisk0: Pri GPT at sector 1

gpt show: error: bogus map

gpt show: unable to open device '/dev/rdisk0': Undefined error: 0

I can install team viewer if you wanna remote in and run some commands to see the status of the MBR and parttion table. I don't mind. Just want this fixed. Seriously dreading the thought of having to wipe the hdd and start over.

There is another utility called gdisk (http://sourceforge.net/projects/gptfdisk/?source=dlp) which may be worth looking at, otherwise testdisk is one of last resort.