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

Lost Windows partition after upgrading to Yosemite

Hi all,


Hope you can help since upgrading my Mac OS to Yosemite, I have been unable to log back into my Windows Partition. If i hold alt on start up on the mac disk is shown. I have seen a few similar issues on this forum and been trying to follow the post but struggling a little now so wondered if some could help with next step


This seems to be the info from the other threads. I have installed the test disk utility and done a analyse on the disk, i'm little unsure of what to do now, i would like if possible to go back into the windows instead of reinstalling as i have quite a bit of data on that side of the disk.


Any help massively appreciated Dave


User uploaded file


User uploaded file



User uploaded file


User uploaded fileUser uploaded file

Posted on Feb 4, 2015 4:14 PM

Reply
30 replies

Apr 17, 2015 11:05 PM in response to Loner T

I think I'm seeing a similar problem (lost access to Windows after Yosemite upgrade), but I have a little different situation.


While my system (MBP 11,1) was still running Mavericks, a while back I used the excellent instructions on how to add a third bootable partition using the hybrid MBR instructions. My partition table looks like this:


Disk /dev/disk0: 977105060 sectors, 465.9 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): 8654C3BA-C230-47F6-A9C4-AC1F5FF234CE

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 977105026

Partitions will be aligned on 8-sector boundaries

Total free space is 137 sectors (68.5 KiB)


Number Start (sector) End (sector) Size Code Name

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 442304239 210.7 GiB AF00 Customer

3 442304240 443573775 619.9 MiB AB00 Recovery HD

4 443573776 741462231 142.0 GiB AF05 Work Boot

5 741462232 742731775 619.9 MiB AB00 Recovery HD

6 742731776 977104895 111.8 GiB 0700 BOOTCAMP

When I first booted after the update with Option held down, I saw only the main boot partition ("Macintosh HD") and the "Work Boot" partition. The first is still Mavericks (10.9.5), the other is Yosemite (10.10.3).

After some messing about I remembered the commands to at least expose the BOOTCAMP partition:

Recovery/transformation command (? for help): h


WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,

just hit the Enter key at the below prompt and your MBR partition table will

be untouched.


Type from one to three GPT partition numbers, separated by spaces, to be

added to the hybrid MBR, in sequence: 5

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): n


Creating entry for GPT partition #5 (MBR partition #1)

Enter an MBR hex code (default AB):

Set the bootable flag? (Y/N): y


Unused partition space(s) found. Use one to protect more partitions? (Y/N): n


Recovery/transformation command (? for help): o


Disk size is 977105060 sectors (465.9 GiB)

MBR disk identifier: 0xD2D65B97

MBR partitions:


Number Boot Start Sector End Sector Status Code

1 * 741462232 742731775 primary 0xAB

2 1 741462231 primary 0xEE


Recovery/transformation command (? for help): w


Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING

PARTITIONS!!


Do you want to proceed? (Y/N): y

OK; writing new GUID partition table (GPT) to /dev/disk0.

Warning: Devices opened with shared lock will not have their

partition table automatically reloaded!

Warning: The kernel may continue to use old or deleted partitions.

You should reboot or remove the drive.

The operation has completed successfully.

and got it so that all three show up when I boot with Option, although I only see one recovery partition (labeled Recovery 10.9). But trying to boot the BOOTCAMP partition (which shows up as "Windows" in the alt boot screen) gets me the "Missing operating system_" error.

Running Repair Disk generates mostly ok output, with the exception of "Invalid Disk Label, cksum error" mismatch errors, e.g.:

disk0s4: Scan for Volume Headers

disk0s4: Scan for Disk Labels

Invalid Disk Label @ 152510496768: cksum mismatch

Running Repair Disk seems to undo the hybrid partition map (but you probably knew that 🙂 )

I'm not sure that that isn't causing additional trouble, as I also got a "Missing operating system_" error on the Work Boot partition at least once after doing those commands and rebooting.

I have some options:

* Nothing on the Windows partition was critical, and I should have a full backup on that external disk I mentioned (Windows 7, using the standard Windows backup routine). So nuke-and-pave is an option, if that's simplest–but I've never done that, so pointers would be good.

* If it's possible to recover what was there, that would be great. As a start, here's the dump from TestDisk 7.0-WIP:

TestDisk 7.0-WIP, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org


Disk /dev/disk0 - 500 GB / 465 GiB - 977105060 sectors (RO)

Current partition structure:

Partition Start End Size in sectors


1 P EFI System 40 409639 409600 [EFI System Partition]

2 P Mac HFS 409640 442304239 441894600 [Customer]

3 P Mac Boot 442304240 443573775 1269536 [Recovery HD]

4 P Unknown 443573776 741462231 297888456 [Work Boot]

5 P Mac Boot 741462232 742731775 1269544 [Recovery HD]

Warning: number of heads/cylinder mismatches 255 (NTFS) != 1 (HD)

Warning: number of sectors per track mismatches 63 (NTFS) != 1 (HD)

6 P MS Data 742731776 977104895 234373120 [BOOTCAMP]


I don't know if that helps you or not.

* As a last ditch, I have backups of all three partitions (Time Machine for both Mac partitions and a disk image of Work Boot done just before the Yosemite upgrade), so nuke-and-pave for all three is possible. But I'd really, really like to get back to the three partition scheme (personal Mac OS, work Mac OS, personal Windows).

Any advice would be appreciated.


Thanks!

Apr 18, 2015 10:24 AM in response to scfw0x0f

I got this result from the quick analyse of the drive:


TestDisk 7.0-WIP, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org


Disk /dev/rdisk0 - 500 GB / 465 GiB - 977105060 sectors (RO)


The harddisk (500 GB / 465 GiB) seems too small! (< 620 GB / 577 GiB)

Check the harddisk size: HD jumpers settings, BIOS detection...


The following partitions can't be recovered:

Partition Start End Size in sectors

> MS Data 977104895 1211478014 234373120


Mac HFS 977105020 978374555 1269536










[ Continue ]

NTFS, blocksize=4096, 119 GB / 111 GiB


After hitting CONTINUE:

TestDisk 7.0-WIP, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org


Disk /dev/rdisk0 - 500 GB / 465 GiB - 977105060 sectors (RO)

Partition Start End Size in sectors

>P EFI System 40 409639 409600 [EFI]

P Mac HFS 409640 442304239 441894600

P Mac HFS 442304240 443573775 1269536

D Mac HFS 523065160 964959759 441894600

D MS Data 742731776 977104895 234373120

D Mac HFS 975835488 977105023 1269536







Structure: Ok. Use Up/Down Arrow keys to select partition.

Use Left/Right Arrow keys to CHANGE partition characteristics:

P=Primary D=Deleted

Keys A: add partition, L: load backup, T: change type, P: list files,

Enter: to continue

FAT32, blocksize=512, 209 MB / 200 MiB


Following what Loner T recommended in another thread, I went to the MS Data partition and hit 'P':

TestDisk 7.0-WIP, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org

MS Data 742731776 977104895 234373120

Directory /


>dr-xr-xr-x 0 0 0 11-Mar-2015 12:06 .

dr-xr-xr-x 0 0 0 11-Mar-2015 12:06 ..

dr-xr-xr-x 0 0 0 18-Mar-2014 20:53 $Recycle.Bin

dr-xr-xr-x 0 0 0 11-Mar-2015 12:06 Boot

dr-xr-xr-x 0 0 0 31-Jan-2015 16:16 Config.Msi

dr-xr-xr-x 0 0 0 23-Oct-2014 17:40 Intel

dr-xr-xr-x 0 0 0 13-Jul-2009 20:20 PerfLogs

dr-xr-xr-x 0 0 0 7-Dec-2014 18:00 Program Files

dr-xr-xr-x 0 0 0 22-Jan-2015 20:24 Program Files (x86)

dr-xr-xr-x 0 0 0 22-Jan-2015 20:21 ProgramData

dr-xr-xr-x 0 0 0 18-Mar-2014 20:53 Recovery

dr-xr-xr-x 0 0 0 11-Mar-2015 12:12 System Volume Information

dr-xr-xr-x 0 0 0 18-Mar-2014 20:53 Users

dr-xr-xr-x 0 0 0 23-Jan-2015 04:08 Windows

Next

Use Right to change directory, h to hide Alternate Data Stream

q to quit, : to select the current file, a to select all files

C to copy the selected files, c to copy the current file

Part 2:

TestDisk 7.0-WIP, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org

MS Data 742731776 977104895 234373120

Directory /

Previous

dr-xr-xr-x 0 0 0 13-Jul-2009 20:20 PerfLogs

dr-xr-xr-x 0 0 0 7-Dec-2014 18:00 Program Files

dr-xr-xr-x 0 0 0 22-Jan-2015 20:24 Program Files (x86)

dr-xr-xr-x 0 0 0 22-Jan-2015 20:21 ProgramData

dr-xr-xr-x 0 0 0 18-Mar-2014 20:53 Recovery

dr-xr-xr-x 0 0 0 11-Mar-2015 12:12 System Volume Information

dr-xr-xr-x 0 0 0 18-Mar-2014 20:53 Users

dr-xr-xr-x 0 0 0 23-Jan-2015 04:08 Windows

-r--r--r-- 0 0 8192 19-Mar-2014 04:03 BOOTSECT.BAK

-r--r--r-- 0 0 2056 18-Mar-2014 20:56 RHDSetup.log

-r--r--r-- 0 0 383786 20-Nov-2010 19:23 bootmgr

-r--r--r-- 0 0 0 19-Mar-2014 07:54 end

-r--r--r-- 0 0 12812943360 12-Mar-2015 22:27 hiberfil.sys

>-r--r--r-- 0 0 2097152000 12-Mar-2015 22:27 pagefile.sys

Next

Use Right to change directory, h to hide Alternate Data Stream

q to quit, : to select the current file, a to select all files

C to copy the selected files, c to copy the current file


The top 3 numbers:

TestDisk 7.0-WIP, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org

MS Data 742731776 977104895 234373120

Directory /

Apr 18, 2015 10:26 AM in response to scfw0x0f

1. Please post the output of


sudo dd if=/dev/rdisk0sN count=1 2>/dev/null | hexdump -C (where N is the number assigned to the Bootcamp disk slice as seen in diskutil list output).


2. You have two OS X installations, and corresponding Recovery HDs. On a single-disk Mac, this is an invitation to data loss. How is tolerance for data loss? My recommendation is to remove one OS X+Recovery installation and put it on an external disk and boot from it when needed.


3. No hybrid MBR can be crafted which a subsequent software upgrade will not corrupt. Your current configuration is non-standard.


4. You do not need a new MBR (yet!) till the output from step 1 is available.

Apr 18, 2015 10:35 AM in response to Loner T

1) dd output:

Stephens-MacBook-Pro:~ scf$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 226.3 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Apple_CoreStorage 152.5 GB disk0s4

5: Apple_Boot Recovery HD 650.0 MB disk0s5

6: Microsoft Basic Data BOOTCAMP 120.0 GB disk0s6

Stephens-MacBook-Pro:~ scf$ sudo dd if=/dev/rdisk0s6 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 30 45 2c |........?....0E,|

00000020 00 00 00 00 80 00 80 00 ff 3f f8 0d 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 71 dc 40 04 1f 41 04 fe |........q.@..A..|

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

2) Yes, it's a MBP I use for work (who does their own nasty stuff to their partition) and personal use. This partition scheme has worked well for over a year, and carrying a separate drive is a PITA (travel, etc.). I'd prefer to keep it as-is for now and keep backing up frequently...

3) Understood. I *think* at least once I had to go back into gdisk and repeat the steps to rebuild the hybrid MBR.

4) See above (and thanks!)

Apr 18, 2015 9:10 PM in response to Loner T

Yeah...that didn't go so well.


In "sudo gdisk /dev/disk0", I did this:


Recovery/transformation command (? for help): h


WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,

just hit the Enter key at the below prompt and your MBR partition table will

be untouched.


Type from one to three GPT partition numbers, separated by spaces, to be

added to the hybrid MBR, in sequence: 4 5 6

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): n


Creating entry for GPT partition #4 (MBR partition #1)

Enter an MBR hex code (default AF):

Set the bootable flag? (Y/N): y


Unused partition space(s) found. Use one to protect more partitions? (Y/N): n


Recovery/transformation command (? for help): p

Disk /dev/disk0: 977105060 sectors, 465.9 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): 8654C3BA-C230-47F6-A9C4-AC1F5FF234CE

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 977105026

Partitions will be aligned on 8-sector boundaries

Total free space is 137 sectors (68.5 KiB)


Number Start (sector) End (sector) Size Code Name

1 40 409639 200.0 MiB EF00 EFI System Partition

2 409640 442304239 210.7 GiB AF00 Customer

3 442304240 443573775 619.9 MiB AB00 Recovery HD

4 443573776 741462231 142.0 GiB AF05 Work Boot

5 741462232 742731775 619.9 MiB AB00 Recovery HD

6 742731776 977104895 111.8 GiB 0700 BOOTCAMP


Recovery/transformation command (? for help): o


Disk size is 977105060 sectors (465.9 GiB)

MBR disk identifier: 0xD2D65B97

MBR partitions:


Number Boot Start Sector End Sector Status Code

1 * 443573776 741462231 primary 0xAF

2 1 443573775 primary 0xEE


Recovery/transformation command (? for help): w


Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING

PARTITIONS!!


Do you want to proceed? (Y/N): y

Rebooting with <option> showed only the Windows partition.

I suspect I missed something.

Landru, guide us! 🙂

Apr 18, 2015 9:29 PM in response to scfw0x0f

Here is a sample Q&A when 2 3 4 is used. In your case it will shift to 4 5 6. Please ensure you accept the defaults for MBR Hex codes by pressing enter/return.

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y


Creating entry for GPT partition #2 (MBR partition #2)

Enter an MBR hex code (default AF): Press Enter/Return

Set the bootable flag? (Y/N): N


Creating entry for GPT partition #3 (MBR partition #3)

Enter an MBR hex code (default AB): Press Enter/Return

Set the bootable flag? (Y/N): N


Creating entry for GPT partition #4 (MBR partition #4)

Enter an MBR hex code (default 07): Press Enter/Return

Set the bootable flag? (Y/N): Y

Apr 18, 2015 9:57 PM in response to Loner T

Are you doing this with Mavericks or Yosemite, or something else? When I run this using gdisk under Mavericks, i get this sequence:


Recovery/transformation command (? for help): h


WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,

just hit the Enter key at the below prompt and your MBR partition table will

be untouched.


Type from one to three GPT partition numbers, separated by spaces, to be

added to the hybrid MBR, in sequence: 4 5 6

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): n


Creating entry for GPT partition #4 (MBR partition #1)

Enter an MBR hex code (default AF):

Set the bootable flag? (Y/N): y


Unused partition space(s) found. Use one to protect more partitions? (Y/N): y

Note: Default is 0xEE, but this may confuse Mac OS X.

Enter an MBR hex code (default EE): 07


I don't see the question about Unused partition space(s) in your sequence.


Apparently in the meantime I've really horked things up; the whole disk is no longer recognized by Disk Utility 😟 I'm going nuke-and-pave on the whole disk.


Given that, is it still possible from that point to add the third partition? I could try my original instructions from here: <Re: Repairing Boot Camp after creating new partition>


Argh! (But thanks for trying!)

Apr 19, 2015 4:04 AM in response to scfw0x0f

scfw0x0f wrote:


Are you doing this with Mavericks or Yosemite, or something else? When I run this using gdisk under Mavericks, i get this sequence:


Recovery/transformation command (? for help): h


WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,

just hit the Enter key at the below prompt and your MBR partition table will

be untouched.


Type from one to three GPT partition numbers, separated by spaces, to be

added to the hybrid MBR, in sequence: 4 5 6

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): n

This is incorrect. Do you realize what your answer does to your MBR?


scfw0x0f wrote:


Are you doing this with Mavericks or Yosemite, or something else? When I run this using gdisk under Mavericks, i get this sequence:


Recovery/transformation command (? for help): h


WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,

just hit the Enter key at the below prompt and your MBR partition table will

be untouched.


Type from one to three GPT partition numbers, separated by spaces, to be

added to the hybrid MBR, in sequence: 4 5 6

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): n


Creating entry for GPT partition #4 (MBR partition #1)

Enter an MBR hex code (default AF):

Set the bootable flag? (Y/N): y


Unused partition space(s) found. Use one to protect more partitions? (Y/N): y

Note: Default is 0xEE, but this may confuse Mac OS X.

Enter an MBR hex code (default EE): 07


I don't see the question about Unused partition space(s) in your sequence.

In my case, I do not have a large gap between my GPT entries. Gdisk does not show such a gap. You also seem to answer the same question with a yes and a no, which is incorrect.

Unused partition space(s) found. Use one to protect more partitions? (Y/N): n


Recovery/transformation command (? for help): p

Disk /dev/disk0: 977105060 sectors, 465.9 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): 8654C3BA-C230-47F6-A9C4-AC1F5FF234CE

Partition table holds up to 128 entries

Please post the output of sudo gpt -vv -r show /dev/disk0.

Lost Windows partition after upgrading to Yosemite

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