Skip navigation

Repairing Boot Camp after creating new partition

177324 Views 1,254 Replies Latest reply: Apr 18, 2014 12:22 PM by Loner T RSS
  • BobTheFisherman Level 6 Level 6 (10,570 points)
    Currently Being Moderated
    Jan 17, 2013 6:22 AM (in response to DSC426)

    DSC426 wrote:

     

    Here is a screen capture of how it is configured.  Also, I didn't start a new thread because this seemed the most relevant to the topic with posts just days ago.  Either way, just looking for some help.

     

    Untitled.jpg

     

    As already stated, you can not create multiple partition on a drive containing a Bootcamp partition. If you want help the best way is to not continue a topic in an already solved thread. Many regular users do not bother opening or reading a thread that is marked solved.They focus on new issues, which yours would be if you started a new thread. I'm just trying to help you get the best help you can.

  • Christopher Murphy Level 2 Level 2 (470 points)

    The gdisk output is fine. So what you need to do is go to recovery/transformation and create a new hybrid MBR, add partitions 2 3 4, make only 4 bootable, then write out the new partition tables. That will effectively keep the MBR the same as now, and write out new repaired GPT primary and backup partitions.

     

    Part of the problem in your case is that you keep mixing tools around, using gdisk first before bootcamp and then using it gain after boot camp. I can't really follow what you're doing. And on top of it, you're using Windows 8 which while it should work, in every native installation of it I've seen it uses either 2 or 3 partitions which is totally incompatible with how Apple supports Windows 7. It should be possible to do a single partition installation of Windows 8 like Windows 7, but I've never tried it and seems to be horribly off topic because it's completely unsupported by Apple. For such a thing you are 1000% better off putting Windows 8 in a VM.

  • Christopher Murphy Level 2 Level 2 (470 points)
    Currently Being Moderated
    Jan 17, 2013 7:29 AM (in response to DSC426)

    You cannot do this and have the Apple prescribed partition scheme. By adding an additional exFAT partition, Apple's tools intentionally, by design, break Windows bootability. It's possible to regain bootability but you will not be able to either read or write to the OS X partition from within Windows.

     

    Using gdisk, you need to go to the recovery menu, create a new hybrid MBR, answer yes to the first question, then add partitions 4 and 5 to the MBR, making only partition 5 bootable. You will be able to use the exFAT volume in OS X and Windows. You will be able to read (optionally write) the Windows volume in OS X as well. But again, when you're in Windows, you will not be able to see or use the OS X partition. Further, this partition arranagement is not what Apple uses, so it's possible for Disk Utility or a future installer to break the bootability of this arranagement.

     

    And last, exFAT is a bad choice for a volume format. It's really meant for flash media like USB sticks, CF and SDXC cards. Not SSD or HDD. It has only one FAT, so if it gets corrupt you will lose all data. You're better off using FAT32. If you need bigger file support, or for larger volumes, then you need to use NTFS.

  • Christopher Murphy Level 2 Level 2 (470 points)

    You can not create multiple partitions on a drive with a Bootcamp partition. You likely have to start over.

     

    Both are untrue. The fact is, Disk Utility lets you create multiple additional partitions on a drive with a Boot Camp partition, and Apple has zero knowledge base articles proscribing such action. And yet, in effect, when you do this, the user experiences data loss in that they no longer have Windows bootability. It's pretty heinous. And if more advanced users weren't so nervous about learning something new like how to repair these Apple tool induced problems, with a tool like gdisk, then people wouldn't have to start over. It's a really simple repair the vast majority of the time, it's just that Apple provides no tools to fix this once you've screwed it up, which their tools freely let you do to the point it's inticement.

  • DSC426 Calculating status...

    Thank you... Quick response!  A couple of updates.  I have only used gdisk for the read-only information output I provided.  Didn't even know this tool existing before I had the problem... Did it all through the GUI bootcamp / GUI disk utility originally and haven't done anything, except carve out space using the OSX GUI Disk Utility since for the new exfat partition - which is when it broke.  Also, I am running Windows 7 Pro 64bit not Windows 8.

     

    My original goal in making the change was to provide Windows more space, in a separate partition, not to try to read/write to OSX from Windows.  In fact the opposite, I was thinking while using OSX I would be able to read/write files that I put there (ExFAT partition) when I was in Windows previously.  In other words, have a partition both Windows and OSX could see/use, independent of the OS I booted into.  When I initially set things up I carved out more space for OSX than Windows and am finding I need more space to use Windows today than I do in OSX.  Originally, I set Windows up to use 64GB NTFS.  The remainder ~188GB for OSX.  In a 1st choice) PERFECT scenario I would like each to be equally split approx128GB NTFS, approx 128GB OSX.  I don't know if I can do that now somehow and not lose data.  2nd choice) Revert to my previous config 64GB NTFS, the rest OSX losing no data and just scraping/removing the ExFAT partition -it contains no data.  3rd Choice) Get it to boot to either and live with the ExFAT, or remove it (ExFAT) using disk util after I have my dual boot option back and working and return the space back to OSX. 

     

    It was a crazy little experiment and I think simply using a portable usb hdd would be just fine so long as I can get back to where I was.

     

    Thoughts?  Help?

  • Berend de Meyer Level 1 Level 1 (5 points)

    Hi Christopher,

     

    THANKS for your prompt reply! I'll give it a shot this weekend!

     

    And yes, as I mentioned earlier, this is rocket sience for me....

     

    Cheers

  • cyberguy1 Calculating status...

    I need help... value 5 is the partitions disk0s number right? so in this case I put 4 instead of 5?

  • ashlandguy2 Calculating status...

    When I put that command in, it says command not found. I'm on a MacBook Late 2009 10.8.2 if that helps

  • ashlandguy2 Level 1 Level 1 (0 points)

    Nevermind, I found it.

  • RemiRobi Calculating status...
    Currently Being Moderated
    Jan 18, 2013 10:21 PM (in response to ashlandguy2)

    This post is incredible ! So much information in it...But I didn't manage to boot my windows 7 bootcamp partition.

    Here is my situation (I tried several things without succes, so finally, I reformat disk0) :

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *500.1 GB   disk0

       1:                        EFI                         209.7 MB   disk0s1

       2:                  Apple_HFS Vidéos                  499.8 GB   disk0s2

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *480.1 GB   disk1

       1:                        EFI                         209.7 MB   disk1s1

       2:                  Apple_HFS iMac                    388.0 GB   disk1s2

       3:       Microsoft Basic Data BOOTCAMP                91.8 GB    disk1s3

     

    sudo gpt -r -vv show disk0

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

    gpt show: disk0: PMBR 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         PMBR

              1          1         Pri GPT header

              2         32         Pri GPT table

             34          6        

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

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

      976510984     262151        

      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 -  976773167] <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 

     

    sudo gpt -r -vv show disk1

    gpt show: disk1: mediasize=480103981056; sectorsize=512; blocks=937703088

    gpt show: disk1: Suspicious MBR at sector 0

    gpt show: disk1: Pri GPT at sector 1

    gpt show: disk1: Sec GPT at sector 937703087

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

      758222120     262872        

      758484992  179216384      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      937701376       1679        

      937703055         32         Sec GPT table

      937703087          1         Sec GPT header

     

    sudo fdisk /dev/disk1

    Disk: /dev/disk1          geometry: 58369/255/63 [937703088 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 254  63 [    409640 -  757812480] HFS+       

    *3: 07 1023 254  63 - 1023 254  63 [ 758484992 -  179216384] HPFS/QNX/AUX

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

     

    Can anyone help me ?

  • RemiRobi Level 1 Level 1 (30 points)
    Currently Being Moderated
    Jan 19, 2013 8:05 AM (in response to RemiRobi)

    Hi,

    I've just install REFIT and it solves the problem !! It was so simple...

     

    I uninstalled it, because I don't want to have a boot menu.

     

    Rémi

  • frisco330 Calculating status...

    Hello All I have the same issue where I resized the OSX partition and then lost my boot camp.  I have tried all the steps  listed here to recreate the PMBR and then tried to use windows repair to fix the bootloader with no sucess.  So I wanted to solicit any advice on next steps for recovery, I am thinking the partition boundaries are off a bit so that it is unable to be recognized from with in the windows environment as NTFS.  Here is my output for the basic information.  I noticed Christopher Murphy is indeed the expert and applaud him for the help he provides!

     

    gpt -r -vv show disk0

    gpt show: disk0: mediasize=320072933376; sectorsize=512; blocks=625142448

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 625142447

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

      304014520     262144        

      304276664  246315112      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      550591776   74550639        

      625142415         32         Sec GPT table

      625142447          1         Sec GPT header

     

     

    diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *320.1 GB   disk0

       1:                        EFI                         209.7 MB   disk0s1

       2:                  Apple_HFS Macintosh HD            155.4 GB   disk0s2

       3:       Microsoft Basic Data                         126.1 GB   disk0s3

     

    Any advice is greatly welcomed!

     




    MacBook Pro, Mac OS X (10.6.8)
  • RemiRobi Level 1 Level 1 (30 points)
    Currently Being Moderated
    Jan 20, 2013 6:12 PM (in response to frisco330)

    For me, installing refit soved all my problems... There is no risk to try : http://refit.sourceforge.net

  • frisco330 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jan 20, 2013 6:16 PM (in response to RemiRobi)

    Thank you RemiRobi for the quick response,

    I tried that as well.  Basically it can not find the boot loader I get the missing operating system message. 

  • Christopher Murphy Level 2 Level 2 (470 points)
    Currently Being Moderated
    Jan 20, 2013 8:06 PM (in response to frisco330)

    I need to see the result from

    sudo fdisk /dev/disk0

1 ... 23 24 25 26 27 ... 85 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (21)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.