repairing bootcamp after creating new partition

Question

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&#x27;t know if the command line "sugo" utility and syntax  that I&#x27;ve seen in postings here applies to all such situations but if anyone can guide me through it I would be very grateful.  Thanks

Loner T · Answer

Please post the output of1. diskutil list2. diskutil cs list3. sudo gpt -vv -r show /dev/BootcampDiskWithoutSlice (where BootcampDiskWithoutSlice is of the form disk0 and is visible from the output of 1.)4. sudo fdisk /dev/BootcampDiskWithoutSlice5. sudo dd if&#x3D;/dev/rBootcampDisk count&#x3D;1 2&gt;/dev/null | hexdump -C (where BootcampDisk is of the form disk0s4 and is visible from the output of 1. Please note the &#x27;r&#x27; preceding the disk0s4 format)

Disco Dave D · Answer

Thanks.  Here you go.   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            852.2 GB   disk0s2   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s6   4:       Microsoft Basic Data Windows D               22.8 GB    disk0s7   5:       Microsoft Basic Data BOOTCAMP                124.3 GB   disk0s4diskutil cs listNo CoreStorage logical volume groups foundsudo gpt -vv -r show disk0gpt show: disk0: mediasize&#x3D;1000204886016; sectorsize&#x3D;512; blocks&#x3D;1953525168gpt show: disk0: Suspicious MBR at sector 0gpt show: disk0: Pri GPT at sector 1gpt show: 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  1664355600      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC  1664765240     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC  1666034776         936           1666035712    44627968      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7  1710663680   242860032      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7  1953523712        1423           1953525135          32         Sec GPT table  1953525167           1         Sec GPT header

Loner T · Answer

Please restart your Mac (the holes in disk0s2, s4, s6, s7 indicate repartitioning and deletions).3,4 and 5 will be as it stands now (before the reboot).3. sudo gpt -vv -r show /dev/disk0s44. sudo fdisk /dev/disk0s45. sudo dd if&#x3D;/dev/rdisk0s4 count&#x3D;1 2&gt;/dev/null | hexdump -C

Disco Dave D · Answer

will do

Loner T · Answer

If you reboot, please use the disk0s"n" that you get from a new diskutil list.

Disco Dave D · Answer

I tried before rebooting but was getting error messages as per the below and now will try again after rebooting.  sudo gpt -vv -r show /dev/disk0s4gpt show: unable to open device &#x27;/dev/disk0s4&#x27;: No such file or directorysudo fdisk /dev/disk0s4fdisk: /dev/disk0s4: Resource busy

Disco Dave D · Answer

Please see the error below for step 3 and a re-run of step 1. 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            852.2 GB   disk0s2   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3   4:       Microsoft Basic Data Windows D               22.8 GB    disk0s4   5:       Microsoft Basic Data BOOTCAMP                124.3 GB   disk0s5sudo gpt -vv -r show /dev/disk0s5gpt show: unable to open device &#x27;/dev/disk0s5&#x27;: No such file or directory

Loner T · Answer

Bad cut-paste. 😟1. sudo gpt -vv -r show /dev/disk02. sudo fdisk /dev/disk03. sudo dd if&#x3D;/dev/rdisk0s5 count&#x3D;1 2&gt;/dev/null | hexdump -C

Disco Dave D · Answer

No worries.  Here you go.  I&#x27;m glad you can interpret this stuff.sudo gpt -vv -r show /dev/disk0gpt show: /dev/disk0: mediasize&#x3D;1000204886016; sectorsize&#x3D;512; blocks&#x3D;1953525168gpt show: /dev/disk0: Suspicious MBR at sector 0gpt show: /dev/disk0: Pri GPT at sector 1gpt 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  1664355600      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC  1664765240     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC  1666034776         936           1666035712    44627968      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7  1710663680   242860032      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7  1953523712        1423           1953525135          32         Sec GPT table  1953525167           1         Sec GPT headersudo fdisk /dev/disk0Disk: /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] &lt;Unknown ID&gt; 2: AF 1023 254  63 - 1023 254  63 [    409640 - 1664355600] HFS+         3: AB 1023 254  63 - 1023 254  63 [1664765240 -    1269536] Darwin Boot  4: 07 1023 254  63 - 1023 254  63 [1666035712 -   44627968] HPFS/QNX/AUXsudo dd if&#x3D;/dev/rdisk0s5 count&#x3D;1 2&gt;/dev/null | hexdump -C00000000  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.&gt;..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&#x60;.|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  |..............&lt;.|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

Loner T · Answer

Please download GPT Fdisk. (http://sourceforge.net/projects/gptfdisk/).

Disco Dave D · Answer

Will do.  Are there any risks to the fix or other impacts that would be good to know?

Loner T · Answer

As long as only the MBR is manipulated, it should not cause any data issues. Your NTFS Volume Header is intact, which is a good sign.What year/model is the Mac? There may be other options, if you have a 2013 Mac. Caveat is that this configuration is very fragile. The disk should not be partitioned either on Windows or OSX side, which will break this setup. A software upgrade of OSX may also break this setup.

Disco Dave D · Answer

Thanks.  I&#x27;ve downloaded the program.  My Mac is a mid-2011 vintage.  So if my MAC updates the OS at some point as part of the normal course OS software upgrades that happen from time to time BOOTCAMP may no longer work again?

Loner T · Answer

Bootcamp standard configuration on older Macs cannot support an additional partition for sharing data. The GDisk utility can create a new MBR to work around that limitation, but that has implications for recovery and space. Disk Utility can cause problems, or Windows can cause problems. It is very fragile.

Disco Dave D · Answer

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&#x27;t seem worth the difficulty and potential future problems.   Thanks