Repairing Boot Camp after creating new partition

Dear all,

I am having a similar problem. Tried to resize the hard drive with Paragon Camptune X and well, technically it worked but now I can not boot with Boot Camp anymore. I have seen the cited answer to be working, is this a solution I can use as well? Thanks for your assistance.

Manuel

It may be a bit better to start a new thread. You can also post the output of the following commands in the new thread and post a reference here.

diskutil list

sudo fdisk /dev/<DiskNameOfYourBootcamp>

sudo gpt -vv -r show /dev/<DiskNameOfYourBootcamp>

Opened a new thread here:

Repairing Boot Camp Partition

Regarding the commands 'sudo' - I can not execute them since I am not aware of the disk name.

Manuel

Just wanted to say a big THANK YOU to Christopher Murphy and Loner T for all the help they have provided on this BootCamp issue.

BTW, is there any "official" statement/solution from Apple on this problem?

The 'official' stance is documented in the Bootcamp FAQ. Resizing/moving is not supported. The Late 2013 Macs seem to support EFI much better than in the past, despite some driver and hardware support issues. The 'long-term' direction is probably full EFI compliance.

Hi I get a similar problem after canning the partition map (and then removing the extra disk I created)

I now have 4 partitions. Windows disk is good I can open it using finder and all data is there but it won't boot up using bootcamp.

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 277.7 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 130.0 GB disk0s4 <===== I can see the data from mac osx is still there and ok.

When I try and re-boot to bootcamp it gives me the "No bootable device --- insert boot disk and press any key" message

using

sudo gpt -r -vv show disk0

Password:

gpt show: disk0: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: disk0: Suspicious MBR at sector 0 <===== This looks weird

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 976773167

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

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

543965712 178902512

722868224 253904896 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

976773120 15

976773135 32 Sec GPT table

976773167 1 Sec GPT header

I tried using gdisk and creating a hybrid MBR and marked them as bootable.

I get this message when running GDISK

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

MBR: hybrid

BSD: not present

APM: not present

GPT: present

Found valid GPT with hybrid MBR; using GPT.

using p i get

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

1 40 409639 200.0 MiB EF00 EFI system partition

2 409640 542696175 258.6 GiB AF00 Customer

3 542696176 543965711 619.9 MiB AB00 Recovery HD

4 722868224 976773119 121.1 GiB 0700 BOOTCAMP

Help ?? what Do i need to do to get it to boot into windows.

I suggest starting a new thread of your own, please post what you posted above but also include

sudo fdisk /dev/disk0

And then post the URL in this thread for notification of the new thread. That the Finder sees your Windows files is a very good thing. I'm confused why there's 87GB of free space reported by the GPT, that's not available to either OS X or Windows. So hopefully the MBR info from fdisk will shed some light. If the MBR and GPT are the same, then you'll need to use Windows Startup Repair or bootrec.exe to fix the boot problem; and then later you'll want to obliterate Windows and reinstall it, to recapture all that free space. And if the MBR and GPT aren't matching then you'll need to figure out which one is correct first - the correct one is the one that OS X is mounting with your files intact, so the command df -h will show the size of the volume and from that we can deduce whether the MBR or GPT entry is being honored, and then how to fix the discrepancy. Might take a couple days... so be patient.

Cannot reboot Bootcamp after partition mod 10.9.4

created thread with all the information thanks.

The free space is due to me attempting to re-size the mac osx partition in order to increase the windows partition size. I can re-size it back if necessary but i didn't want to mess with it any further and make things worse.

in response to Christopher Murphy

i canno boot to win7

new thread is Cannot boot to windows 7 after canceling bootcamp backup

can you help me? thank you

Hi,

I have the same problem after installing Yosemite, the Bootcamp is still visible when in Startup Disk, but i cannot boot into Windows, when i hold the OPTION key at startup, only 10.9 and 10.10 shows up 😠 When i forced to boot from Startup Disk I received an error message that there is no bootable device.

I tried this trick which seemed to help some people here.

(sudo fdisk -e /dev/disk0

setpid 4

07

flag 4

write)

But no luck for me. It actually enabled the option to boot when holding the OPTION key at startup, but it gets stuck and will not load anything, nor does it show any error message.

Please help me nice people here 😢 I spent Several hours with no luck.

Thanks Loads

sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=251000193024; sectorsize=512; blocks=490234752

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

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

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

gpt show: /dev/disk0: Sec GPT at sector 490234751

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

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

117652072 19752568 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

137404640 1269536 5 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

138674176 351559680 6 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

490233856 863

490234719 32 Sec GPT table

490234751 1 Sec GPT header

sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 490234751] <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: 07 0 0 0 - 0 0 0 [ 0 - 0] HPFS/QNX/AUX

diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *251.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 59.4 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Apple_HFS Yosemite 10.1 GB disk0s4

5: Apple_Boot Recovery HD 650.0 MB disk0s5

6: Microsoft Basic Data BOOTCAMP 180.0 GB disk0s6

sudo fdisk /dev/disk0s6

fdisk: /dev/disk0s6: Resource busy

sudo gpt -vv -r show /dev/disk0s6

gpt show: unable to open device '/dev/disk0s6': Resource busy

1. Installing Soon-tobe-released Os is not supported.

2. You have 6 GPT entries, bootcamp disk uses a mbr, which can support only 4.

3. Fdisk and gpt work on whole disks, not disk slices.

4. I would recommand...

a. Remove the new Os.

b. Start a new thread and post a reference here.

c. Please post the the output of sudo dd if=/dev/disk0s6 count=1 2>/dev/null | hexdump -C

d. The disk0s6 will change if you do this after you remove the new Os.

Hi

Here is my none working dual boot HD 😟

sudo gpt -r -vv show disk0

gpt show: disk0: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 976773167

start size index contents

0 1 MBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - ID1

409640 819253632 2 GPT part - ID2

819663272 1533528 3 GPT part - ID3

821196800 155576320 4 GPT part - ID4

976773120 15

976773135 32 Sec GPT table

976773167 1 Sec GPT header

sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 60801/255/63 [976773168 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 - 819253632] HFS+

3: AB 1023 254 63 - 1023 254 63 [ 819663272 - 1533528] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [ 821196800 - 155576320] HPFS/QNX/AUX

admin$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Power 419.5 GB disk0s2

3: Apple_Boot Recovery HD 785.2 MB disk0s3

4: Microsoft Basic Data WINDOWS 79.7 GB disk0s4

after an unsuccessful try

Disk: /dev/disk0 geometry: 60801/255/63 [976773168 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 0 0 2 - 1023 254 63 [ 1 - 821196799] <Unknown ID>

*2: 07 1023 254 63 - 1023 254 63 [ 821196800 - 155576320] HPFS/QNX/AUX

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

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

can someone help to make my dual boot works?

thanks 🙂

1. It may be a bit cleaner to start new thread and post your information there and a reference back here.

2. What was the issue with Windows before the retry? And after the retry?

3. Curious on why your GPT has no partition type GUIDs ?

4. Can you post the output of the dd command to verify your NTFS partition ?

5. It may be helpful to know what caused the problem?

Thanks for your prompt response.🙂

Hmmm.. So I'd rather choose waiting few days to finish testing the new OS; my main concern is if the Windows partition is damaged completely and forever; If it remains intact and there's a solution to recover it, i'd then rather use my Dell laptop for the windows work until I'm about to delete Yosemite. SO CAN YOU PLEASE CONFIRM that the Windows part is not damaged?...

Anyway, I'm wondering about why there is more than 3 disks?! I only have 3 partitions, 1) Mavericks 2) BootCamp 3) Yosemite , is it because of the recovery disks!?! So maybe just delete the 10.10 recovery disk.

Another question, how come I can actually boot to the windows side (after using your trick..) it just gets stuck at the loading screen. =..

Thanks again for your outstanding willingness to help me and many others here. 😁