Bootcamp gone haywire after Yosemite update

Question

Level 1

0 points

Bootcamp gone haywire after Yosemite update

Hello

I recently updated my Macbook Pro to OS X Yosemite 10.10, and as a result, my bootcamp (Windows 7, 64-Home edition) is now gone.

I have tried to follow many of the discussions posted already but non seem to have a clear solution to my issue. I ve had no problem with Bootcamp before with the Lion and Maverick updates, but this time my guess is that the problem probably lies in the fact that I re-sized my partitions using a window software.

Basically the current situation is my Bootcamp no longer appears when I press Alt on start-up.

Upon checking my partition through Disk Utility, here is what I see:

So you see that not only Bootcamp is now changed into disk0s4, there is also a gap of hard drive space that is not used by either Mac or Windows.

I have tried the sudo MBR method but I always encounter errors despite I followed word for word on other discussions. I think they likely have a slight different situation than mine? Here is a sample of my Diskutil List: (I saw a guy with a fifth item listed as Basic Data Bootcamp, but I don't have that line...)

diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *750.2 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 450.0 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data 200.8 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD *449.6 GB disk1

Logical Volume on disk0s2

D642C513-A4DB-4E81-9E67-546F88021205

Unlocked Encrypted

Thank you in advance for replies.

MacBook Pro, OS X Yosemite (10.10)

Posted on Oct 20, 2014 3:29 PM

Reply

Answer 1

Andy TLW Author

Level 1

0 points

Oct 20, 2014 3:48 PM in response to Andy TLW

OK just read some more posts, so I am guessing I am one of those missing operating system all together?

Here is my

sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=750156374016; sectorsize=512; blocks=1465149168

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 1465149167

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 878906248 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

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

880585432 192353576

1072939008 392208384 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1465147392 1743

1465149135 32 Sec GPT table

1465149167 1 Sec GPT header

And here is

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 c0 f3 3f |........?......?|

00000020 00 00 00 00 80 00 80 00 ff 9f 60 17 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 a5 7a 8d d2 82 8d d2 02 |.........z......|

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 2

Loner T

Level 9

59,471 points

Oct 20, 2014 4:53 PM in response to Andy TLW

You are the second person today who has a NTFS header showing correctly, but still missing Bootcamp. Yosemite has bigger issues than just ML or Mavericks.

You are in a similar situation to Windows error loading after Yosemite upgrade . Can you take a look at this and see how far you can get before significant surgery may be requires. I suggest downloading and installing the Testdisk and GPT Fdisk to start the analysis and looking for the missing NTFS header which is somewhere between GPT#3 and GPT#4.

I am also tracking, a bit primitively though, here - Bootcamp and Yosemite upgrade - potential data loss warning

Reply

Answer 3

mldrum

Level 1

0 points

Oct 20, 2014 7:23 PM in response to Andy TLW

My system also showed this after the Yosemite install.

When I pressed option/alt at boot the only drive available was "Macintosh HD"

I was able to open the Yosemite Recovery partition by holding COMMAND and R at boot.

I then opened terminal and typed the following command:

diskutil coreStorage revert

Now my recovery partition is avaiable when holding option at boot and I'm assuming my MBR has been restored.

This should allow Windows bootcamp to boot again.

Reply

Answer 4

Andy TLW Author

Level 1

0 points

Oct 20, 2014 9:16 PM in response to mldrum

Hi Loner T: Thanks I will try to it now.

mldrum: Thanks for the share. I tried it but the recovery partition didn't show up for me. Back to the more complicated method.

Reply

Answer 5

Loner T

Level 9

59,471 points

Oct 21, 2014 5:48 AM in response to mldrum

You are confusing the OS X Recovery HD with a bootcamp partition. On a working Yosemite system this is what it looks like. You can see the Recovery HD and Bootcamp. OS X Recovery HD cannot recover Windows Bootcamp, because they are unaware of each other.

The current issue is that Yosemite moves partitions without understanding what it is doing and corrupts NTFS headers, Bootloader/manager for Windows, and can cause data loss.

Recovery HD is also used for FileVault2 encryption and Find My Mac.

diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *256.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 128.2 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 127.0 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS OSY-MBP13 *126.4 GB disk1

Logical Volume on disk0s2

8A0116D5-7E1E-44D8-B2A0-8D4E4D48298D

Unencrypted

Reply

Answer 6

Andy TLW Author

Level 1

0 points

Oct 22, 2014 6:27 PM in response to Loner T

Hello again.

I am still stuck on the Testdisk analyse phase, the process is very slow with ~1.5billion data to analyse on my 750GB system.

I think I have at least spent more than 15 hours on this screen, is this normal? Thanks

Reply

Answer 7

Loner T

Level 9

59,471 points

Oct 22, 2014 6:42 PM in response to Andy TLW

Can you post the image using an image sharing service like IMGUR? I cannot see the image.

Reply

Answer 8

Andy TLW Author

Level 1

0 points

Oct 22, 2014 6:46 PM in response to Loner T

Hey Loner

Hows this one?

http://i.imgur.com/Kc70EeX.png?1

Reply

Answer 9

Loner T

Level 9

59,471 points

Oct 22, 2014 6:51 PM in response to Andy TLW

Did you start Testdisk with sudo testdisk? If yes, for some posters, this took over 10+ hours, it is purely a factor of the size of the disk. It will read the disk sector by sector to look for lost headers. If it has been siting at 0% for a long time (which I suspect it is not, because it at least shows two entries), then my suggestion is to let it run an produce the list of entries.

Reply

Answer 10

Andy TLW Author

Level 1

0 points

Oct 22, 2014 6:58 PM in response to Loner T

Ok got it! Will patiently wait for this to goes through then.

And yes it has been sitting at 00% despite there are two entries posted.

Reply

Answer 11

Andy TLW Author

Level 1

0 points

Oct 25, 2014 3:41 PM in response to Loner T

Hello Loner

I have tried many scans with test disk for the past few days and none is working. I have done at least 5 scans (10hrs each) and I tried with both 6.14 and 7 versions. The progress of the scan always gets stuck at 56%, check the screenshot link. http://imgur.com/0lKSJPq

For each scan, once it gets stuck at 56%, the entire apple system is slowed down to a frozen state. For the last one, I waited for an hour and it still won't progress any further. Do you know what is the problem here? Thank you!

Reply

Answer 12

Loner T

Level 9

59,471 points

Oct 25, 2014 3:53 PM in response to Andy TLW

1. Was the partition re-sizing activity done just before the Yosemite upgrade?

2. The other problem I see is the "cylinder" 828473344 where Testdisk is stuck, lies within your OS X partition as it is currently sitting. This gap is very typical of a Yosemite problem - 880585432 192353576 .

3. Can you post the output of sudo disk /dev/disk0 ? If Yosemite did the "right" thing, then the simpler fix may just requires an update to the MBR.

Reply