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 45 of 102 last Next
  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 20, 2013 11:29 PM in response to Scotch_Brawth
    Level 1 (0 points)
    Aug 20, 2013 11:29 PM in response to Scotch_Brawth

    Christopher Murphy can you please help me.  I upgraded to lion a month ago and tried to boot my windows partition and received the following message:  bootcamp partition missing operating system.  I erased my whole harddrive, reinstalled snow leopard from disk, created bootcamp partition and restored it from disk image, then used migration assistant to transfer files from my lion backup (such as music and pictures).  Before using the migration assistant to transfer the files, my windows that was restored from the disk image worked fine.  After transferring the files from the lion backup, Snow Leapord works fine.  When I reboot using Bootcamp as startup disk I get the error:  bootcamp partition missing operating system. 

     

    Results for "sudo gpt -r -v show disk0"

    result 1.png

     

     


    Results for "sudo fdisk /dev/disk0"

    result 2.png

     

    Thanks in advance!

  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 20, 2013 11:33 PM in response to Christopher Murphy
    Level 1 (0 points)
    Aug 20, 2013 11:33 PM in response to Christopher Murphy

    Christopher Murphy can you please help me.  I upgraded to lion a month ago and tried to boot my windows partition and received the following message:  bootcamp partition missing operating system.  I erased my whole harddrive, reinstalled snow leopard from disk, created bootcamp partition and restored it from disk image, then used migration assistant to transfer files from my lion backup (such as music and pictures).  Before using the migration assistant to transfer the files, my windows that was restored from the disk image worked fine.  After transferring the files from the lion backup, Snow Leapord works fine.  When I reboot using Bootcamp as startup disk I get the error:  bootcamp partition missing operating system. 

     

    Results from "sudo gpt -r -v show disk0"

    result 1.png

     


    Results from "sudo fdisk /dev/disk0"

    result 2.png

     

    Thanks in advance!

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Aug 20, 2013 11:36 PM in response to DgraytheMac
    Level 3 (555 points)
    Aug 20, 2013 11:36 PM in response to DgraytheMac

    The disk either doesn't have a GPT or it's corrupt. What's the result from each of the following commands:

    diskutil list

    diskutil verifyDisk /dev/disk0

  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 20, 2013 11:51 PM in response to Christopher Murphy
    Level 1 (0 points)
    Aug 20, 2013 11:51 PM in response to Christopher Murphy

    Result of "diskutil list"

     

    result 3.png

     

    Result of "diskutil verifyDisk /dev/disk0"

    result 4.png

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Aug 21, 2013 12:00 AM in response to DgraytheMac
    Level 3 (555 points)
    Aug 21, 2013 12:00 AM in response to DgraytheMac

    Weird result from diskutil verifyDisk; verifyDisk and verifyVolume aren't the same thing. But in any case the GPT appears to be corrupt and needs to be repaired. And it looks like the hybrid MBR is wrong so a new one needs to be created. These aren't coincidences, you're using something that is modifying the partition maps on the disk incorrectly.

     

    Download and install gdisk and execute this command and lets see what it says (that is a lower case L):

     

    sudo gdisk -l /dev/disk0

  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 21, 2013 12:06 AM in response to Christopher Murphy
    Level 1 (0 points)
    Aug 21, 2013 12:06 AM in response to Christopher Murphy

    Result of "sudo gdisk -l /dev/disk0"


    result 5.png

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Aug 21, 2013 12:14 AM in response to Christopher Murphy
    Level 3 (555 points)
    Aug 21, 2013 12:14 AM in response to Christopher Murphy

    Huh. OK two things in a new Terminal window:

     

    sudo dmesg

     

    That will take up more than a page, maybe several pages. Copy and past the entire contents from the line of the command to the end to pastebin.org, set the expiration for at least a week, and then post the URL.

     

    Next:

     

    sudo gdisk /dev/disk0

     

    At the command prompt:

    v  <return>

  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 21, 2013 12:31 AM in response to Christopher Murphy
    Level 1 (0 points)
    Aug 21, 2013 12:31 AM in response to Christopher Murphy

    Pastebin URL:  http://pastebin.com/Q5PSLfBi

     

     

    Result of "sudo gdisk /dev/disk0"


    result 6.png

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Aug 21, 2013 12:47 AM in response to DgraytheMac
    Level 3 (555 points)
    Aug 21, 2013 12:47 AM in response to DgraytheMac

    So what's up with the abnormal shutdowns?

     

    As for fixing the hybrid MBR, in gdisk you'll go to the recovery menu with r <return> and then h <return> to make a new hybrid MBR. Then enter

     

    2 3

     

    That's 2<space>3<return>

     

    Add GPT to MBR first entry? Yes.

    <return> to accept default type code

    GPT 2 MBR 2 bootable? No.

    <return> to accept default type code

    GPT 3 MBR 3 bootable? Yes.

    Protect more partitions? No.

    w <return>

    y

     

    Reboot.

  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 21, 2013 12:56 AM in response to Christopher Murphy
    Level 1 (0 points)
    Aug 21, 2013 12:56 AM in response to Christopher Murphy

    What abnormal shutdowns?  I got the blue screen with disk memory wiping away about a week or two ago on the Bootcamp partition but hurried up and held the power button until it shut off if that's what you're talking about

     

    For the steps you mentioned i'm getting another option:

    result 7.png

  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 21, 2013 1:01 AM in response to DgraytheMac
    Level 1 (0 points)
    Aug 21, 2013 1:01 AM in response to DgraytheMac

    Never mind i understand the steps, sorry about that.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Aug 21, 2013 1:02 AM in response to DgraytheMac
    Level 3 (555 points)
    Aug 21, 2013 1:02 AM in response to DgraytheMac

    <return> to accept it. It is actually a partition type hex code...so it calls it hex code, I called it type code.

  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 21, 2013 1:12 AM in response to Christopher Murphy
    Level 1 (0 points)
    Aug 21, 2013 1:12 AM in response to Christopher Murphy

    Ok.  Completed the steps after rebooting to Snow Leapord:  everythings fine.  When rebooting to Bootcamp partition:  It now says that it is a non-system disk, press any key to reboot.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Aug 21, 2013 8:34 AM in response to DgraytheMac
    Level 3 (555 points)
    Aug 21, 2013 8:34 AM in response to DgraytheMac

    Now you'll need to boot the Windows install DVD and run Windows startup repair. And if that doesn't work then you'll need to read Bootrec.exe write up in this thread.

  • by DgraytheMac,

    DgraytheMac DgraytheMac Aug 21, 2013 12:10 PM in response to Christopher Murphy
    Level 1 (0 points)
    Aug 21, 2013 12:10 PM in response to Christopher Murphy

    so should i do this if disk utility is showing that there are 0 files on it now  as shown in the picture below?  There was 200+GB of files used on there before it messed up.  Or should I just try to reinstall the disk image I have on my external?:

    result 8.png

     

    I also reran the command "sudo gpt -r -v show disk0" and "sudo fdisk /dev/disk0" which yields the following results:

    result 9.png

     

    result 10.png

     

     

    Or should I still use the Bootrec.exe tool because the repair with the DVD didn't work?

first Previous Page 45 of 102 last Next