1 20 21 22 23 24 Previous Next 1,374 Replies Latest reply: Jul 10, 2014 1:49 PM by NikkuShouri Go to original post
  • 315. Re: Repairing Boot Camp after creating new partition
    Alex Senkevich Level 1 Level 1 (0 points)

    Hello Christopher,

    sorry for bothering but i have another question.
    I made everything like you wrote in steps 1 and 2 and got my Windows disappeared from boot menu.

    So i had no chance to get to the step 3.

    Here is what i have now

     

    ==============================================================================

    sh-3.2# gpt -r -vv show disk0

    gpt show: disk0: mediasize=256060514304; sectorsize=512; blocks=500118192

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 500118191

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

      382668504        296       

      382668800  117448704      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      500117504        655       

      500118159         32         Sec GPT table

      500118191          1         Sec GPT header

    ==============================================================================

    sh-3.2# fdisk /dev/disk0

    Disk: /dev/disk0    geometry: 31130/255/63 [500118192 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 -  382258864] HFS+       

    *3: 07 1023 254  63 - 1023 254  63 [ 382668800 -  117448704] HPFS/QNX/AUX

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

    ==============================================================================

    sh-3.2# gpt -r -vv show disk1

    gpt show: disk1: mediasize=240057409536; sectorsize=512; blocks=468862128

    gpt show: disk1: Suspicious MBR at sector 0

    gpt show: disk1: Pri GPT at sector 1

    gpt show: disk1: Sec GPT at sector 468862127

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

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

      468862088          7       

      468862095         32         Sec GPT table

      468862127          1         Sec GPT header

    ==============================================================================

    sh-3.2# fdisk /dev/disk1

    Disk: /dev/disk1    geometry: 29185/255/63 [468862128 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 -  467182912] HFS+       

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

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

    ==============================================================================

    sh-3.2# dd if=/dev/disk0 count=1 2>/dev/null | hexdump -C

    00000000  fa 31 c0 8e d8 8e c0 8e  d0 bc 00 7c fb fc 89 e6  |.1.........|....|

    00000010  bf 00 06 b9 00 01 f3 a5  ea 1d 06 00 00 88 16 00  |................|

    00000020  08 b4 08 cd 13 31 c0 88  f0 40 a3 f0 06 80 e1 3f  |.....1...@.....?|

    00000030  88 0e f2 06 be be 07 31  c0 b9 04 00 f6 04 80 74  |.......1.......t|

    00000040  03 40 89 f7 83 c6 10 e2  f3 83 f8 01 75 73 8a 16  |.@..........us..|

    00000050  00 08 b8 00 41 bb aa 55  31 c9 30 f6 f9 cd 13 72  |....A..U1.0....r|

    00000060  23 81 fb 55 aa 75 1d f6  c1 01 74 18 57 be e0 06  |#..U.u....t.W...|

    00000070  8b 5d 08 89 5c 08 8b 5d  0a 89 5c 0a 8a 16 00 08  |.]..\..]..\.....|

    00000080  b4 42 eb 2a 57 8b 45 08  8b 55 0a f7 36 f2 06 42  |.B.*W.E..U..6..B|

    00000090  89 d1 31 d2 f7 36 f0 06  88 c5 d1 e8 d1 e8 24 c0  |..1..6........$.|

    000000a0  08 c1 88 d6 8a 16 00 08  bb 00 7c b8 01 02 cd 13  |..........|.....|

    000000b0  72 16 5e 81 3e fe 7d 55  aa 75 08 fa ea 00 7c 00  |r.^.>.}U.u....|.|

    000000c0  00 77 05 be f4 06 eb 03  be 0f 07 ac 20 c0 74 0c  |.w.......... .t.|

    000000d0  b4 0e 8a 3e 62 04 b3 07  cd 10 eb ef eb fe 00 00  |...>b...........|

    000000e0  10 00 01 00 00 7c 00 00  00 00 00 00 00 00 00 00  |.....|..........|

    000000f0  00 00 00 00 4d 69 73 73  69 6e 67 20 6f 70 65 72  |....Missing oper|

    00000100  61 74 69 6e 67 20 73 79  73 74 65 6d 0d 0a 00 4f  |ating system...O|

    00000110  70 65 72 61 74 69 6e 67  20 73 79 73 74 65 6d 20  |perating system |

    00000120  6c 6f 61 64 69 6e 67 20  65 72 72 6f 72 0d 0a 00  |loading error...|

    00000130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

    *

    000001c0  02 00 ee 7f 0e 19 01 00  00 00 27 40 06 00 80 7f  |..........'@....|

    000001d0  0f 19 af fe ff ff 28 40  06 00 b0 ce c8 16 80 fe  |......(@........|

    000001e0  ff ff 07 fe ff ff 00 10  cf 16 00 20 00 07 00 00  |........... ....|

    000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|

    00000200

    ==============================================================================

    sh-3.2# dd if=/dev/disk1 count=1 2>/dev/null | hexdump -C

    00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

    *

    000001b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 fe  |................|

    000001c0  ff ff ee fe ff ff 01 00  00 00 27 40 06 00 80 fe  |..........'@....|

    000001d0  ff ff af fe ff ff 28 40  06 00 40 a5 d8 1b 00 fe  |......(@..@.....|

    000001e0  ff ff ab fe ff ff 68 e5  de 1b 20 5f 13 00 00 00  |......h... _....|

    000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|

    00000200

    ==============================================================================

     

     

    Please help me and Dec 21 i will save your life ;-)
    Thank you.

    Alex

  • 316. Re: Repairing Boot Camp after creating new partition
    Christopher Murphy Level 3 Level 3 (525 points)

    OK so you've already written out the change, you should reboot and hold down option and see if you get a Windows icon, and then what happens if you choose it.

  • 317. Re: Repairing Boot Camp after creating new partition
    Coffeecoco Level 1 Level 1 (0 points)

    I appologise if you wanted me todo something before hand

     

    Windows Icon has always been there

    i tried it did the same thing black screen

    but parallels can boot the same partition perfectly

  • 318. Re: Repairing Boot Camp after creating new partition
    Christopher Murphy Level 3 Level 3 (525 points)

    @Alex

    *2: AF   25 127  15 - 1023 254  63 [    409640 -  382258864] HFS+      

    *3: 07 1023 254  63 - 1023 254  63 [ 382668800 -  117448704] HPFS/QNX/AUX

     

    This is wrong you set both partitions to be bootable (asterisk means active flag is set). So go back to gdisk, recovery menu, add paritions 2 3, make sure 2 is NOT bootable and 3 is.

  • 319. Re: Repairing Boot Camp after creating new partition
    Christopher Murphy Level 3 Level 3 (525 points)

    @Alex

    Another issue is that your boot loader doesn't appear to be a Windows boot loader. Yours starts with this line:

    00000000  fa 31 c0 8e d8 8e c0 8e  d0 bc 00 7c fb fc 89 e6  |.1.........|....|

    And a Windows boot loader should be this line:

    00000000  33 c0 8e d0 bc 00 7c 8e  c0 8e d8 be 00 7c bf 00  |3.....|......|..|

     

    So invariably it seems you will need to boot from a Windows installer, and use startup repair. If that doesn't work you get to go down the bootrec rabbit hole from command prompt.

  • 320. Re: Repairing Boot Camp after creating new partition
    Alex Senkevich Level 1 Level 1 (0 points)

    Yuppie!
    you made it! Don't think i'm kid! I'm 30 but i'm just happy!
    i got  win menu and entered it.

    then i got screen:
    Screen Shot 2012-12-12 at 12.52.44 AM.png

    i i'm starting to think what can i do. Because i don't have CDROM because my 2nd SSD is placed insted of it.
    And i can't boot from USB stick with Windows 7 install. Because Apple doesn't allow to boot Macbook Pro in this way.

  • 321. Re: Repairing Boot Camp after creating new partition
    Coffeecoco Level 1 Level 1 (0 points)

    WAIT Windows Boots now!!! I think i had a sneaky usb cable pluged into a device that was screwing it up

     

    anyway i get bluescreens now so thats another story i assume

  • 322. Re: Repairing Boot Camp after creating new partition
    Christopher Murphy Level 3 Level 3 (525 points)

    @Alex

    There's a way to do this with a VM, so that you boot the VM with a Windows 7 ISO, while the disk is a real whole disk (the one you're trying to fix) instead of a VM, and run bootrec or startup repair from there.

  • 323. Re: Repairing Boot Camp after creating new partition
    Christopher Murphy Level 3 Level 3 (525 points)

    @Coffeecoco

    Same situation as Alex. You'll need to use a VM to boot a Windows 7 installer ISO, while also having the real full disk available to that VM, and run Windows startup repair. I don't know how to do this in any VM except VBOX.

  • 324. Re: Repairing Boot Camp after creating new partition
    Alex Senkevich Level 1 Level 1 (0 points)

    Thank you Christopher!
    That's what i'm doing now from Parallels. Trying to mount iso and use it as a CD.
    Thank you very much again! How can i add points to your level? Where i need to vote?

    Also feel free to contact me if you need any help with php web development especially with Drupal.

  • 325. Re: Repairing Boot Camp after creating new partition
    Coffeecoco Level 1 Level 1 (0 points)

    Thank you Christopher

    Although I gained another issue, I spent the day on windows 7 and decided to boot into mac os

     

    for some god un known reason my second raid slice was "missing" and would not boot....

    was so disapointed so i was forced to reinstall, the second raid device would not show in mac os installer untill i deleted the raid disk entirely then i had to reinstall a time machine back up.

    at the same time i deleted the windows 7 first to hope that my other raid slice would appear.

     

    so back to square one i dont know what the issue was.  sad face

    Unsure if i want to attempt todo this all over again, in case i get the same problem

    I cant officially use bootcamp to partition my drive because... bootcamp assistant complains that i dont have a dvd drive and cant detect my installer, there for refuse to partition my drive correctly, so im stuck with disk utility.... any suggestions?

  • 326. Re: Repairing Boot Camp after creating new partition
    Christopher Murphy Level 3 Level 3 (525 points)

    VM's are the way to do this. I find Boot Camp totally irritating and risky. If we get UEFI/GPT supported Windows 8 installs, then I might change my mind. But right now you have to tread an extremly narrow path, some of which Apple does not document well, and if you go off the path, abruptly you can find yourself in the world of data loss, and rebuilding a computer for a day or two.

  • 327. Re: Repairing Boot Camp after creating new partition
    Christopher Murphy Level 3 Level 3 (525 points)

    Oh and Disk Utility is treacherous. I trust it with very little these days, in the way of partitioning. I never use it for repartitioning or resizing.

  • 328. Re: Repairing Boot Camp after creating new partition
    Alex Senkevich Level 1 Level 1 (0 points)

    BTW i still can't find a decision how to fix Windows MBR because Paralles doesn't allow to modify it and VM Vare fusion fixed it BUT only for itself. So now i'm running under VM Vare.
    The main problem that i can't but CD-Rom back to macbook because i Windows is on the secondary disk that is placed instead of CDrom. And there is no possibility to start Windows from USB. Stupid situation... The only hope is to try USB external CD-Rom. I hope it will work but have doubds because of USB connection.

  • 329. Re: Repairing Boot Camp after creating new partition
    Christopher Murphy Level 3 Level 3 (525 points)

    It's possible this could be fixed from a linux LiveCD that supports EFI booting, which is needed to boot non-recent Apple hardware from USB. From there you can write a replacement boot loader to LBA 0. The one I'm thinking of is Fedora 17. The Live CD can be written directly to a USB stick using dd on OS X. Once booted, the CD should contain a suitable mbr replacement in the syslinux folder (it is on the Fedora 18 final test candidate I'm testing now); all this bootloader does is tell the CPU to jump to the first sector of whatever partition is flagged as bootable in the MBR. That's it. And that's all you need it to do. Once it's jumped from LBA 0 to your Windows partition the computer should boot just like it does your VM. In theory. If not, the nice thing about a LiveCD is that you have full internet access, and can download other files including a real microsoft LBA 0 boot loader for that first sector. But seriously, it's a tiny bit of code, only 440 bytes. So if it works, it's completely unused after that and can't cause further problem down the line. It's purely jump code.

1 20 21 22 23 24 Previous Next