1 67 68 69 70 71 Previous Next 1,371 Replies Latest reply: Jul 6, 2014 10:25 AM by Christopher Murphy Go to original post
  • 1,020. Re: Repairing Boot Camp after creating new partition
    Holvy Level 1 Level 1 (0 points)

    This just saved me so much time in my lab of 22 iMacs setup to dual boot.

     

    Thanks!

  • 1,021. Re: Repairing Boot Camp after creating new partition
    mamuller Level 1 Level 1 (0 points)

    Thanks a lot, I spent hours and hours on this issue and you gave me the only solution that works !

  • 1,022. Re: Repairing Boot Camp after creating new partition
    NakedPenguin Level 1 Level 1 (0 points)

    Hi Chris,

     

    Would you kindly have a look at this thread for me? Your help would be much appreciated.

     

    https://discussions.apple.com/thread/5860699

     

    Many thanks

  • 1,023. Re: Repairing Boot Camp after creating new partition
    kbajpai Level 1 Level 1 (0 points)

    Here is the complete step by step detailed article to achieve 2 windows partitions - http://macosxtricks.blogspot.com

  • 1,024. Re: Repairing Boot Camp after creating new partition
    WarthogARJ Level 1 Level 1 (0 points)

    Hi,

    I have a similar problem; Mavericks wouldn't startup in BootCamp since I upgraded from ML.

    I can run Windows 7 installed on it using Parallels Desktop OK though.

    But I want the option to bootup into BootCamp (some Windows software I have is resource intensive).

     

    I have MacBook Pro 2012 with SSD 969GB Crucial main drive, a 2nd HDD 1TB (installed in optical bay) and 16 GB RAM.

    Mavericks 10.9.1 upgraded from ML.

    I run Windows 7 using Parallels Desktop 9 from BootCamp.

     

    I tried to do the same fix that Christopher Murphy suggested using GDisk but it didn't work: I could not boot up at all afterwards; not even in Mac mode.

    Got a strange sort of empty flag.....

    I think I damaged my Mac partition table....sigh.

    I had to reformat my main SSD and re-install from my backups.

     

    I'm not blaming Christopher: obviously something was not suitable or I made a mistake.

    I am reasonably competent at using Terminal.

    I thought my case was the same as Scotch-Brawth's.

    Our maps looked almost identical.

     

    So after my crash I reformated my SSD and reloaded my Mac partition from a CarbonCopyClone backup (I had a choice of CCC or TimeMachine).

    And my BootCamp from a Winclone backup.

    I've done this in the past, and wasn't expecting problems.

     

    However after that I could not access Windows in BootCamp at all.

    Even just from Parallels Desktop.

    Remember the problem that I set out to fix was to try to bootup into BootCamp, but I had no problem running Windows with Parallels.

     

    Before my GDisk disaster:

    SSD 845 GB Mac start-up

    SSD-2 25 GB NTFS (empty)

    BootCamp 90 GB NTFS

     

    (I saved diskutil list and sudo gpt of my maps, but no point in posting these since I've reformated since that).

     

    After my GDisk disaster (self-inflicted I'm sure):

    (1) First set-up was the same as before: could not access Windows and couldn't see BootCamp as a Startup option

     

    (2) Simplified set-up I have now:

    SSD 870 GB Mac start-up

    BootCamp 90 GB NTFS

     

    As soon as I went to (2) I got the option to bootup into BootCamp on startup: so obviously my partition scheme before was part of the problem.

     

    This is what my system looks like now:

     

    Last login: Tue Feb  4 14:22:13 on console

    alans-mbp:~ arjarvis_mbp$ diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *960.2 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:                  Apple_HFS Mac_SSD                 869.9 GB   disk0s2

       3:                 Apple_Boot Recovery HD             784.2 MB   disk0s3

       4:       Microsoft Basic Data BOOTCAMP                89.3 GB    disk0s4

     

    alans-mbp:~ arjarvis_mbp$ sudo gpt -r -vv show disk0

    Password:

    gpt show: disk0: mediasize=960197124096; sectorsize=512; blocks=1875385008

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 1875385007

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

      1699341608     1531680      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

      1700873288         952        

      1700874240   174510080      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1875384320         655        

      1875384975          32         Sec GPT table

      1875385007           1         Sec GPT header

     

     

    alans-mbp:~ arjarvis_mbp$ sudo fdisk /dev/disk0

    Disk: /dev/disk0          geometry: 116737/255/63 [1875385008 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  31  20 [    409640 - 1698931968] HFS+       

    3: AB 1023  31  21 - 1023 118  44 [1699341608 -    1531680] Darwin Boot

    *4: BF 1023 133  52 - 1023  70   5 [1700874240 -  174510080] <Unknown ID>

     

     

    I now have the option on startup (Alt) to boot into Mac, Windows or Recovery.

    However Windows (BootCamp) just hangs in the Windows screen.

    It gets as far as the Microsoft windows start screen and then just stays there: I left it for several hours.

     

    Windows Bootcamp Hang.jpg

    When booted into Mac, the Mac side works fine, but Parallels cannot access the BootCamp Windows 7 anymore: same problem: gets to Windows start screen and just stays there.

    And my feeling is that it SHOULD hace run: after all I had what I thought was a good BootCamp backup using WinClone (I've tried three different versions of winclone backups, including one I KNOW is 100% good).

     

    I've been speaking with Parallels Support but so far no success.

     

    The problem is it's not obvious where the issue lies:

    Parallels

    Winclone

    Apple

    Microsoft

     

    In summary I have TWO linked problems:

    (1) I used to be able to access the BootCamp Windows 7 using Parallels for Mac Version 9 but it cannot now

    And I restored from very good backups.

    It SHOULD be able to do it: I was able to before I ran GDisk (and I did my backups BEFORE I did GDisk).

     

    (2) I would LIKE to be able to start-up in BootCamp.

    That's my main goal.

    But ever since Mavericks upgrade I've had problems.

    Some that might be self-inflicted though: I was trying to get fancy and add a 2nd Windows partition (which I've removed now)

    So maybe that's part of the reason I had BootCamp start-up issues.

     

    What I have now:

    - main SSD partitioned as per above maps

    - TimeMachine backups of system before and after my GDisk disaster

    - CarbonCopyClone backup of system after I restored it from damaging my Mac partition

    - Winclone backups: about six different ones (I know at least 1 of them works for 100% (the earliest one)

     

     

    Any ideas?

     

    I'm willing to be adventurous and run GPT fdisk again: I'd REALLY like to get the better of this!

     

    Alan Jarvis

  • 1,025. Re: Repairing Boot Camp after creating new partition
    WarthogARJ Level 1 Level 1 (0 points)

    Aha!!!

    I think I solved it.

    I tried a few different WinClone copies of my BootCamp and I got one to work.

    But there was some damage to Windows.

    I think because Parallels tried to access Windows but the config files were wrong and it just hung.

     

    So by dint of deleting the BootCamp patition and adding it again I managed to get a session that ran Windows enough to do a chkdsk.

     

    BootCampCheck.png
    And now I can access Windows via Parallels.
    I repaired it again with chkdsk /b and now I can access it OK.
    I am now going to defrag it and back it up some more before I try to bootup into bootCamp from Startup.
    I think I still have a dodgy partition scheme though: nothing has changed from the last time I ran gpt

    gpt show: disk0: mediasize=960197124096; sectorsize=512; blocks=1875385008

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 1875385007

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

      1699341608     1531680      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

      1700873288         952        

      1700874240   174510080      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1875384320         655        

      1875384975          32         Sec GPT table

      1875385007           1         Sec GPT header

    The phrase "suspicious MBR" does not look good!!
  • 1,026. Re: Repairing Boot Camp after creating new partition
    Loner T Level 1 Level 1 (90 points)

    Can you post the output of sudo fdisk /dev/disk0?

     

    In your previous post the 'id' column shows BF for the "*4" partition, but it should be '07' for Bootcamp to work.

     

    Parallels may not care about fdisk, because it already has pointer to the NTFS partition which has bootcamp.

     

    The "suspicious MBR" is expected because you have OSX and Bootcamp on the same disk. (You can read more about MBRs and GPTs here - http://www.rodsbooks.com/gdisk/hybrid.html )

  • 1,027. Re: Repairing Boot Camp after creating new partition
    WarthogARJ Level 1 Level 1 (0 points)

    Aha!

    I did not know that.

     

    Alans-MacBook-Pro:~ arjarvis_mbp$ sudo fdisk /dev/disk0

    Disk: /dev/disk0          geometry: 116737/255/63 [1875385008 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  31  20 [    409640 - 1698931968] HFS+       

    3: AB 1023  31  21 - 1023 118  44 [1699341608 -    1531680] Darwin Boot

    *4: BF 1023 133  52 - 1023  70   5 [1700874240 -  174510080] <Unknown ID>

  • 1,028. Re: Repairing Boot Camp after creating new partition
    Loner T Level 1 Level 1 (90 points)

    Please try the steps outlined here - https://discussions.apple.com/message/23681966#23681966

     

    This should change the 4th partition to '07'.

  • 1,029. Re: Repairing Boot Camp after creating new partition
    WarthogARJ Level 1 Level 1 (0 points)

    Dang and hot diggity razzlefrazzles!!

    I need to have TWO Terminal sessons going for this...excellent.

    Awesome.

     

    OK: I will make multiple backups of everything, put on my belt AND suspenders, and have a full pot of coffee ready.

    In the morning.

     

    Will send an Action Report back.

     

    Thanks for the help!

  • 1,030. Re: Repairing Boot Camp after creating new partition
    Loner T Level 1 Level 1 (90 points)

    WarthogARJ wrote:

     

    I need to have TWO Terminal sessons going for this...excellent.

    Awesome.

    The second terminal window was suggested if syntax or sub-commands for fdisk command were needed. It is really not necessary.

  • 1,031. Re: Repairing Boot Camp after creating new partition
    Joseph Fernandez Level 1 Level 1 (0 points)

    Can someone please help me with recovering my system? I can't see the windows boot at the launch screen, here's my relevant info. I'm not a big command line geek so if you could tell me exactly what to type in to fix this...

     

    anomaly:~ ape$ sudo gpt -r -vv show disk0

    gpt show: disk0: mediasize=1000555581440; sectorsize=512; blocks=1954210120

    gpt show: disk0: PMBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 1954210119

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

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

      1753632328         440        

      1753632768   200577024      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1954209792         295        

      1954210087          32         Sec GPT table

      1954210119           1         Sec GPT header

    anomaly:~ ape$ sudo fdisk /dev/disk0

    Disk: /dev/disk0          geometry: 121643/255/63 [1954210120 sectors]

    Signature: 0xAA55

             Starting       Ending

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

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

    1: EE 1023 254  63 - 1023 254  63 [         1 - 1954210119] <Unknown ID>

    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    

  • 1,032. Re: Repairing Boot Camp after creating new partition
    Loner T Level 1 Level 1 (90 points)

    May I suggest

     

    1. If you are inclined to follow steps at this link, you can try these... https://discussions.apple.com/message/24172151#24172151

     

    I would suggest running the following two non-destructive commands to ensure there is a backup of the current disk information available either in this thread or somewhere where you have access to it (if there are issues later).

     

    or

     

    2. Create a new thread, put a reference here, and post the output that you currently have in that thread

  • 1,033. Re: Repairing Boot Camp after creating new partition
    WarthogARJ Level 1 Level 1 (0 points)

    Hi Loner T,

    I read the threads you suggested as well as the link about hybrid MBR:

    http://www.rodsbooks.com/gdisk/hybrid.html

     

    Can I confirm the steps please? (and I'll be really anal-retentive about it: I've already made a mistake with fdisk once!)

    And I think this would be a useful procedure to have since it seems lots of people have this issue.

     

    (1) Backup everything (I use TimeMachine and CCC as well as WinClone)

     

    (2) Download gpt if required

    http://sourceforge.net/projects/gptfdisk/

     

    (3) Start Mac Terminal 

     

    (4) Run these two commands to check my partitions:

    And post results somewhere safe so I can be helped if problems (that's a clever idea):

     

    sudu fdisk /dev/disk0

    sudo gpt -r -vv show disk0

     

    Alans-MacBook-Pro:~ arjarvis_mbp$ sudo fdisk /dev/disk0

    Disk: /dev/disk0          geometry: 116737/255/63 [1875385008 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  31  20 [    409640 - 1698931968] HFS+       

    3: AB 1023  31  21 - 1023 118  44 [1699341608 -    1531680] Darwin Boot

    *4: BF 1023 133  52 - 1023  70   5 [1700874240 -  174510080] <Unknown ID>

    Alans-MacBook-Pro:~ arjarvis_mbp$ sudo gpt -r -vv show disk0

    gpt show: disk0: mediasize=960197124096; sectorsize=512; blocks=1875385008

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 1875385007

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

      1699341608     1531680      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

      1700873288         952        

      1700874240   174510080      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1875384320         655        

      1875384975          32         Sec GPT table

      1875385007           1         Sec GPT header

     

     

    (5) Based on this info, my 4th Partition (BootCamp) has the id "BF".

    It SHOULD be "07" in order for BootCamp to bootup on startup.

     

    So I need to run a series of fdisk commands to change that.

     

    (6) sudo fdisk -e /dev/rdisk0

    (which seems to return an error: I'm not sure why we are running it if it gives an error??)

     

    Alans-MacBook-Pro:~ arjarvis_mbp$ sudo fdisk -e /dev/rdisk0

    fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory

    Enter 'help' for information

    fdisk: 1>

     

    So is there a better command to run here?

    Is this just a way to get fdisk to start running?

     

    After this I'm a little bit confused.

    The thread you sent me has two DIFFERENT sequences of Terminal commands:

    https://discussions.apple.com/message/23681966#23681966#23681966

     

    Can you please confirm that these are correct?

     

    (7) From the last part of this post:

    setpid 4

    07

    write

    Y

    flag 4

    write

    Y

    print

    quit

     

    (8) Or from the more dertailed instructions to RamosWipout earlier in that post:

    help

    print

    setpid 4?

    07

    flag 4

    write

     

    I think (7) looks better. Correct?

     

    Then I think you tell your system to restart.

     

    (9) then you type in the following to check that it all worked:

    sudo fdisk /dev/rdisk0

     

    (10) And obviously check that your system DOES bootup into BootCamp at startup.

     

    So can you please confirm these steps?

    Especially if we should be using (7) or (8).

     

    The other less competent users like myself really appreciate the help of you guys in this!

     

    Alan Jarvis

  • 1,034. Re: Repairing Boot Camp after creating new partition
    Loner T Level 1 Level 1 (90 points)

    You can use Step 7. In step 6, the "-e" puts fdisk in prompt mode. The "1>" indicates that fdisk is working on partition 1 (by default). stepid command should change it "4>" or "*4>".

1 67 68 69 70 71 Previous Next