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

Windows 7 partition got corrupted after yosemite upgrade

Loner T please help. I can't believe Apple would do this to me. After Yosemite upgrade, windows 7 keeps booting into setup or recovery.


Salmans-MBP-2:~ salman$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *600.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS OS X 199.5 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data Windows 7 300.0 GB disk0s4

5: Microsoft Basic Data 99.8 GB disk0s5

Salmans-MBP-2:~ salman$ diskutil cs list

No CoreStorage logical volume groups found

Salmans-MBP-2:~ salman$ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=600127266816; sectorsize=512; blocks=1172123568

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 1172123567

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

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

391297024 585936896 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

977233920 194887680 5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1172121600 1935

1172123535 32 Sec GPT table

1172123567 1 Sec GPT header

Salmans-MBP-2:~ salman$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 72961/255/63 [1172123568 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 - 389617848] HFS+

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

*4: 07 1023 254 63 - 1023 254 63 [ 391297024 - 585936896] HPFS/QNX/AUX

Salmans-MBP-2:~ salman$

Salmans-MBP-2:~ salman$

Salmans-MBP-2:~ salman$

Salmans-MBP-2:~ salman$ ç

MacBook Pro, OS X Yosemite (10.10.2)

Posted on Mar 11, 2015 1:20 PM

Reply
Question marked as Best reply

Posted on Mar 11, 2015 1:23 PM

Please post the output of the following commands.


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

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

11 replies

Mar 11, 2015 1:38 PM in response to Loner T

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

Password:

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 b8 52 17 |........?.....R.|

00000020 00 00 00 00 80 00 80 00 ff 5f 8a 2e 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 e0 4f 34 ba 5b 34 ba c0 |.........O4.[4..|

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



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

00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

*

00000200


Thx.

Mar 11, 2015 7:33 PM in response to Loner T

The recovery tool or bootrec is not able to find any valid windows partition.

I just noticed that there is a partition 5. I never created a 100GB partition.

Surprisingly OS X does mount Windows 7 disk. I can click on some files and but others error out.

Its a two fold problem: First one as I stated above that windows recovery tool is not able to find any valid partitions. The other problem is that Yosemite upgrade took the windows partition and split into two.

Mar 13, 2015 1:04 PM in response to Loner T

No. I didn't create any additional partitions from within Windows. I am convinced that its Yosemite that messed it up. From within OS X's mounted Windows partition, I can access my relatively older created files without any problems. When I try to access some of the newly created files, they error out. I suspect that those files are residing on the 100GB partition.

Mar 13, 2015 1:39 PM in response to bayarea001

This is a question for Winclone folks. During Restore, if you restore from a 'shrunk' image and restore it to a larger partition, the restore is first done to the same shrunk size, then it is expanded to the designated size, by manipulating the NTFS header and 'moving' it to the larger partition boundary. A chkdsk is then executed so that the MFT and NTFS occupies the entire designated partition. If the 'old' and 'shrunk' NTFS header and MFT is left intact in the original location, Yosemite will see two live headers, and create two parts.


If you had the pre-restore size as 100GB and the expanded size was 400GB (rdisk0s4), Yosemite did the 'correct' procedure by creating the original 100GB and 300GB (perhaps a better option was for the Yosemite upgrade to fail), but the 100GB header (rdisk0s5) is no longer valid because it is no longer linked in the MFT, as it points to a non-existent location on disk.


1. Do you have the original Winclone image?

2. Were any files modified after the expanded Windows was in place (very likely because that was the intent)?

3. The files may get corrupted (as you have observed) because the 100G and 300G chunks now have independent MFTs.

Windows 7 partition got corrupted after yosemite upgrade

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