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

After update to Yosemite, Windows won't start

Yes, the Yosemite update crippled my Bootcamp partition too. Unfortunately I stumled upon Bootcamp and Yosemite upgrade - potential data loss warning too late to read the warnings...


I’ve a Macbook Pro (early 2011) that runs Windows 7 most of the time. Four years without problems - the Macbook is the best Windows computer ever!


After I experienced some hard to trace Windows crashes in the past days, I thought it was a good idea to start the computer in OS X and check for updates. One of them was Yosemite and as the other updates went smooth, I thought Yosemite would be be a piece of cake too. An error message appeared while installing (something about MBR I think) and now I can only start in OS X, although the Windows partition is still there.


I have read some good tips from the uber-fixer Loner T in Bootcamp and Yosemite upgrade - potential data loss warning, so here is the output from the commands. I hope there is some advice for my disk too :-)


diskutil list:

—————————

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *512.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macbook 56.0 GB disk0s2

3: Microsoft Basic Data 455.8 GB disk0s3



diskutil cs list:

—————————————————

No CoreStorage logical volume groups found



sudo gpt -vv -r show /dev/disk0:

——————————————————————————————

gpt show: /dev/disk0: mediasize=512110190592; sectorsize=512; blocks=1000215216

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 1000215215

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

109784640 262592

110047232 890167296 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1000214528 655

1000215183 32 Sec GPT table

1000215215 1 Sec GPT header



sudo fdisk /dev/disk0:

————————————————————

gpt show: /dev/disk0: mediasize=512110190592; sectorsize=512; blocks=1000215216

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 1000215215

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

109784640 262592

110047232 890167296 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1000214528 655

1000215183 32 Sec GPT table

1000215215 1 Sec GPT header

MBPvanCristophe:~ Christophe$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 62260/255/63 [1000215216 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>

2: AF 1023 254 63 - 1023 254 63 [ 409640 - 109375000] HFS+

3: 0C 1023 254 63 - 1023 254 63 [ 110047232 - 890167296] Win95 FAT32L

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

MacBook Pro, OS X Yosemite (10.10.4)

Posted on Jul 28, 2015 9:41 AM

Reply
28 replies

Aug 7, 2015 8:22 AM in response to Loner T

Hi Loner T, here are the results:



MS Data 135134908 401260219 266125312


Can't open filesystem. Filesystem seems damaged.


MS Data 214470963 480596274 266125312


Can't open filesystem. Filesystem seems damaged.


MS Data 344785684 610910995 266125312


Can't open filesystem. Filesystem seems damaged.


MS Data 401260219 667385530 266125312


Can't open filesystem. Filesystem seems damaged.


MS Data 480596274 746721585 266125312


Can't open filesystem. Filesystem seems damaged.


MS Data 566582000 832707311 266125312


Can't open filesystem. Filesystem seems damaged.

Aug 7, 2015 12:16 PM in response to Loner T

Hello Loner T, the Windows partition was about 450 Gb before upgrading. I checked all the other MS entries too, but every time the same message "can't open filesystem". I think this means a fresh install. Will it work when I first upgrade to Yosemite and then do the bootcamp thing? Or is Yosemite and bootcamp a bad combination?

Aug 21, 2015 1:25 AM in response to Loner T

Hi Loner T,


Sorry for the late answer, the Macbook didn't start anymore. Turned out the GPU on the mainboard was defect, the mainboard is replaced by Apple. At least I know what caused the strange crashes in Windows...


Back to the disk, checked the entry you suggested:


MS Data 59267072 1000210431 940943360


Can't open filesystem. Filesystem seems damaged.

Oct 22, 2015 10:57 AM in response to BrockwayF

Post the output of the following commands from OSX Terminal in the new discussion


diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0


The "sudo" commands will prompt for your password, and it will not be echoed back. You may also see a warning about improper use of "sudo" and potential data loss due to "abuse" of the command.

After update to Yosemite, Windows won't start

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