Bootcamp partition issue after Yosemite upgrade

Question

Level 1

0 points

Bootcamp partition issue after Yosemite upgrade

I've installed bootcamp on my mac. Later on I needed more space on my bootcamp partition and used some method to shrink the mac partition and increase the bootcamp partition. This method worked fine until I did a Yosemite upgrade today. Now I see that my bootcamp partition is gone and has reverted to it's original size. Below is a screenshot of disk utility and outputs of the commands wanted. I need help in recovering my bootcamp partition. Thank you very much.

diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *160.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 55.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data 78.0 GB disk0s4

diskutil cs list

No CoreStorage logical volume groups found

sudo gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=160041885696; sectorsize=512; blocks=312581808

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 312581807

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

107831512 1269544 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

109101056 51138560

160239616 152340480 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

312580096 1679

312581775 32 Sec GPT table

312581807 1 Sec GPT header

sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 0 0 2 - 1023 254 63 [ 1 - 160239615] <Unknown ID>

*2: 07 1023 254 63 - 1023 254 63 [ 160239616 - 152340480] 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

sudo dd if=/dev/rdisk0 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 e9 54 00 00 00 00 00 00 |em...c{..T......|

000001c0 02 00 ee fe ff ff 01 00 00 00 ff 0f 8d 09 80 fe |................|

000001d0 ff ff 07 fe ff ff 00 10 8d 09 00 88 14 09 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

MacBook Pro

Posted on Oct 18, 2014 1:06 PM

Reply

Answer 1

Loner T

Level 9

59,513 points

Oct 18, 2014 1:25 PM in response to leevsn

You have the same issue as some of the others which are tracked in Bootcamp and Yosemite upgrade - potential data loss warning

Please see "Missing Operating system_ " After installing Yosemite for next steps using Testdisk to look for searching for deleted partitions. Please post the output of the last command before Testdisk comes into the picture.

Do you recall the size of your OS X and Windows partitions before the upgrade?

You are roughly missing 27GB (160 - (55 + 78) ) which is the gap between GPT#3 and GPT#4.

The last command should be

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

Reply

Answer 2

leevsn Author

Level 1

0 points

Oct 18, 2014 1:22 PM in response to Loner T

I've included the updated output for the last command

00000000 57 ac 81 37 d5 fe 20 bc c8 1b 93 fe 7f eb 7d bf |W..7.. .......}.|

00000010 f9 eb fb 78 ab e6 4f 23 34 67 cc ff 00 98 57 14 |...x..O#4g....W.|

00000020 1c db cc b7 bf 64 8d bf 78 ff 00 e4 db 7f d4 4f |.....d..x......O|

00000030 fd 20 4b fe e4 22 55 17 78 de b7 9f 74 c8 96 35 |. K.."U.x...t..5|

00000040 55 b5 87 d6 6e 7c 78 f1 f4 a7 e1 fb 11 fe ef 84 |U...n|x.........|

00000050 a9 fd ec 52 c5 ff 00 2e 11 7f bc b8 aa c8 12 33 |...R...........3|

00000060 f9 95 2d c3 06 fd cd 9b 43 ca ac df 17 08 9f fd |..-.....C.......|

00000070 7e 7c e5 ff 00 75 4b 2c 9e af fd 2c 3d 5f f4 fc |~|...uK,...,=_..|

00000080 55 96 ff 00 a3 84 6e 2e cd 1b 2f 2e ab c7 8f 1f |U.....n.../.....|

00000090 b1 cf 87 a7 c3 83 ff 00 be bd 2f 4f fd d5 f5 5f |........../O..._|

000000a0 f7 15 2a ad de 1e 0c f3 48 65 3e 99 e5 23 14 66 |..*.....He>..#.f|

000000b0 93 97 3f b3 f6 f9 f3 f5 f8 27 ee a5 fa cc b7 3c |..?......'.....<|

000000c0 3f 7b fa 4b d2 bf 89 57 99 6b 7a cc f6 3e 8f 98 |?{.K...W.kz..>..|

000000d0 2d a1 1c b4 7d 42 cf 52 40 91 a3 28 8e 19 7e 2f |-...}B.R@..(..~/|

000000e0 ee 7d 38 fd 3f ab 3c b2 ff 00 a3 ff 00 ba bf 7b |.}8.?.<........{|

000000f0 17 fa 2f ab 2e 2a fa 03 f3 5a f2 e2 cb f2 e7 59 |../..*...Z.....Y|

00000100 7b 50 27 96 ea cd ac 2d 3d 05 ab 17 bd 64 b4 84 |{P'....-=....d..|

00000110 a0 43 56 6f df fe c2 7f c6 2e 1f 65 d5 4e ad a2 |.CVo.......e.N..|

00000120 b3 d3 ec a0 b1 8f 80 b4 b4 8a 38 23 40 aa bc 63 |..........8#@..c|

00000130 8e 2e 09 44 fb 28 9c 15 bf e2 bf 4f 9f fb ab d5 |...D.(.....O....|

00000140 96 25 55 ee a4 09 e9 2c 80 fb 53 96 e7 97 fc 1f |.%U....,..S.....|

00000150 db a7 fc 59 ea f0 ff 00 76 fa 49 70 aa c9 26 31 |...Y....v.Ip..&1|

00000160 38 d8 50 d3 e1 1e e2 9f 2f e7 fd af 4f e1 7f 8b |8.P...../...O...|

00000170 d2 f5 5e dd 55 49 26 01 e3 48 d4 f1 6d cd 0f 56 |..^.UI&..H..m..V|

00000180 ff 00 89 fe da 7f c2 ff 00 c5 51 4e aa 43 e6 76 |..........QN.C.v|

00000190 9a e7 5c f2 ad b7 a6 44 6f ac a4 a1 a9 fe f9 b2 |..\....Do.......|

000001a0 bb 9b c4 7f 27 fd 77 fb d8 ad d5 53 fc e2 d2 74 |....'.w....S...t|

000001b0 cd 47 ca 2d 26 a3 01 b8 b5 d2 ae ad 75 2b 98 83 |.G.-&.......u+..|

000001c0 88 ab 04 12 81 73 c9 f9 c5 c4 0b 56 b8 7f ef 62 |.....s.....V...b|

000001d0 ff 00 89 62 ab 7c bd f9 75 e5 2f 2f 6a 17 8f 6c |...b.|..u.//j..l|

000001e0 b3 49 6d 73 f5 74 16 b7 93 7d 6a dd 16 d6 45 96 |.Ims.t...}j...E.|

000001f0 16 5f 57 f7 84 c4 78 7a 52 dc 4b 2c 90 7c 11 45 |._W...xzR.K,.|.E|

00000200

Reply

Answer 3

Loner T

Level 9

59,513 points

Oct 18, 2014 1:53 PM in response to leevsn

Since the beginning of the Bootcamp partition does not have an NTFS header Bootcamp has stopped working.

These are the options...

1. Use Testdisk and look for deleted partitions as in "Missing Operating system_ " After installing Yosemite .

2. Short-cut #1 by assuming that the end of GPT#3+1 byte is where Bootcamp starts, in your specific case it is 109101056. Manipulate the GPT using GPT FDisk (http://sourceforge.net/projects/gptfdisk/) accordingly, and re-execute the 'dd' command. If a NTFS header exists, then make MBR changes and test.

3. If #2 does not work, fall back to #1.

4. Nuke-and-Pave and rebuild Windows from scratch, depending on your backup availability and tolerance for data loss.

Reply

Answer 4

leevsn Author

Level 1

0 points

Oct 18, 2014 1:41 PM in response to Loner T

Yes, I noticed the gap. I think the beginning of the gap is where my bootcamp partition should start. I was thinking of using some sort of tool to resize the bootcamp partition to fill the gap, but I'm unsure about the behaviour of the tool to do something like that. I've posted the updated output for the last command and I'm running through the steps of test disk now.

Reply

Answer 5

leevsn Author

Level 1

0 points

Oct 18, 2014 1:45 PM in response to Loner T

I have gdisk installed from reading the older threads. I was unsure how the tool and how partitioning behaved so I wasn't confident in implementing such a change since I was afraid of deleting any data. I'm going to try the shortcut you mentioned.

Reply

Answer 6

Loner T

Level 9

59,513 points

Oct 18, 2014 1:53 PM in response to leevsn

Please see Bootcamp missing after expanding partition for reference on deleting/adding GPT and re-creating a Hybrid MBR. If you get stuck somewhere, please post back on the current thread.

For your original question about resizing, from Boot Camp 5.1: Frequently asked questions

How can a Windows partition be resized after Windows is installed?

You need to delete the Windows partition using the Boot Camp Assistant, and start over to change the size of the Windows partition. Back up your important Windows files first.

Reply

Answer 7

leevsn Author

Level 1

0 points

Oct 18, 2014 2:20 PM in response to Loner T

I've implemented the changes you've suggested. The partition is readable now. Thank you.

The partition wasn't bootable so I created a hybrid mbr and added the partition to it and tried booting into window.

I now receive an error message indicating that windows can not boot due to not having access to a device. Is there a way to fix this error?

Thank you so much for helping restore access the partition again.

Reply

Answer 8

Loner T

Level 9

59,513 points

Oct 18, 2014 4:23 PM in response to leevsn

The BCD is corrupted. It needs to be rebuilt. W7 uses Bootrec.exe, W8+ requires using the Installation Media.

Reply