1 4 5 6 7 8 9 Previous Next 130 Replies Latest reply: Jun 2, 2013 3:21 PM by Christopher Murphy Go to original post
  • 75. Re: Unable to boot up in bootcamp after installing Mountain Lion
    Christopher Murphy Level 3 Level 3 (525 points)

    The gpt and diskutil commands only show the GPT. Problems booting Windows on Apple hardware are almost always the result of a malformed (hybrid) MBR. To display the MBR:

     

    sudo fdisk /dev/disk0

  • 76. Re: Unable to boot up in bootcamp after installing Mountain Lion
    Christopher Murphy Level 3 Level 3 (525 points)

    My suggestion is that people should just stop using Boot Camp. Apple hardware doesn't make for the best gaming platform, and that's about the only legitimate need for native booting Windows anyway. None of these partition and bootloader problems happen when running Windows in a VM, so that's what most people should be doing.

  • 77. Re: Unable to boot up in bootcamp after installing Mountain Lion
    Ricardo Ramalho Level 1 Level 1 (0 points)

    I'm already doing just that... Visual Studio 2010 (and 2012) is kinda slow on a VM, and anyone doing that should do:

    - manual backup of the VM files

    - add an exclusion to Time Machine, so that the backup process don't get jammed too many times, when passing on the VM directories...

     

     

  • 78. Re: Unable to boot up in bootcamp after installing Mountain Lion
    TheBoz2 Level 1 Level 1 (0 points)

    In my case I like the MBP.  It is a great laptop.  However I work in Windows.  The only time I use OSX is to edit some videos, or iOS development.  **** the only reason I upgraded to ML was to get the new Xcode.

     

    So finally after almost 12 hours of ****, here is what I had to do to get up and running.

     

    Reinstall Primary OS that came with the laptop, Leopard.  Wipe all partitions and do the fresh install.

    After that I had to install the Snow Leopard.

    Then Install the App Store

    Then Install Mountian Lion

    Then Run Boot Camp, save drivers, and Install Windows 7.

    Build Windows 7 from the ground up, and wait the 10 years for all the Service Packs to update.

     

    If you are boot camped and you are going to do a Mountion Lion update be sure to back up all your stuff, and be ready for one **** of an adventure.  Because Apple is going to F U_C K you up down right and left.

     

    Apple support is 0 help in this matter.  They more or less told me to pound sand.

     

    So if you guy want me to pull any settings from my machine now that it is all fresh and working let me know.

  • 79. Re: Unable to boot up in bootcamp after installing Mountain Lion
    aathum Level 1 Level 1 (0 points)

    Guys:

    I had the exact same problem. Windows 7 worked fine and after mountain lion upgrade bootup screen would not come up  Black screen. All the discussions on the boot records was good. I was able to get to an apple guy and by a stroke of good fortune and some help from GOD no kidding. We tried the following and it worked fine:

     

    1. Start OS X in single user mode command+s on boot

    2. When the root prompt comes up type fsck -fy

    3. Type reboot after its done.

    4. Here is the link to the articlehttp://support.apple.com/kb/TS1417?viewlocale=en_US

    the step where fsck -fy is executed is about halfway down the document. Their example shows /sbin/fsck -fy but the /sbin/ isn't needed unless you proceed this command with other commands.

     

    The process will check the disk and the MBR and correct any issues.

    The boot worked fine after that. You will see a new recover disk created by Mountain lion and a new option for booting from network.

    Pretty cool

    Arthur

  • 80. Re: Unable to boot up in bootcamp after installing Mountain Lion
    Have you seen my elephant? Level 1 Level 1 (0 points)

    I think I might have a solution to this, but it probably needs more people to test it.

     

    I just downloaded the latest Windows Support Software, using the Boot Camp Assistant in Mountain Lion. After the software was burned to a DVD, Boot Camp Assistant asked for permission to install a new helper program.

     

    I'm thinking the helper program fixed some missing settings.

     

    Since then, Windows has booted successfully every time. I didn't even need to install the support software.

     

    Let me know if this works, or if not.

  • 81. Re: Unable to boot up in bootcamp after installing Mountain Lion
    g5cal Level 1 Level 1 (0 points)

    After upgrading to OS X 10.8 my Boot Camp partition disappeared in the same way as for Ricardo Ramalho. I can see it in Disk Utility as a gray partition with the name "disk0s4" that cannot be mounted.

     

    How can I fix the partition table with GPT fdisk? Could you please give some advise Christopher Murphy?

     

     

    This is the info that "sudo gpt -r -vv show disk0" shows in the Terminal:

    mbp-2:~ user$ sudo gpt -r -vv show disk0

    gpt show: disk0: mediasize=2000398934016; sectorsize=512; blocks=3907029168

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 3907029167

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

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

      3627284576   123387808        

      3750672384   156356608      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      3907028992         143        

      3907029135          32         Sec GPT table

      3907029167           1         Sec GPT header

  • 82. Re: Unable to boot up in bootcamp after installing Mountain Lion
    g5cal Level 1 Level 1 (0 points)

    And:

     

    sudo fdisk /dev/disk0

    Disk: /dev/disk0geometry: -1539437/4/63 [-387938128 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 - -669361896] HFS+       

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

    4: 0C 1023 254  63 - 1023 254  63 [-544294912 -  156356608] Win95 FAT32L

  • 83. Re: Unable to boot up in bootcamp after installing Mountain Lion
    Christopher Murphy Level 3 Level 3 (525 points)

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

    3627284576   123387808       

    3750672384   156356608      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

     

    You have 58GB of free space in between partitions not being used for anything. What it looks like to me is that at some point before upgrading you were messing around with partitions in Disk Utility, or you had a botched Boot Camp Assistant attempt at some point and it was never fixed.

     

    First I'd see if you can recapture that 58GB easily for Mac OS X or not with this command:

    diskutil resizevolume /dev/disk0s2 limits

     

    Only after you get the GPT in order should you then create a new hybrid MBR to get Windows to boot again.

  • 84. Re: Unable to boot up in bootcamp after installing Mountain Lion
    g5cal Level 1 Level 1 (0 points)

    Thanks Christopher. But that command doesn't seem to remove the 58GB of free space.

    Do I need to boot up in single user mode first?

     

    Could I fix the partition table and the Boot Camp "bootability" without fixing the free 58GB? I don't need them. I just want to backup the stuff on the Boot Camp partition.

     

    diskutil resizevolume /dev/disk0s2 limits

    For device disk0s2 iMac:

            Current size:  1.9 TB (1856309964800 Bytes)

            Minimum size:  1.2 TB (1215110606848 Bytes)

            Maximum size:  1.9 TB (1856309964800 Bytes)

     

     

    sudo fdisk /dev/disk0

    Disk: /dev/disk0          geometry: -1539437/4/63 [-387938128 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 - -669361896] HFS+       

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

    4: 0C 1023 254  63 - 1023 254  63 [-544294912 -  156356608] Win95 FAT32L

     

    sudo gpt -r -vv show disk0

    Password:

    gpt show: disk0: mediasize=2000398934016; sectorsize=512; blocks=3907029168

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 3907029167

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

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

      3627284576   123387808        

      3750672384   156356608      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      3907028992         143        

      3907029135          32         Sec GPT table

      3907029167           1         Sec GPT header

     


  • 85. Re: Unable to boot up in bootcamp after installing Mountain Lion
    Christopher Murphy Level 3 Level 3 (525 points)

    The diskutil command was not designed to remove the 58G. It was designed just to find out if it can be done. And it can't. It would require some surgery to relocated the Recovery HD out of the way, then you could recapture that free space. So we'll just move on and make Windows bootable again.

     

    The Apple included fdisk can't edit an MBR on a disk of this size. So you'll need to go to sourceforge and download 'GPT fdisk' to create a new hybrid MBR. What needs to change is in the MBR, 4th line:

    4: 0C 1023 254  63 - 1023 254  63 [-544294912 -  156356608] Win95 FAT32L

    The 0C is wrong, it should be 07. And it should be marked bootable, but isn't. gdisk can fix this, but it's a manual process, only command line. Here are the commands to use, with explanations in brackets.

     

    sudo gdisk /dev/disk0

    r       [recovery menu]

    h       [create new hybrid MBR]

    2 3 4   [add partitions 2 3 and 4 to MBR] 

    y       [place 0xEE partition as #1]

    <enter> [accept the default]

    n       [not bootable]

    <enter> [accept default]

    n       [not bootable]

    <enter> [accept default]

    y       [mark as bootable]

    w       [write changes to disk]

    y       [confirm you really want to do this]

     

    If you don't understand what any of this means, then don't do it. You'll just have to live with the Boot Camp backup you already have, wipe your disk and start over.

  • 86. Re: Unable to boot up in bootcamp after installing Mountain Lion
    g5cal Level 1 Level 1 (0 points)

    Thanks alot Christopher. I changed it to 07 and marked it as bootable.

     

    Now it appears as a bootable partition during start up. But the Windows 7 system on it doesn't work.

    And the Windows 7 DVD cannot repair the "start up issues".

     

    I guess I wont be able to backup the content on the Boot Camp partition then?

     

    The OS X 10.8 installer is really bad. Apple should inform that any previous Boot Camp partition will get "destroyd" during the 10.8 upgrade.

  • 87. Re: Unable to boot up in bootcamp after installing Mountain Lion
    Christopher Murphy Level 3 Level 3 (525 points)

    I disagree. Most users are not having this problem. I still don't know why a small percentage do.

     

    Backing up regularly, especially before major upgrades, is a basic computer requirement if you care at all about the data. It doesn't require any warnings in advance. I do feel that Apple should warn users that Boot Camp increases the risk.

     

    Does the Windows (BOOTCAMP) volume mount in Mac OS X?

  • 88. Re: Unable to boot up in bootcamp after installing Mountain Lion
    g5cal Level 1 Level 1 (0 points)

    Okay. Maybe just a few users have these issues.

     

    And ofcourse. One should back up all data regularly, especially before upgrades.

     

    The partition doesn't mount in Finder or with Disk Utility. It is still grey as before.

     

    I will try to clone it to an external FAT32 formatted drive with Data Rescue 3.2 and see if I can get the files that way.

  • 89. Re: Unable to boot up in bootcamp after installing Mountain Lion
    Christopher Murphy Level 3 Level 3 (525 points)

    Try this and post the results; use the Advance Editor option (upper right side of the forum reply entry) to change the font for your pasted results to Andale Mono so it's easier for me to read. You can copy-paste these into Terminal, just make sure you copy exactly the first to the last character of each line. These are four separate commands. The first two don't generate any results on-screen. The second two do.

     

    dd if=/dev/disk0 of=~/4s_part3.bin skip=3627284576 count=1

    dd if=/dev/disk0 of=~/4s_part4.bin skip=3750672384 count=1

     

    hexdump -C ~/4s_part3.bin

    hexdump -C ~/4s_part4.bin

     

    Basically what this does is reads 1 sector from the very beginning of free space, and the very beginning of what's claimed to be the Windows partition, and stores them into two files in your home directory. Then the second set of commands displays the contents of those files. What I'm looking for is header information for the NTFS volume. Maybe the beginning of the Windows partition is somewhere else.

     

    After you do this you can throw away those two .bin files in your home folder.

1 4 5 6 7 8 9 Previous Next