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

    Hello Christopher,

    i have the same problem but with small difference. I have Mac Book Pro late 2011

    1) Windows was installed before using Boot Camp and worked perfectly with Mac OS on my HDD.
    2) Then i updated my Mac OS to 10.8.2 and while upgrade installed it on SSD. Windows still worked OK.

    All old partitions were left on HDD that i put instead of CDROM.

    3) I felt the POWER of SSD and decided to change my HDD to SSD

    4) I copied partitions from HDD to SSD but without partition that have contained Old version of Mac OS.

    5) My Windows option from boot menu stoped to work because of number of partitions on new SSD.
    I tried different combinations of hybrid MBR using gdisk but nothing changed.
    In boot menu i have "Mac OS, Windows, Recovery HD"

    When i click Windows - i have "Missing operating system" message.
    Here is result of diskutil list

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

    /dev/disk0

       #:      TYPE NAME                                 SIZE           IDENTIFIER

       0:      GUID_partition_scheme               *256.1 GB   disk0

       1:      EFI                                                 209.7 MB   disk0s1

       2:      Apple_HFS Users                         195.7 GB    disk0s2

       3:      Microsoft Basic Data Windows 7    60.1 GB    disk0s3

    /dev/disk1

       #:      TYPE NAME                                 SIZE            IDENTIFIER

       0:      GUID_partition_scheme                *240.1 GB   disk1

       1:       EFI                                                 209.7 MB   disk1s1

       2:       Apple_HFS Mac OS                      239.2 GB   disk1s2

       3:       Apple_Boot Recovery HD             650.0 MB   disk1s3

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

    Can you please help me to fix this situation?

    Thank you,
    Alex

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

    Hello Christopher,

    I am Dearly looking forward to fixing this problem, Ive attempted to read as much as i can on what you have explained so far

     

    Just to clear it all up I have an Imac with 2x raid 0 ssd and a 2TB "data" disk  obviously i have no dvd drive

    My problem  is Ive tried and tried to install bootcamp Via a Winclone image i took from my macbook

     

    moved the image over to my IMAC installed it to a partition on the 2TB disk, as ive learned windows wont work with software raid...

    I have attempted to follow your posts on the first page to attempt to get my windows to boot, but it still wont

    How ever parallels can see it perfectly.

     

    P.S I can not for the life of me notice that when i reboot some times that my 2TB disk appears as disk0 and some times disk1 i assume its normal. I some how think this is the problem?

     

    "safe" partition is not required but it was just where i put my time machine backup.

     

    Before i write this post this is what i did to the mbr..

    ==========

    r <enter>        go to the recovery & transformation menu

    h <enter>        create a new hybrid MBR

    3 <enter>        add partion 3 to the MBR

    <enter>          accept the default MBR hex code of 07

    y <enter>        set the bootable flag

    n <enter>        do not protect more partitions

    o < enter>       print (display) the MBR

    ===========

    NOW:

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *2.0 TB     disk0

       1:                        EFI                         209.7 MB   disk0s1

       2:                  Apple_HFS Untitled 1              1.5 TB     disk0s2

       3:       Microsoft Basic Data BOOTCAMP                180.2 GB   disk0s3

       4:                  Apple_HFS safe                    353.2 GB   disk0s4

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *120.0 GB   disk1

       1:                        EFI                         209.7 MB   disk1s1

       2:                 Apple_RAID                         119.7 GB   disk1s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *120.0 GB   disk2

       1:                        EFI                         209.7 MB   disk2s1

       2:                 Apple_RAID                         119.7 GB   disk2s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk2s3

    /dev/disk3

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS MAC_OSX_LION           *239.4 GB   disk3

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

    Before Reboot:

    h-3.2# diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *120.0 GB   disk0

       1:                        EFI                         209.7 MB   disk0s1

       2:                 Apple_RAID                         119.7 GB   disk0s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *2.0 TB     disk1

       1:                        EFI                         209.7 MB   disk1s1

       2:                  Apple_HFS Untitled 1              1.5 TB     disk1s2

       3:       Microsoft Basic Data BOOTCAMP                180.2 GB   disk1s3

       4:                  Apple_HFS safe                    353.2 GB   disk1s4

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *120.0 GB   disk2

       1:                        EFI                         209.7 MB   disk2s1

       2:                 Apple_RAID                         119.7 GB   disk2s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk2s3

    /dev/disk3

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS MAC_OSX_LION           *239.4 GB   disk3

     

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

    sh-3.2# sudo gdisk /dev/disk0

    GPT fdisk (gdisk) version 0.8.5

     

    Partition table scan:

      MBR: hybrid

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with hybrid MBR; using GPT.

     

    Command (? for help): r

     

    Recovery/transformation command (? for help): o

     

    Disk size is 3907029168 sectors (1.8 TiB)

    MBR disk identifier: 0x00004A06

    MBR partitions:

     

    Number  Boot  Start Sector   End Sector   Status      Code

       1                     1       409639   primary     0xEE

       2                409640   2864961951   primary     0xAF

       3      *     2865225728   3217215487   primary     0x0C

       4            3217215488   3907029127   primary     0xAF

     

    Recovery/transformation command (? for help): p

    Disk /dev/disk0: 3907029168 sectors, 1.8 TiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 7E4EFAC0-0F27-43D9-B1AE-DC690095B4A7

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 3907029134

    Partitions will be aligned on 8-sector boundaries

    Total free space is 263789 sectors (128.8 MiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640      2864961951   1.3 TiB     AF00  Untitled 1

       3      2865225728      3217215487   167.8 GiB   0700  BOOTCAMP

       4      3217215488      3907029127   328.9 GiB   AF00  Apple_HFSX_Untitled_2

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

    sh-3.2# 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  2864552312      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

      2864961952      263776        

      2865225728   351989760      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      3217215488   689813640      4  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

      3907029128           7        

      3907029135          32         Sec GPT table

      3907029167           1         Sec GPT header

    sh-3.2#

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

    I need the results from these:

    sudo gpt -r -vv show disk0

    sudo fdisk /dev/disk0

    sudo gpt -r -vv show disk1

    sudo fdisk /dev/disk1


     

    Probably what's happened is you have a Windows boot loader on one disk, and don't have one on the other. Which disk is SSD and HDD?

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

    P.S I can not for the life of me notice that when i reboot some times that my 2TB disk appears as disk0 and some times disk1 i assume its normal. I some how think this is the problem?

     

    This is normal. And it's why you need to make sure you're using the correct indentifier after each reboot.

     

    So you bought Winclone, why aren't you getting support for this problem from them?

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

    Hello Christopher,

    right now both disks are SSD:

    Here are results:

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

    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 - 1023 254  63 [         1 -  382668799] <Unknown ID>

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

    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     

    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#

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

    Post the results for this:

    sudo dd if=/dev/disk0 count=1 2>/dev/null | hexdump -C

    sudo dd if=/dev/disk1 count=1 2>/dev/null | hexdump -C

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

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

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

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

    *

    000001c0  02 00 ee fe ff ff 01 00  00 00 ff 0f cf 16 80 fe  |................|

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

    000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 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  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  |................|

    *

    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

    sh-3.2#

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

    Yeah so disk1 has a boot loader and disk0 does not, but disk0 is what has Windows on it. And you need some MBR adjustments so this is what I'd do. I'm assuming you haven't rebooted since the last post, which can cause disk1 and disk0 to flip.

     

    1. Move boot loader from disk1 to disk0 then delete it from disk0. You really need to make sure you get count=1 in there or you'll experience data loss. Obviously you should have backups of important info already in case you have a spasm and hit return before you fully write out the whole line...might be better to copy paste.

     

    sudo dd if=/dev/rdisk1 of=/dev/rdisk0 bs=440 count=1

    sudo dd if=/dev/zero of=/dev/rdisk1 bs=440 count=1

     

    2. Using gdisk.

    For disk0 you should use gdisk's recovery menu to create a new hybrid MBR, and add partitions 2 3. It may avoid problems down the road, and is the way Apple arranges their hybrid MBRs. Make sure 3 is set as bootable.

     

    For disk1 you should use gdisk expert menu to create a new protective MBR. This will remove the hybrid MBR, which is no longer needed for this disk. This is the disk with only HFS+ volumes on it (OS X boot and Recovery HD).

     

    Then reboot.

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

    3. The BCD (for Windows) may contain incorrect information because Windows was moved from one disk to another. Follow this if it doesn't boot. I'd try /RebuildBcd first if you get a Bcd related error, or you get an error screen with a lot more than one line of error text (meaning it got past the first stage boot loader already).

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

    You asked which disk is ssd which is hhd

    you can see the 2 x 120 GB hhd ( raid )and the other 2TB drive?

    or do i need to show something else?

     

    to further what you mentioned

    when i boot and hold OPTION , I get MAC_OS_LION AND MAC_OS_LION_2  AND Windows....

    Booting either mac_os_lion or mac_os_lion_2 still boot my system as normal

    ======

    sh-3.2# diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *2.0 TB     disk0

       1:                        EFI                         209.7 MB   disk0s1

       2:                  Apple_HFS Untitled 1              1.5 TB     disk0s2

       3:       Microsoft Basic Data BOOTCAMP                180.2 GB   disk0s3

       4:                  Apple_HFS safe                    353.2 GB   disk0s4

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *120.0 GB   disk1

       1:                        EFI                         209.7 MB   disk1s1

       2:                 Apple_RAID                         119.7 GB   disk1s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *120.0 GB   disk2

       1:                        EFI                         209.7 MB   disk2s1

       2:                 Apple_RAID                         119.7 GB   disk2s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk2s3

    /dev/disk3

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS MAC_OSX_LION           *239.4 GB   disk3

    =======

     

     

     

    sh-3.2# 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  2864552312      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

      2864961952      263776        

      2865225728   351989760      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      3217215488   689813640      4  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

      3907029128           7        

      3907029135          32         Sec GPT table

      3907029167           1         Sec GPT header

    sh-3.2# 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    0   0   2 -   25 127  14 [         1 -     409639] GPT        

    2: AF   25 127  15 -  843  74  31 [    409640 - -1430414984] HFS+       

    *3: 0C  859 181  27 - 1010  15  29 [-1429741568 -  351989760] Win95 FAT32L

    4: AF 1010  15  30 -  940 248  20 [-1077751808 -  689813640] HFS+       

    sh-3.2#

    -==================

    sh-3.2# sudo gpt -r -vv show disk1

    gpt show: disk1: mediasize=120034123776; sectorsize=512; blocks=234441648

    gpt show: disk1: PMBR at sector 0

    gpt show: disk1: Pri GPT at sector 1

    gpt show: disk1: Sec GPT at sector 234441647

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

      234179464     262144      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

      234441608          7        

      234441615         32         Sec GPT table

      234441647          1         Sec GPT header

    sh-3.2# sudo fdisk /dev/disk1

    Disk: /dev/disk1    geometry: 14593/255/63 [234441648 sectors]

    Signature: 0xAA55

             Starting       Ending

    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]

    ------------------------------------------------------------------------

    1: EE 1023 254  63 - 1023 254  63 [         1 -  234441647] GPT        

    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     

    sh-3.2#

     

     

     

    And disk 2

    h-3.2# sudo gpt -r -vv show disk2

    gpt show: disk2: mediasize=120034123776; sectorsize=512; blocks=234441648

    gpt show: disk2: PMBR at sector 0

    gpt show: disk2: Pri GPT at sector 1

    gpt show: disk2: Sec GPT at sector 234441647

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

      234179464     262144      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

      234441608          7        

      234441615         32         Sec GPT table

      234441647          1         Sec GPT header

    sh-3.2# sudo fdisk /dev/disk2

    Disk: /dev/disk2    geometry: 14593/255/63 [234441648 sectors]

    Signature: 0xAA55

             Starting       Ending

    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]

    ------------------------------------------------------------------------

    1: EE 1023 254  63 - 1023 254  63 [         1 -  234441647] GPT        

    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     

    sh-3.2#

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

    @Coffeecoco

    You read the wrong response. There's a response for you and one for Alex Senkevich and it looks like you've got them mixed.

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

    Could you please assist me sir?

    I dont feel they are able to assist because my setup is so unique with the raid and all

    Is the reason why my BOOTCAMP wont boot due to the identifier ?

    All i get is a blackscreen when booting Windows 7

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

    The RAID has nothing to do with this, the Windows volume is on another disk entirely.

     

    This entry in the MBR appears to have an incorrect type ID, it should be 07:

    *3: 0C  859 181  27 - 1010  15  29 [-1429741568 -  351989760] Win95 FAT32L

     

    But I don't know if that's what's preventing it from booting or not. That can be fixed with gdisk by creating a new hybrid MBR from the recovery menu, and in your case you'll add partitions 2 3 4 and make 3 bootable. Then write out the new partition tables with the w command.

     

    You could also report the result from:

    sudo dd if=/dev/disk0 count=1 2>/dev/null | hexdump -C

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

     

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

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

    00000010  06 b9 00 02 fc f3 a4 50  68 1c 06 cb fb b9 04 00  |.......Ph.......|

    00000020  bd be 07 80 7e 00 00 7c  0b 0f 85 0e 01 83 c5 10  |....~..|........|

    00000030  e2 f1 cd 18 88 56 00 55  c6 46 11 05 c6 46 10 00  |.....V.U.F...F..|

    00000040  b4 41 bb aa 55 cd 13 5d  72 0f 81 fb 55 aa 75 09  |.A..U..]r...U.u.|

    00000050  f7 c1 01 00 74 03 fe 46  10 66 60 80 7e 10 00 74  |....t..F.f`.~..t|

    00000060  26 66 68 00 00 00 00 66  ff 76 08 68 00 00 68 00  |&fh....f.v.h..h.|

    00000070  7c 68 01 00 68 10 00 b4  42 8a 56 00 8b f4 cd 13  ||h..h...B.V.....|

    00000080  9f 83 c4 10 9e eb 14 b8  01 02 bb 00 7c 8a 56 00  |............|.V.|

    00000090  8a 76 01 8a 4e 02 8a 6e  03 cd 13 66 61 73 1c fe  |.v..N..n...fas..|

    000000a0  4e 11 75 0c 80 7e 00 80  0f 84 8a 00 b2 80 eb 84  |N.u..~..........|

    000000b0  55 32 e4 8a 56 00 cd 13  5d eb 9e 81 3e fe 7d 55  |U2..V...]...>.}U|

    000000c0  aa 75 6e ff 76 00 e8 8d  00 75 17 fa b0 d1 e6 64  |.un.v....u.....d|

    000000d0  e8 83 00 b0 df e6 60 e8  7c 00 b0 ff e6 64 e8 75  |......`.|....d.u|

    000000e0  00 fb b8 00 bb cd 1a 66  23 c0 75 3b 66 81 fb 54  |.......f#.u;f..T|

    000000f0  43 50 41 75 32 81 f9 02  01 72 2c 66 68 07 bb 00  |CPAu2....r,fh...|

    00000100  00 66 68 00 02 00 00 66  68 08 00 00 00 66 53 66  |.fh....fh....fSf|

    00000110  53 66 55 66 68 00 00 00  00 66 68 00 7c 00 00 66  |SfUfh....fh.|..f|

    00000120  61 68 00 00 07 cd 1a 5a  32 f6 ea 00 7c 00 00 cd  |ah.....Z2...|...|

    00000130  18 a0 b7 07 eb 08 a0 b6  07 eb 03 a0 b5 07 32 e4  |..............2.|

    00000140  05 00 07 8b f0 ac 3c 00  74 09 bb 07 00 b4 0e cd  |......<.t.......|

    00000150  10 eb f2 f4 eb fd 2b c9  e4 64 eb 00 24 02 e0 f8  |......+..d..$...|

    00000160  24 02 c3 49 6e 76 61 6c  69 64 20 70 61 72 74 69  |$..Invalid parti|

    00000170  74 69 6f 6e 20 74 61 62  6c 65 00 45 72 72 6f 72  |tion table.Error|

    00000180  20 6c 6f 61 64 69 6e 67  20 6f 70 65 72 61 74 69  | loading operati|

    00000190  6e 67 20 73 79 73 74 65  6d 00 4d 69 73 73 69 6e  |ng system.Missin|

    000001a0  67 20 6f 70 65 72 61 74  69 6e 67 20 73 79 73 74  |g operating syst|

    000001b0  65 6d 00 00 00 63 7b 9a  06 4a 00 00 00 00 00 00  |em...c{..J......|

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

    000001d0  0f 19 af 4a df 4b 28 40  06 00 78 99 bd aa 80 b5  |...J.K(@..x.....|

    000001e0  db 5b 0c 0f dd f2 00 e0  c7 aa 00 f0 fa 14 00 0f  |.[..............|

    000001f0  de f2 af f8 d4 ac 00 d0  c2 bf 88 b8 1d 29 55 aa  |.............)U.|

    00000200

    sh-3.2#

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

    I did as you said now please view the changes

    Recovery/transformation command (? for help): p

    Disk /dev/disk0: 3907029168 sectors, 1.8 TiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 7E4EFAC0-0F27-43D9-B1AE-DC690095B4A7

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 3907029134

    Partitions will be aligned on 8-sector boundaries

    Total free space is 263789 sectors (128.8 MiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640      2864961951   1.3 TiB     AF00  Untitled 1

       3      2865225728      3217215487   167.8 GiB   0700  BOOTCAMP

       4      3217215488      3907029127   328.9 GiB   AF00  Apple_HFSX_Untitled_2

     

    Recovery/transformation command (? for help): o

     

    Disk size is 3907029168 sectors (1.8 TiB)

    MBR disk identifier: 0x00004A06

    MBR partitions:

     

    Number  Boot  Start Sector   End Sector   Status      Code

       1                     1       409639   primary     0xEE

       2                409640   2864961951   primary     0xAF

       3      *     2865225728   3217215487   primary     0x07

       4            3217215488   3907029127   primary     0xAF

     

    Recovery/transformation command (? for help):

     

    sh-3.2# 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    0   0   2 -   25 127  14 [         1 -     409639] GPT        

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

    *3: 07 1023 254  63 - 1023 254  63 [-1429741568 -  351989760] NTFS       

    4: AF 1023 254  63 - 1023 254  63 [-1077751808 -  689813640] HFS+       

    sh-3.2#

     

    P.S i spoke to wineclone support they told me apple dont support my setup ( dvd drive missing ) and they cant support what i have done they requested that i re install the DVD drive.

1 19 20 21 22 23 Previous Next