Q: Repairing Boot Camp after creating new partition

and also please explain this to me as well... why is the information i highlighted not Win95 FAT32L, just like the others.

I need your help. :/

Arvind,

There is a set of steps that Franky/Tom have outlined with testdisk (if you go back a couple of pages). Christopher is asking you to execute those and look for your files to validate that you have the correct partition start and end.

a.) I can't answer your question because by assuming your problem is caused by the same thing the last few people have had, you started changing things with your partition map that will hide what the true problem is. Based on the fdisk and gpt output you posted, your system should boot Windows. If it doesn't, you have other problems and you should post a new thread briefly describing steps you've taken leading up to the current state of the drive (don't list the reasons why you did it, just list each thing you did do).

b.) Code 07 is interpreted by Apple's old old old version of fdisk as HPFS/QNX/AUX, but it's the code most commonly used for NTFS. 07 is the correct code so just leave that alone.

c.) Please don't whine for more help 30 minutes after asking for free help. It's irritating. Try to have some imagination that maybe people have other things to do, including SLEEPING at 3:30am when you were posting these demands for help. You can legitimately bump a thread after 2 days if someone hasn't responded, but 30 minutes is flat out rude. If you're in that big of a hurry you should have backups you can restore from sooner.

im sorry. i didnt mean to. im from a different country and i didnt know the time difference. :/ sorry i wont bother you again. and and thanks for your help. i really appreciate it.!

Did you get it working or not?

Christopher, following you on other threads, you seem to be extremely knowledgable in this area.  I have updated to 10.9 Mavericks and the process has rendered my previously working bootcamp config with Windows not bootable.  I believe during the RecoveryHD portion of the upgrade it wiped my Hybrid/PMBR partition.  I can still mount and access the Windows NTFS partition from OS X however upon selecting at startup it will not boot the windows partition.  After running gptsync from rEFInd I have an entry in my MBR table but it's only created my system partition on the MBR, not my windows 'system reserved' boot partiton.  Can I somehow manually edit the HybridMBR table to include the correct 4 partitions (System Reserved starting at 150,378,824 as the first partition, Windows starting at 151,095,624 as the second partition, and the MacHD starting at 409,640)?  Here's the output from my current disk state:

$ sudo gpt -r -vv show disk0

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

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: 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  148437504      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  148847144     262144        

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

  150378824     716800      4  GPT part - E3C9E316-0B5C-4DB8-817D-F92DF00215AE

  151095624  339139089      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  490234713          6        

  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 -  151095623] <Unknown ID>

*2: 07 1023 254  63 - 1023 254  63 [ 151095624 -  339139089] 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    

I don't understand why you have an MSR partition, which is only necessary when UEFI booting Windows. There is no MBR equivalent for this partition type and it's not use for booting Windows. If you've managed to install Windows on a Mac to EFI boot, instead of CSM-BIOS boot, then you don't need a hybrid MBR at all.

Hey, Chris, you have been fantasic. I have been following your discussion to date. I have upgraded macbook pro to Mavericks and like others my bootcamp had gone leaving me with 'disk0s4' So far i have followed the gdisk options to recover drive that was highlighted by tomd007 and franky.

here is some info:

I have now got the windows drive in boot menu but I get 'no operating system'

Hope you can help.

Put another way: If you follow the Boot Camp Installation & Setup Guide, Windows is installed as a single partition only, and it is a CSM-BIOS installation that depends on a hybrid MBR. No other method is supported. So I don't know what you've done.

Your GPT now has five partitions, so you obviously haven't installed it per the guide. So the question is, how did you install it? I'm going to guess that it's a UEFI install, in which case there isn't a way to convert it into a support CSM-BIOS install. You'd have to delete the two Windows partitions, create a single new one, then create a new hybrid MBR, and then from the Windows installer reformat the new single partition and reinstall.

If it is a UEFI install, and you want to preserve that, then you need to replace the hybrid MBR with a protective MBR. And then try to repair the installation using Windows startup repair *booted in EFI mode*. If you boot the install media in BIOS mode, Windows only supports BIOS+MBR repairs. If you boot the install media in EFI mode, Windows only supports EFI+GPT+EFI System partition repairs.

Macs are booting in EFI mode for non-OS X OS's if you use the option key at boot time, and choose the EFI option for that system's install media. If you choose an icon labeled Windows, that's CSM-BIOS boot mode.

@mrmcb

Well you couldn't have followed all of the previous advice and steps or you wouldn't have the results you've posted.

Your start sector for the 4th partition is clearly wrong, I don't know where you came up with 1239961600 as that's not one of the options in testdisk. In testdisk, using the up/down arrow keys, you need to choose each of the NTFS options, and press P to list files. If you get an error message, then that NTFS choice isn't the right one, you need to go back to the listing (quit) and then use arrow keys to highlight a different NTFS option, press P to list files, etc. until you get a valid file listing of your Windows files. Once you have listed files successfully, quit again to go back to the listing and use the start and end values for that NTFS option, in gdisk. The start value in testdisk = First sector in gdisk. The end value in testdisk = Last sector in gdisk.

The other thing is that somehow your MBR has totally the wrong ID code of 03, I really don't know how you managed to do that. In any case that can be fixed when you create a new hybrid MBR which you can only do once you fix the GPT first.

I might be wrong, but I'll bet dollars to donuts that you made changes in gdisk but you didn't use the w command to write them out to disk. Your existing fdisk and gpt results look like what I'd expect to see BEFORE creating the new replacement partition 4 in gdisk, based on testdisk information.

Christopher, thanks again, you are sooo helpful!

I have found the list of files :

My last job then is the gdisk portion.....

This is a little scary as i do not understand and I worry i erase something.

is there any post that is specific to instructions needed to follow or can you guide me?

Think i have found the info, was it the instructions that you gave sumnerrain on page 53?

I am cautious and will wait for the OK.

Fixed my problem by simply using gdisk to sync the MBR from the valid GPT; all is working perfectly now.  Update to my (albiet non-standard) GPT partition and hybrid MBR map:

$ sudo gpt -r -vv show disk0

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

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: 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  148437504      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  148847144     262144        

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

  150378824     716800      4  GPT part - E3C9E316-0B5C-4DB8-817D-F92DF00215AE

  151095624  339139089      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  490234713          6        

  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    0   0   2 -   25 127  14 [         1 -     409639] <Unknown ID>

*2: 0C 1023 254  63 - 1023 254  63 [ 150378824 -     716800] Win95 FAT32L

3: 07 1023 254  63 - 1023 254  63 [ 151095624 -  339139089] HPFS/QNX/AUX

4: AF   25 127  15 - 1023 254  63 [    409640 -  148437504] HFS+