Scotch_Brawth

Q: Repairing Boot Camp after creating new partition

I'm running OS X 10.8 and Windows 7 x64 Pro.

 

After properly setting up Boot Camp to dual-boot Windows on my Mac mini, I decided to test whether or not it was true that creating another partition (a data partition for OS X) would interfere with Boot Camp.  Wikipedia claims it does interfere but without citing a source, whilst the Boot Camp documentation itself only specifies that the disk must be a single partition _prior_ to setup - there's no mention of whether the disk must be _kept_ that way afterwards.

 

I opened Disk Utility, reduced the size of my OS X parition from 420GB to 80GB, and created a new partition in the unallocated space.  Here's how it looks now:

/___sbsstatic___/migration-images/190/19047693-1.png

When I attempted to proceed with the process, I did receive a warning that doing this (and I quote), "may" cause problems with Boot Camp.  Seeing as it was inconclusive, I thought I'd give it a shot - nothing ventured…

 

Of course, it borked Boot Camp, otherwise I wouldn't be posting here.  Whilst OS X boots just fine, the Boot Camp partition now no longer shows up in the Startup Manager, though it does in the Startup Disk prefPane.  If I do attempt to boot into Boot Camp, I receive the following message on a black screen:

No bootable device --- insert boot disk and press any key

The advice given to someone who had this same problem was, "fix your damaged Boot Camp volume."  But I'm at a loss as to how to do that.

 

So, anyone know how to proceed now so that I can keep my partitions as is, whilst fully restoring normal Boot Camp functionality?

Mac mini (Mid 2011), Mac OS X (10.7.4)

Posted on Jul 26, 2012 11:28 PM

Close

Q: Repairing Boot Camp after creating new partition

  • All replies
  • Helpful answers

first Previous Page 47 of 102 last Next
  • by frankywashere,

    frankywashere frankywashere Oct 22, 2013 7:27 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 22, 2013 7:27 PM in response to Christopher Murphy

    Christopher!

     

    I just installed Mavericks and it broke my BootCamp.

     

    I only have 2 partitions, real simple. one mac, one bootcamp.

     

    The Bootcamp drive is gone, and it shows up in diskutility as "Disk0s4"

     

    anyway to fix this using your magic terminal commands?

     

    Frank

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 22, 2013 7:37 PM in response to spidi21
    Level 3 (555 points)
    Oct 22, 2013 7:37 PM in response to spidi21

    So what you need to do is go back through those steps to create a  new hybrid MBR, and instead of adding only partition #4 to the MBR, add 2 3 4 and only mark the one with Windows as bootable - presumably that's 4 since that's what you did before it worked. For what it's worth, there's a 3 GB gap of unused free space between partitions 3 and 4. So at some point you'll want to back everything up and start from scratch.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 22, 2013 7:40 PM in response to frankywashere
    Level 3 (555 points)
    Oct 22, 2013 7:40 PM in response to frankywashere

    No idea. Provide the result from:

     

    sudo fdisk /dev/rdisk0

    sudo gpt -r -v show /dev/rdisk0

  • by frankywashere,

    frankywashere frankywashere Oct 22, 2013 7:57 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 22, 2013 7:57 PM in response to Christopher Murphy

    Thanks Chris,

     

    here's the screenshot:

     

    Screen Shot 2013-10-22 at 10.56.58 PM.png

  • by frankywashere,

    frankywashere frankywashere Oct 22, 2013 7:58 PM in response to frankywashere
    Level 1 (0 points)
    Oct 22, 2013 7:58 PM in response to frankywashere

    and btw, i had Windows 7 installed and it was formatted NTFS, I beleive.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 22, 2013 10:33 PM in response to frankywashere
    Level 3 (555 points)
    Oct 22, 2013 10:33 PM in response to frankywashere

    Try the 2nd command again you didn't include the gpt part.

  • by defly,

    defly defly Oct 23, 2013 3:24 AM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 23, 2013 3:24 AM in response to Christopher Murphy

    Screen Shot 2013-10-23 at 13.22.55.png

    Hi, also having this issue.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 23, 2013 7:51 AM in response to defly
    Level 3 (555 points)
    Oct 23, 2013 7:51 AM in response to defly

    The problem is the 4th partition in the MBR has the wrong type code and isn't marked bootable. So you can either fix this using fdisk or gdisk. The gdisk method is probably better documented in this thread. The fdisk method is faster.

     

    sudo fdisk -e /dev/disk0

    setpid 4

    07

    flag 4

    write

  • by defly,

    defly defly Oct 23, 2013 8:13 AM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 23, 2013 8:13 AM in response to Christopher Murphy

    Just done it. Now with holding Alt button I can see Windows, but when I choose it, prints only "Missing operating system"

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 23, 2013 8:26 AM in response to defly
    Level 3 (555 points)
    Oct 23, 2013 8:26 AM in response to defly

    There is a large 28GB gap between partitions 3 and 4. My guess is this is the result of an aborted attempt at using Disk Utility to modify the partitions of the disk, something Apple really needs to disallow once a disk has been "bootcamped". Their documentation indirectly says this, basically if you need to make changes you have to blow away Windows with Bootcamp Assistant and start from scratch anytime you want to make any change. But Disk Utility will let you get into big, big trouble.

     

    Anyway, can you confirm/deny that you can see the bootcamp volume in OS X? Can you navigate the folders within that bootcamp volume, and find your stuff on it? If you can, then Windows Startup Repair should be able to fix this problem. If you don't have a volume named BOOTCAMP automounted while you're in OS X, then it's a lot trickier.

  • by defly,

    defly defly Oct 23, 2013 8:30 AM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 23, 2013 8:30 AM in response to Christopher Murphy

    Thank you for help! I can't see BOOTCAMP volume through finder.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 23, 2013 9:17 AM in response to defly
    Level 3 (555 points)
    Oct 23, 2013 9:17 AM in response to defly

    In that case you're in testdisk territory. It's verbose and may propose multiple options each of which you just need to test to see which one gets you access to your data. At the least it'll let you get access to documents at things like that. It might be able to suggest one or more possible partition start-end values, and if you get the right combination, it will restore boot. And if not, you'll need to back everything up, and then see if Bootcamp Assitant will delete what you have so you can start over with Windows. If not, then it'll tell you to reformat the whole disk with a single partitition.

  • by frankywashere,

    frankywashere frankywashere Oct 23, 2013 2:39 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 23, 2013 2:39 PM in response to Christopher Murphy

    sorry Chris, here you go, and man you're an all-star.

     

    Screen Shot 2013-10-23 at 5.38.29 PM.png

  • by frankywashere,

    frankywashere frankywashere Oct 23, 2013 2:47 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 23, 2013 2:47 PM in response to Christopher Murphy

    Also Chris, I have no idea if this helps you, but I used testdisk and found this crap out which I have no idea what it means.

     

    Screen Shot 2013-10-23 at 5.45.26 PM.png

    Screen Shot 2013-10-23 at 5.45.01 PM.png

  • by tomd007,

    tomd007 tomd007 Oct 23, 2013 5:13 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 23, 2013 5:13 PM in response to Christopher Murphy

    Hello Chriss... I am another guy with a similar problem... I have upgraded to Mavericks and it killed my boot camp where I have my Windows 7 (64x) installation, which I cannot aford to lose as there is all my office work.

     

    Before Mavericks and a couple of months ago, I had reduced the size of my Mac OS partition with Disc Utility and increased my Windows partition with a third party software in Windows 7 ... I realized that DiscUtility didn't recognized this change properly, and it looked like the image below, but I could access my Windows installation by pressing "Atl" during boot up each time. i was working that way.

     

    I installed Mavericks yesterday, and now I cannot access my boot camp partition at all. Please see if you can help me.

     

    I have ran the commands you have indicated here and this are the results:

     

    Last login: Wed Oct 23 18:15:31 on console

    Toms-Laptop:~ tom$ sudo gpt -r -vv show disk0

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

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

      784539400  114110712        

      898650112   78123008      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      976773120         15        

      976773135         32         Sec GPT table

      976773167          1         Sec GPT header

    Toms-Laptop:~ tom$ sudo fdisk /dev/rdisk0

    Password:

    Disk: /dev/rdisk0          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 -  782860224] HFS+       

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

    4: 0C 1023 254  63 - 1023 254  63 [ 898650112 -   78123008] Win95 FAT32L

    Toms-Laptop:~ tom$

     

    This is how it looks from Disk Utility:

    Disk Utility.png

     

    You can see a section that looks unpartitioned... that's the amount I increased my partition from Windows and the same amount I decreased the Mac partition from Disk Utility a couple of months ago... however I used to access Windows by pressing "Atl" while booting.

     

    Please let me know your comments.

     

    Many thanks!

first Previous Page 47 of 102 last Next