Bootcamp partition missing after resizing primary partition

Question

Level 1

0 points

Bootcamp partition missing after resizing primary partition

I installed Windows on a 50gb bootcamp partition, and then found the partition was too small, so I used disk utility to resize the primary partition, and then resized the Windows partition within Windows. When I got back to OS X, it no longer lists BOOTCAMP as a partition in Disk Utility, and instead lists "disk0s3" and reports it's original 50gb size. Windows still boots fine, but it's wonky because OS X tools that access bootcamp, like Paragon Bootcamp Backup and VMware fusion can't interact with it at all and give a bunch of errors.

From what I understand, it seems that I can fix the problem by syncing my MBR with my GPT. But, other instructions diverge from my specific situation too fast to keep up with the terminal commands.

Can someone help?

sudo gpt -r -vv show disk0

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

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

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

1797284640 1248

1797285888 58583040 3

1855868928 97654784 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1953523712 1423

1953525135 32 Sec GPT table

1953525167 1 Sec GPT header

diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh SSD 920.0 GB disk0s2

3: Microsoft Basic Data 50.0 GB disk0s3

iMac 17" i7, Mac OS X (10.6.6)

Posted on Mar 2, 2015 10:53 AM

Reply

Answer 1

rkaufmann87

Level 10

140,472 points

Mar 2, 2015 11:07 AM in response to petruzzo

Please re-post in the Boot Camp (note correct spelling) forums. Chances are you did not use the correct tool for re-partitioning

Reply

Answer 2

Loner T

Level 9

59,471 points

Mar 2, 2015 1:07 PM in response to petruzzo

Resizing/re-partitioning for a BC/Windows installation is not allowed when using MBRs.

From Boot Camp 5.1: Frequently asked questions - Apple Support

Can I resize the Windows partition after installing Windows?

No. Back up your important files, then use Boot Camp Assistant to delete the old partition and create a new one.

Please post the output of

sudo fdisk /dev/disk0

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

Reply

Answer 3

petruzzo Author

Level 1

0 points

Mar 2, 2015 1:14 PM in response to Loner T

Thank you. I'll know better next time.

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 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>

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

*3: 07 1023 254 63 - 1023 254 63 [1797285888 - 156237824] HPFS/QNX/AUX

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

Primarykstation:~ William$ sudo dd if=/dev/rdisk0s3 count=1 2>/dev/null | hexdump -C

00000000 bc c8 10 51 e3 68 e3 68 28 98 02 00 00 00 00 00 |...Q.h.h(.......|

00000010 a6 03 00 00 ba 07 00 00 08 00 00 00 cc 04 00 00 |................|

00000020 bc 0a 14 00 02 a8 00 00 15 00 7f b4 04 47 53 02 |.............GS.|

00000030 1a 66 70 c4 29 d9 c4 36 dd 01 a7 c4 ea f6 a5 01 |.fp.)..6........|

00000040 7f 19 00 b4 04 47 53 02 1a 66 70 c4 29 d9 c4 36 |.....GS..fp.)..6|

00000050 dd 01 a7 c4 ea f6 a5 fe 00 01 04 40 01 4d 69 63 |...........@.Mic|

00000060 72 6f 73 6f 66 74 2d 57 69 6e 64 6f 77 73 2d 43 |rosoft-Windows-C|

00000070 6c 69 65 6e 74 2d 46 65 61 74 75 72 65 73 2d 50 |lient-Features-P|

00000080 61 63 6b 61 67 65 2d 41 75 74 6f 4d 65 72 67 65 |ackage-AutoMerge|

00000090 64 2d 6e 65 74 7e 33 31 62 66 33 38 35 36 61 64 |d-net~31bf3856ad|

000000a0 33 36 34 65 33 35 7e 61 6d 64 36 34 7e 7e 36 2e |364e35~amd64~~6.|

000000b0 33 2e 39 36 30 30 2e 31 36 33 38 34 2e 63 61 74 |3.9600.16384.cat|

000000c0 7c 15 00 7f b4 06 af 39 ce 20 04 ed c5 72 e4 d6 ||......9. ...r..|

000000d0 88 16 aa 97 60 b6 d3 83 01 7f 19 00 b4 06 af 39 |....`..........9|

000000e0 ce 20 04 ed c5 72 e4 d6 88 16 aa 97 60 b6 d3 83 |. ...r......`...|

000000f0 fe 00 01 04 40 01 4d 69 63 72 6f 73 6f 66 74 2d |....@.Microsoft-|

00000100 57 69 6e 64 6f 77 73 2d 43 6c 69 65 6e 74 2d 46 |Windows-Client-F|

00000110 65 61 74 75 72 65 73 2d 50 61 63 6b 61 67 65 2d |eatures-Package-|

00000120 41 75 74 6f 4d 65 72 67 65 64 2d 62 61 73 65 7e |AutoMerged-base~|

00000130 33 31 62 66 33 38 35 36 61 64 33 36 34 65 33 35 |31bf3856ad364e35|

00000140 7e 61 6d 64 36 34 7e 7e 36 2e 33 2e 39 36 30 30 |~amd64~~6.3.9600|

00000150 2e 31 36 33 38 34 2e 63 61 74 7c 15 00 7f b4 06 |.16384.cat|.....|

00000160 c5 22 c2 9c e2 08 14 8e 1d 4d a4 01 96 37 a7 93 |.".......M...7..|

00000170 76 0b 01 7f 19 00 b4 06 c5 22 c2 9c e2 08 14 8e |v........"......|

00000180 1d 4d a4 01 96 37 a7 93 76 0b fe 00 01 04 40 01 |.M...7..v.....@.|

00000190 4d 69 63 72 6f 73 6f 66 74 2d 57 69 6e 64 6f 77 |Microsoft-Window|

000001a0 73 2d 43 6c 69 65 6e 74 2d 46 65 61 74 75 72 65 |s-Client-Feature|

000001b0 73 2d 50 61 63 6b 61 67 65 2d 41 75 74 6f 4d 65 |s-Package-AutoMe|

000001c0 72 67 65 64 2d 62 61 73 65 7e 33 31 62 66 33 38 |rged-base~31bf38|

000001d0 35 36 61 64 33 36 34 65 33 35 7e 61 6d 64 36 34 |56ad364e35~amd64|

000001e0 7e 7e 36 2e 33 2e 39 36 30 30 2e 31 36 33 38 34 |~~6.3.9600.16384|

000001f0 2e 63 61 74 7c 15 00 7f b4 07 61 92 b7 36 c0 90 |.cat|.....a..6..|

00000200

Reply

Answer 4

Loner T

Level 9

59,471 points

Mar 2, 2015 1:31 PM in response to petruzzo

Your GPT has

1797285888 58583040 3

1855868928 97654784 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

Your MBR has

*3: 07 1023 254 63 - 1023 254 63 [1797285888 - 156237824] HPFS/QNX/AUX

Notice that the highlighted number in the MBR is not the same as the starting number of the GPT 3 entry. It belongs to the previous entry. The dd for rdisk0s3 uses the GPT entry and does not show the proper NTFS header either.

It is working correctly right now, because your MBR has the correct information, but the GPT does not. Can you download GPT Fdisk (http://sourceforge.net/projects/gptfdisk/) so that the GPT can be corrected. Your MBR should not be manipulated any further till the GPT is corrected. Please do not partition the disk in any way.

Reply

Answer 5

petruzzo Author

Level 1

0 points

Mar 2, 2015 1:42 PM in response to Loner T

Thank you. I have downloaded and installed gptfdisk, can you tell me how to proceed? Or which article to read?

Reply

Answer 6

Loner T

Level 9

59,471 points

Mar 2, 2015 4:02 PM in response to petruzzo

You need to use the following steps. If you see any error messages during the following steps, please stop and post back here with the error message. The following steps have values from your Fdisk output (and you can verify).

Rebuild GPT4 using start/end offsets

Sudo gdisk /dev/rdisk0

P (print the full list of parts)

D (delete)

4 (part 4)

N (new part)

4 (part 4)

1797285888 offset in bytes (start point for Bootcamp part)

+156237824 (Size offset as opposed to End offset)

0700 (Windows part type)

P (print list of all parts just to see what changes will be made)

W (Write the new GPT)

Y (Yes! really write the new GPT)

This will delete and re-write the GPT partition info for /dev/disk0s3.

Execute the following command again

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

The output should similar to the following (in my case it is rdisk0s4, because I have Recovery HD as GPT 3).

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 e8 71 56 |........?.....qV|

00000020 00 00 00 00 80 00 80 00 f8 f7 08 1e 00 00 00 00 |................|

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 13 32 6d 13 b7 bb b5 32 |.........2m....2|

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

Reply

Answer 7

petruzzo Author

Level 1

0 points

Mar 2, 2015 5:08 PM in response to Loner T

Thank you. I followed the instructions, however, at the part selection the range was only 1-3 and entering 4 returned an error.

GPT fdisk (gdisk) version 0.8.10

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Partition table scan:

MBR: hybrid

BSD: not present

APM: not present

GPT: present

Found valid GPT with hybrid MBR; using GPT.

Command (? for help): p

Disk /dev/rdisk0: 1953525168 sectors, 931.5 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): A9E7B232-0E71-4CB4-8D72-E994587689E5

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 1953525134

Partitions will be aligned on 8-sector boundaries

Total free space is 58585717 sectors (27.9 GiB)

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

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 1797284639 856.8 GiB AF00 Untitled 1

3 1855868928 1953523711 46.6 GiB 0700 BOOTCAMP

Command (? for help): d

Partition number (1-3): 4

Value out of range