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.

Repairing Boot Camp after creating new partition

elyoe011 Nov 24, 2014 5:10 AM Re: Repairing Boot Camp after creating new partition

Re: Repairing Boot Camp after creating new partition in response to Loner T

Loner T,


I did this fix:


sudo fdisk -e /dev/disk0

p

setpid 4

07

flag 4

p

write

y


When I started Windows all I had was a black screen with a blinking underscore "_"


I went back to my MAC and try it again... but instead of "setpid 4" and "flag 4" I did "setpid 1" and "flag 1"


Now when I boot into Windows/BootCamp is saying "Missing Operating System" and OS X is not bootable.


Also Macintosh HD is gone from Disk Utility when I go into recovery mode and check Disk Utility...


I there any REMEDY for this? I have a lot of data that I need to recover...


ANY help is really appreciated!!!!!!!!

Mac Pro, OS X Yosemite (10.10.1)

Posted on Nov 24, 2014 6:21 AM

Reply
48 replies

Nov 30, 2014 5:33 PM in response to Loner T

I'm not sure why disk0 became a FDisk_Partition_scheme. When I installed GPT Fdisk and it asked me where did I wanted to installed it I choose the SD card, that's it!


My mac is extremely slow I guess is because I booted of the SD Card....


Here is the output of all commands:


sudo gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=750156374016; sectorsize=512; blocks=1465149168

gpt show: /dev/disk0: MBR at sector 0

gpt show: /dev/disk0: Malformed 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



sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 91201/255/63 [1465149168 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: AF 0 0 2 - 1023 254 63 [ 1 - 1269258239] HFS+

*2: 07 1023 254 63 - 1023 254 63 [1269258240 - 195889152] HPFS/QNX/AUX

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

4: 07 0 0 0 - 0 0 0 [ 0 - 0] HPFS/QNX/AUX



sudo gdisk /dev/disk0

GPT fdisk (gdisk) version 0.8.10


Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

MBR: MBR only

BSD: not present

APM: not present

GPT: present


Found valid MBR and GPT. Which do you want to use?

1 - MBR

2 - GPT

3 - Create blank GPT


Your answer:

Nov 30, 2014 5:47 PM in response to Loner T

Here:


Found valid MBR and GPT. Which do you want to use?

1 - MBR

2 - GPT

3 - Create blank GPT


Your answer: 2

Using GPT and creating fresh protective MBR.


Command (? for help): p

Disk /dev/disk0: 1465149168 sectors, 698.6 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): 28422E5D-FA63-422B-82C9-39BED40FCD23

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 1465149134

Partitions will be aligned on 8-sector boundaries

Total free space is 193362069 sectors (92.2 GiB)


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

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 1074628383 512.2 GiB AF00 Customer

3 1074628384 1075897919 619.9 MiB AB00 Recovery HD

4 1269258240 1465147391 93.4 GiB 0700 BOOTCAMP


Command (? for help):

Nov 30, 2014 6:20 PM in response to Loner T

Done:


Command (? for help): w


Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING

PARTITIONS!!


Do you want to proceed? (Y/N): y

OK; writing new GUID partition table (GPT) to /dev/disk0.

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Warning: The kernel may continue to use old or deleted partitions.

You should reboot or remove the drive.

The operation has completed successfully.


Do I need to reboot or what's next...?

Nov 30, 2014 7:14 PM in response to elyoe011

The only supported method is to backup your files from current bootcamp, use BCA to remove Windows, and reinstall Windows with a new size and then restore you data files.


There is a commercial tool called Winclone which will let you create a backup. Once you have a backup, use BCA to remove the current Bootcamp, and restore the Winclone image to a larger partition.

Repairing Boot Camp after creating new partition

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.