Q: Repairing Boot Camp after creating new partition

Thanks fmnamado for the reply.

I want to use this solution only if there are no possibilities to repair at my issue.

I've see that it is possible to do by terminal, type various things that I've no idea what it's meaning and I hope someone can do this do this for me. XD

Just figured I would add that the current version of CampTuneX will also fix this situation (which I just got myself into).

You sir are a genius!

Had the exact same issue, followed your instructions religiously and windows came back.

Brilliant!

Thank you for this..

My problem might be a different one, but the symptoms look quite similar, and maybe someone of the experts could help me:

I exchanged a hard drive containing a single boot camp partition with Windows 7. Before removing the old drive I used the usual disk utility application to copy the partition to an external (FW) hard drive. Later I created a bootcamp partition of about the same size on the new drive (a little bit larger, because Bootcamp Assistent did not allow to set the exact size) and restored the partition from external drive to the new one.

But the new bootcamp partition was not bootable.

I tried the gdisk utility like explained in this thread (the hybrid MBR thing), but it did not help.

I reinstalled Windows 7 from scratch, this worked so far. Afterwards I again used Disk Utility to restore the bootcamp partition from the external hard drive, hoping that the "bootability" will remain. But it did not.

So the result also was that the partition is not shown in the start manager (when I press ALT during boot). After re-applying the gdisk procedure the bootcamp partition is shown during startup, but when I try to start Windows, I get a black screen with text: "disk read error occurred, press ..."

So somewhat Disk Utility has destroyed the freshly installed Windows. But I cannot understand why. Am I something missing, i.e. is gdisk not powerful enough to make the partition bootable, and why and how has Disk Utility destroyed it? Unfortunately my children and me are playing a computer adventure game which we did not finish yet, and a new installation would destroy all our user settings etc.. :-(

BTW: The disk containing bootcamp is disk2, but yesterday it was disk1. Strange...

Please start a new discussion and do not modify the original drive in any way. Using OS X Disk Utilities to clone/move Windows does not work very well and fails in most cases.

This is the new discussion: Trying to repair copied bootcamp partition

Hi,

Similarly to many of you here, I've had problem after stupidly creating a new partition in OS X, rendering bootcamp unbootable. Following indications, I created a new threads with the following infos :

1. diskutil list

2. diskutil cs list

3. sudo gpt -vv -r show /dev/disk0 (if bootcamp is on disk0, or choose the appropriate disk, as shown in diskutil list).

4. sudo fdisk /dev/disk0 (if bootcamp is on disk0, or choose the appropriate disk, as shown in diskutil list).

5. sudo dd if=/dev/rdisk0 count=1 2>/dev/null | hexdump -C  (if bootcamp is on disk0, or choose the appropriate disk, as shown in diskutil list).

Please help me in : Repairing Bootcamp after creating a new partition

Thank you very much.

Wow seems like a common problem ! First thanks for every one's support my problem is along those same lines I am still going through the 100 page posts ! But figured to mention my problem maybe it has been solved before.

What i did was reduce OS X partition size, restart in bootcamp windows 7 and used Mini Tool Partition to acquire the free space. Restarted windows worked great for a couple of days until i restarted in OS X which as most threads here have boot camp is called disk04 and can not be mounted nor can it been seen in startup disk.

All i want is to get the windows working as i have no backup (i know!) and to sort out the missing space.

I will continue to go through the post but any pointers will be appreciated !

As per original post, here is the results:

Vmini:~ Vulkyn$ sudo gpt -r -vv show disk0

WARNING: Improper use of the sudo command could lead to data loss

or the deletion of important system files. Please double-check your

typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:

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 - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

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

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

  587616672   93750880       

  681367552  295405568      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  976773120         15       

  976773135         32         Sec GPT table

  976773167          1         Sec GPT header

Vmini:~ Vulkyn$ 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 -  585937496] HFS+      

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

4: 0C 1023 254  63 - 1023 254  63 [ 681367552 -  295405568] Win95 FAT32L

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

I created a new thread as well as it seems to be very cluttered here >.<

Lost bootcamp after using mini tool partition to increase windows partition size

Hi All,

I have a problem with bootability of my Windows partition. In short: after updating the Bootcamp drivers via the Bootcamp application in OS X, the partition table on my Mac went completely berserk so I could not boot back to OS X again. I made a number of more or less random attempts to restore OS X and finally got the OS X resurrected. But I cannot boot to Windows anymore. I have a feeling that the partition table settings are incorrect, but I cannot find the right configuration to make it work back again.

Additional information:

- OS X still sees my Bootcamp partition; all files and folders are there, seem intact

- the SSD of my MBP seems perfectly fine, so I am ruling out a hardware fault

- when I start my Mac, the Windows partition is visible on the list of bootable drives

- when I boot to Windows, I see the light blue Windows logo and the circling dots, but nothing happens afterwards

- when I enter the Windows recovery mode and type "dir" in the DOS command line, it shows the contents of the EFI partition i.e. it considers the EFI partition to be the C: drive, which indicates to me that Windows is trying to boot from the EFI partition, rather than from the Bootcamp parition

- before the whole partition problem, I did not see the EFI partition in my disks list in OS X. Now I can. I have a feeling that during my hectic attempts to restore the bootability of OS X I somehow made the EFI partition active, so it "jumped into the place" of Windows/Bootcamp

Here is the output of the diskutil list

Przemeks-MacBook-Pro:~ Przemek$ diskutil list

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.3 GB   disk0

   1:       Microsoft Basic Data EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS Macintosh HD            371.2 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

   4:       Microsoft Basic Data Bootcamp                128.2 GB   disk0s4

Here is the output of the sudo gpt -r -vv show disk0

gpt show: disk0: mediasize=500277790720; sectorsize=512; blocks=977105060

gpt show: disk0: MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 977105059

      start       size  index  contents

          0          1         MBR

          1          1         Pri GPT header

          2         32         Pri GPT table

         34          6        

         40     409600      1  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

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

  725408424       1368        

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

  726679328        224        

  726679552  250425344      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  977104896        131        

  977105027         32         Sec GPT table

  977105059          1         Sec GPT header

Here is the output of the sudo fdisk /dev/disk0

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

Signature: 0xAA55

         Starting       Ending

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

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

1: AF   25 127  15 - 1023 254  63 [    409640 -  724998784] HFS+       

*2: 07 1023 254  63 - 1023 254  63 [ 726679552 -  250425344] HPFS/QNX/AUX

3: EE    0   0   2 -   25 127  14 [         1 -     409639] <Unknown ID>

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

I hope Christopher Murphy still visits this thread every now and then .

Additional info from rEFIt Partition Inspector:

*** Report for internal hard disk ***

Current GPT partition table:

#      Start LBA      End LBA  Type

1             40       409639  Basic Data

2         409640    725408423  Mac OS X HFS+

3      725409792    726679327  Mac OS X Boot

4      726679552    977104895  Basic Data

Current MBR partition table:

# A    Start LBA      End LBA  Type

1         409640    725408423  af  Mac OS X HFS+

2 *    726679552    977104895  07  NTFS/HPFS

3              1       409639  ee  EFI Protective

MBR contents:

Boot Code: Unknown, but bootable

Partition at LBA 40:

Boot Code: None (Non-system disk message)

File System: FAT32

Listed in GPT as partition 1, type Basic Data

Partition at LBA 409640:

Boot Code: None

File System: HFS Extended (HFS+)

Listed in GPT as partition 2, type Mac OS X HFS+

Listed in MBR as partition 1, type af  Mac OS X HFS+

Partition at LBA 725409792:

Boot Code: None

File System: HFS Extended (HFS+)

Listed in GPT as partition 3, type Mac OS X Boot

Partition at LBA 726679552:

Boot Code: Windows BOOTMGR (Vista)

File System: NTFS

Listed in GPT as partition 4, type Basic Data

Listed in MBR as partition 2, type 07  NTFS/HPFS, active

You sir are my hero !!!

Thanks a lot for you help AND your explanations !

Seb, a french guy

Hi Christopher,

I tried creating new MBR using gdisk and it screwed up bootcamp. When I try to start mac by pressing option key it only showed Macintosh HD. Than I followed your instructions and got the bootcamp windows drive option back in the startup disk options. Now the windows is complaining that some drives are inaccessible and its failing to start. Could you please suggest some solution on this.

FYI

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

   1              40          409639   200.0 MiB   EF00  EFI System Partition

   2          409640       243413599   115.9 GiB   AF05  Macintosh HD

   3       243413600       244683135   619.9 MiB   AB00  Recovery HD

   4       244684800       977104895   349.2 GiB   0700  BOOTCAMP

When I choose windows and boot in its asking to insert windows installation/recovery CD and press enter. I tried inserting USB 3.0/ Super drive with windows 7 CD with No Luck.

I followed

r <enter>        go to the recovery & transformation menu

h <enter>        create a new hybrid MBR

4 <enter>        add partion 4 to the MBR

<enter>          accept the default MBR hex code of 07

y <enter>        set the bootable flag

n <enter>        do not protect more partitions

o < enter>       print (display) the MBR

Thanks,

Al

Please start a new discussion and describe the problem. Was there a specific reason to try and recreate the MBR?

I've posted a new thread here Bootcamp gone after partitioning.  Seems I have similar issues with the Bootcamp partition disappearing but I've yet to find a solution.  Data recovery is my hopeful goal. 

Thank you

Anyone familiar with this readout following the sudo gpt -vv -r show /dev/disk0 command?  Doesn't look good.

dons-mbp:~ donharward$ 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: Pri GPT at sector 1

gpt show: error: bogus map

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

dons-mbp:~ donharward$

Bootcamp gone after partitioning