Disco Dave D
Level 1 (1 points)

Q: repairing bootcamp after creating new partition

Like others who have posted here, I had two partitions, MacOS and Bootcamp that worked just fine.  I then added a new partition because I need a "D" drive in Windows configuration to be able to install a particular set of programs that rely on such a configuration (long story and perhaps there was a better way).  Once I added the new NTFS partition and rebooted, I no longer see the Windows drive as a a boot option.  I don't know if the command line "sugo" utility and syntax  that I've seen in postings here applies to all such situations but if anyone can guide me through it I would be very grateful.  Thanks

iMac, Mac OS X (10.7.5), Windows 7

Posted on Oct 1, 2014 1:47 PM

by Loner T,Solvedanswer
Loner T Loner T
Level 7 (24,862 points)
Safari
A:

Fantastic. (no need for GDisk - yet).

 

sudo fdisk -e /dev/disk0

setpid 4

07

flag 4

p

w

y

 

Now reboot.

 

1. Test 1 - Make sure there is a Bootcamp volume in Finder.

2. Test 2 - Make sure you can see files in the Bootcamp volume.

3. Test 3 - Make sure you can see Bootcamp in System Preferences -> Startup Disk.

4. If Test 3 works, select Bootcamp. and click on Restart.

 

If you see a hanging cursor in top left corner, you need Windows Startup Repair.

 

If Windows boots successfully, you are back in business.

Posted on Oct 1, 2014 5:54 PM

Close
Disco Dave D

Q: repairing bootcamp after creating new partition

  • All replies
  • Helpful answers

Previous Page 2

  • by Disco Dave D,

    Disco Dave D Disco Dave D Oct 1, 2014 4:48 PM in response to Loner T
    Level 1 (1 points)
    Oct 1, 2014 4:48 PM in response to Loner T

    Ok.  Thanks.  Is there a simple way to effetively undo the added partition and get back to 2 partitions with Bootcamp working as it was before? 

     

    Assuming that can be done do you happened to know if setting up a diskimage file in windows on the bootcamp drive is a way to get what I need which is a D drive in Windows and avoid the added partition which seems potentially unstable and problematic?

     

    I know this is heading in a different direction but getting a new D drive partition doesn't seem worth the difficulty and potential future problems.   Thanks

  • by Loner T,

    Loner T Loner T Oct 1, 2014 4:54 PM in response to Disco Dave D
    Level 7 (24,862 points)
    Safari
    Oct 1, 2014 4:54 PM in response to Disco Dave D

    If you can use an external drive instead of partitioning the OSX/Windows-via-BC route on older Macs, it would be the safest. If you deleted your Windows D, you may still need startup repair.

  • by Disco Dave D,

    Disco Dave D Disco Dave D Oct 1, 2014 5:24 PM in response to Loner T
    Level 1 (1 points)
    Oct 1, 2014 5:24 PM in response to Loner T

    I had actually tried to reverse it before posting and indeed I was not able to boot in Windows and will need startup repair.  I'll go that route and repost the output per your 5 steps.

  • by Loner T,

    Loner T Loner T Oct 1, 2014 5:42 PM in response to Disco Dave D
    Level 7 (24,862 points)
    Safari
    Oct 1, 2014 5:42 PM in response to Disco Dave D

    The NTFS header being intact may help in a short cut, but you may lose a bit of disk space.

     

    From GPT (you ran the dd command and found NTFS).

     

    1710663680   242860032      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

     

    From FDisk

     

    4: 07 1023 254  63 - 1023 254  63 [1666035712 -   44627968] HPFS/QNX/AUX


    The start/size in GPT 5 mismatch the star/end in MBR 4. You can remove the Win D partition, reboot.


    Now you can use Gdisk to create a Hybrid MBR using 2,3,4 (since 5 will move up to 4 in GPT). You can verify using the dd command but use rdisk0s4 instead of rdisk0s5 and you should still see the first line of "R.NTFS".


    Please post back, if you need detailed steps for the GDisk steps.


  • by Disco Dave D,

    Disco Dave D Disco Dave D Oct 1, 2014 5:44 PM in response to Loner T
    Level 1 (1 points)
    Oct 1, 2014 5:44 PM in response to Loner T

    OK.  3rd partition deleted.  new info runs below

     

    diskutil list

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk0

       1:                        EFI                         209.7 MB   disk0s1

       2:                  Apple_HFS Macintosh HD            875.0 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

       4:       Microsoft Basic Data BOOTCAMP                124.3 GB   disk0s4

     

     

    sudo gpt -vv -r show /dev/disk0

    gpt show: /dev/disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168

    gpt show: /dev/disk0: Suspicious MBR at sector 0

    gpt show: /dev/disk0: Pri GPT at sector 1

    gpt show: /dev/disk0: Sec GPT at sector 1953525167

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

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

      1710663544         136        

      1710663680   242860032      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1953523712        1423        

      1953525135          32         Sec GPT table

      1953525167           1         Sec GPT header

     

     

    sudo fdisk /dev/disk0

    Disk: /dev/disk0    geometry: 121601/255/63 [1953525168 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 - 1708984368] HFS+       

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

    4: 0C 1023 254  63 - 1023 254  63 [1710663680 -  242860032] Win95 FAT32L

     

     

     

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

    00000000  eb 52 90 4e 54 46 53 20  20 20 20 00 02 08 00 00  |.R.NTFS    .....|

    00000010  00 00 00 00 00 f8 00 00  3f 00 ff 00 00 a8 f6 65  |........?......e|

    00000020  00 00 00 00 80 00 80 00  ff bf 79 0e 00 00 00 00  |..........y.....|

    00000030  00 00 0c 00 00 00 00 00  02 00 00 00 00 00 00 00  |................|

    00000040  f6 00 00 00 01 00 00 00  9a b9 e6 6e d8 e6 6e 0c  |...........n..n.|

    00000050  00 00 00 00 fa 33 c0 8e  d0 bc 00 7c fb 68 c0 07  |.....3.....|.h..|

    00000060  1f 1e 68 66 00 cb 88 16  0e 00 66 81 3e 03 00 4e  |..hf......f.>..N|

    00000070  54 46 53 75 15 b4 41 bb  aa 55 cd 13 72 0c 81 fb  |TFSu..A..U..r...|

    00000080  55 aa 75 06 f7 c1 01 00  75 03 e9 dd 00 1e 83 ec  |U.u.....u.......|

    00000090  18 68 1a 00 b4 48 8a 16  0e 00 8b f4 16 1f cd 13  |.h...H..........|

    000000a0  9f 83 c4 18 9e 58 1f 72  e1 3b 06 0b 00 75 db a3  |.....X.r.;...u..|

    000000b0  0f 00 c1 2e 0f 00 04 1e  5a 33 db b9 00 20 2b c8  |........Z3... +.|

    000000c0  66 ff 06 11 00 03 16 0f  00 8e c2 ff 06 16 00 e8  |f...............|

    000000d0  4b 00 2b c8 77 ef b8 00  bb cd 1a 66 23 c0 75 2d  |K.+.w......f#.u-|

    000000e0  66 81 fb 54 43 50 41 75  24 81 f9 02 01 72 1e 16  |f..TCPAu$....r..|

    000000f0  68 07 bb 16 68 70 0e 16  68 09 00 66 53 66 53 66  |h...hp..h..fSfSf|

    00000100  55 16 16 16 68 b8 01 66  61 0e 07 cd 1a 33 c0 bf  |U...h..fa....3..|

    00000110  28 10 b9 d8 0f fc f3 aa  e9 5f 01 90 90 66 60 1e  |(........_...f`.|

    00000120  06 66 a1 11 00 66 03 06  1c 00 1e 66 68 00 00 00  |.f...f.....fh...|

    00000130  00 66 50 06 53 68 01 00  68 10 00 b4 42 8a 16 0e  |.fP.Sh..h...B...|

    00000140  00 16 1f 8b f4 cd 13 66  59 5b 5a 66 59 66 59 1f  |.......fY[ZfYfY.|

    00000150  0f 82 16 00 66 ff 06 11  00 03 16 0f 00 8e c2 ff  |....f...........|

    00000160  0e 16 00 75 bc 07 1f 66  61 c3 a0 f8 01 e8 09 00  |...u...fa.......|

    00000170  a0 fb 01 e8 03 00 f4 eb  fd b4 01 8b f0 ac 3c 00  |..............<.|

    00000180  74 09 b4 0e bb 07 00 cd  10 eb f2 c3 0d 0a 41 20  |t.............A |

    00000190  64 69 73 6b 20 72 65 61  64 20 65 72 72 6f 72 20  |disk read error |

    000001a0  6f 63 63 75 72 72 65 64  00 0d 0a 42 4f 4f 54 4d  |occurred...BOOTM|

    000001b0  47 52 20 69 73 20 6d 69  73 73 69 6e 67 00 0d 0a  |GR is missing...|

    000001c0  42 4f 4f 54 4d 47 52 20  69 73 20 63 6f 6d 70 72  |BOOTMGR is compr|

    000001d0  65 73 73 65 64 00 0d 0a  50 72 65 73 73 20 43 74  |essed...Press Ct|

    000001e0  72 6c 2b 41 6c 74 2b 44  65 6c 20 74 6f 20 72 65  |rl+Alt+Del to re|

    000001f0  73 74 61 72 74 0d 0a 00  8c a9 be d6 00 00 55 aa  |start.........U.|

    00000200

  • by Disco Dave D,

    Disco Dave D Disco Dave D Oct 1, 2014 5:48 PM in response to Loner T
    Level 1 (1 points)
    Oct 1, 2014 5:48 PM in response to Loner T

    Thanks.  Yes your assistance with Gdisk would be very helpful.  Thanks

  • by Loner T,Solvedanswer

    Loner T Loner T Oct 1, 2014 5:54 PM in response to Disco Dave D
    Level 7 (24,862 points)
    Safari
    Oct 1, 2014 5:54 PM in response to Disco Dave D

    Fantastic. (no need for GDisk - yet).

     

    sudo fdisk -e /dev/disk0

    setpid 4

    07

    flag 4

    p

    w

    y

     

    Now reboot.

     

    1. Test 1 - Make sure there is a Bootcamp volume in Finder.

    2. Test 2 - Make sure you can see files in the Bootcamp volume.

    3. Test 3 - Make sure you can see Bootcamp in System Preferences -> Startup Disk.

    4. If Test 3 works, select Bootcamp. and click on Restart.

     

    If you see a hanging cursor in top left corner, you need Windows Startup Repair.

     

    If Windows boots successfully, you are back in business.

  • by Disco Dave D,

    Disco Dave D Disco Dave D Oct 1, 2014 5:56 PM in response to Loner T
    Level 1 (1 points)
    Oct 1, 2014 5:56 PM in response to Loner T

    got this on step 1

     

    sudo fdisk -e /dev/disk0

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

    Enter 'help' for information

    fdisk: 1>     

  • by Disco Dave D,

    Disco Dave D Disco Dave D Oct 1, 2014 6:08 PM in response to Loner T
    Level 1 (1 points)
    Oct 1, 2014 6:08 PM in response to Loner T

    Loner T - you my friend are a lifesaver.  I am back in business thanks to you.   Very much appreciated

     

    Dave

  • by Loner T,

    Loner T Loner T Oct 1, 2014 6:40 PM in response to Disco Dave D
    Level 7 (24,862 points)
    Safari
    Oct 1, 2014 6:40 PM in response to Disco Dave D

    Always forget to mention the i386 error message. Glad to see you back in business.

  • by Enzoerwin,

    Enzoerwin Enzoerwin Dec 25, 2014 11:30 AM in response to Loner T
    Level 1 (0 points)
    Dec 25, 2014 11:30 AM in response to Loner T

    Hi Loner T,

     

    I need your help to find/repair the  the bootcamp after resizing the partition of mac.

    Below are the details you need. I created a new thread as what is usually advisedMissing bootcamp after resizing the partition of mac

     

    Hope you can help me. Its my son's laptop and he needs it badly.:(

Previous Page 2