You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Yosemite Upgrade Broke Bootcamp

Upgraded to Yosemite and now when I ALT Boot Windows 7 and Recovery partitions no longer show up. Using information from other threads I managed to get my Windows 7 partition to show up but when I select it I receive an ERROR READING DISK message. Is there any way to get this fixed?


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 647.3 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data 61.0 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Mac HD *647.0 GB disk1

Logical Volume on disk0s2

EE76C469-0C14-4592-986A-81FA25FAAF17

Unencrypted

diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group 02310D8F-058E-4CCF-8B7F-DAAED96FD1EF

=========================================================

Name: Mac HD

Status: Online

Size: 647348539392 B (647.3 GB)

Free Space: 18927616 B (18.9 MB)

|

+-< Physical Volume 0ABB2748-5135-4046-ACBB-5768C422F26B

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 647348539392 B (647.3 GB)

|

+-> Logical Volume Family 067A450C-844D-4465-8F8B-3DF65E5E2FF9

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

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

|

+-> Logical Volume EE76C469-0C14-4592-986A-81FA25FAAF17

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

Disk: disk1

Status: Online

Size (Total): 646977290240 B (647.0 GB)

Conversion Progress: -none-

Revertible: Yes (no decryption required)

LV Name: Mac HD

Volume Name: Mac HD

Content Hint: Apple_HFS

sudo gpt -vv -r show /dev/disk0

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

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

1266031792 79977296

1346009088 119138304 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1465147392 1743

1465149135 32 Sec GPT table

1465149167 1 Sec GPT header

sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 91201/255/63 [1465149168 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 - 1264352616] HFS+

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

*4: 0C 1023 254 63 - 1023 254 63 [1346009088 - 119138304] Win95 FAT32L

Macbook Pro, Mac OS X (10.5.5)

Posted on Oct 22, 2014 5:54 PM

Reply
69 replies

Oct 22, 2014 6:48 PM in response to fhornedo

You seem to have the same issue. I am glad the bug is consistent, so I know how to solve it. 😉


One more test to confirm that it is the same issue, please post the output of sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C.


Then gap between GPT#3 and GPT#4 is where your NTFS header is most likely to be. Once you post the output, if you are comfortable I can point you to a thread which solves the same problem, if you are comfortable with some Terminal gymnastics and Testdisk and GPT Fdisk.

Oct 22, 2014 7:37 PM in response to Loner T

Here are those results:


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 78 3a 50 |........?....x:P|

00000020 00 00 00 00 80 00 80 00 ff e7 19 07 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 25 25 e3 7c 43 e3 7c 8e |........%%.|C.|.|

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

Oct 22, 2014 7:49 PM in response to fhornedo

Try the simple first step first to see if it works.


sudo fdisk -e /dev/disk0

setpid 4

07

flag 4

p

w

y


Reboot.


Test 1 - Can you see Bootcamp Volume in Finder?

Test 2 - Can you files in the Bootcamp Volume?

Test 3 - Can you select Bootcamp in System Preferences -> Startup Disk.

Test 4 - If Test1,2,3 succeed, select Bootcamp and click Restart. Does Windows come up?


If it does not, the NTFS header you found using dd is bogus.


This thread has gone through the same issue - bootcamp not working after yosemite install.


If you are uncomfortable using it, I can explain the steps individually to start the rebuild process.

Oct 22, 2014 8:35 PM in response to fhornedo

1. Please post the output of sudo fdisk /dev/disk0.

2. Are you saying the previous steps did not work in OSX Terminal, or you executed them and still cannot see any change?

3. If the steps were executed successfully, but no change happened for Windows, then the linked article is where you should start. Are the steps in the linked article where you are running into an issue?

Oct 23, 2014 2:41 PM in response to Loner T

1. Please post the output of sudo fdisk /dev/disk0.


Disk: /dev/disk0 geometry: 91201/255/63 [1465149168 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 - 1264352616] HFS+

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

*4: 07 1023 254 63 - 1023 254 63 [1346009088 - 119138304] HPFS/QNX/AUX


2. Are you saying the previous steps did not work in OSX Terminal, or you executed them and still cannot see any change?


Correct I executed them then after rebooting I still did not see any change


3. If the steps were executed successfully, but no change happened for Windows, then the linked article is where you should start. Are the steps in the linked article where you are running into an issue?


I will look at this one again...I got a bit lost trying to sort through the first time

Oct 23, 2014 3:03 PM in response to fhornedo

1. Do you have any third-party NTFS drivers like Paragon, Tuxera or NTFS-3g/NTFSfree on the OSX side?

2. If #1 is false, if you notice the gap between GPT#3 and #4 is where your correct NTFS header is sitting.

3. Testdisk scans the disk sector-by-sector (when using Deeper Search) and finds such headers. It has the ability to look for files within such partitions.

4. Once you locate a deleted NTFS partition that looks familiar, the current GPT#4 is modified (deleted/added with correct start/end disk sectors), the Hybrid MBR is recreated, and then tested to verify that Windows comes up.

Oct 23, 2014 3:12 PM in response to fhornedo

Notice the start/end/size of the Test Bootcamp line and compares it, first to the Fdisk entry #4 and then the gap between GPT#3 and GPT#4. This is indeed very helpful.


MBR


*4: 07 1023 254 63 - 1023 254 63 [1346009088 - 119138304] HPFS/QNX/AUX


GPT...


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

1266031792 79977296

1346009088 119138304 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7


If you type "P", do you see any familiar files?

Yosemite Upgrade Broke Bootcamp

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.