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

Bootcamp partition missing after yosemite installation

I am running OS X 10.10.1 currently. Right after I upgraded to Yosemite my windows 7 partition was missing. I have all of my school work and programs on that partition and I use it quite often. I have seen other questions similar to this but none with an external hard drive backed up like I do. I tried to repair the windows 7 partition with disk utility but it appears to just be floating in cyber space unrecognizable and unrepairable. Something happened when I "upgraded" to Yosemite.


Thankfully, I have an external hard drive with both my Macbook partition as well as my windows 7 partition saved on to my external hard drive. I went the extra mile and partitioned my external hard drive as well with a macbook partition and a windows 7 partition so they are not in the same part of the hard drive. Unfortunately I'm a little rusty with my tech skills now. How can I just restore this back to what it was? time machine won't restore my windows 7 partition. I just want everything back to where it was originally, I don't care about yosemite. I'm quite sure that I didn't overwrite the windows 7 partition on my external hard drive because it doesn't exist on this new operating system, so it must be in my external drive. Can someone please give me some direction for a beginner on stuff like this?

MacBook Pro (15-inch Mid 2012)

Posted on Mar 4, 2015 2:35 PM

Reply
58 replies

Apr 21, 2015 7:43 PM in response to Loner T

Thanks- I've followed the thread very carefully, but failing so far. Only difference I see is that I seem to have only GPT 1-3, and no 4. Anyway, here are my initial diagnostics:

Last login: Tue Apr 21 19:30:26 on console

LisaHawkinssMBP:~ lisahawkins$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *500.1 GB disk0

1: 0xEE 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 465.9 GB disk0s2

3: Windows_NTFS 33.9 GB disk0s3

4: 0xEE 135.2 MB disk0s4

LisaHawkinssMBP:~ lisahawkins$ diskutil cs list

No CoreStorage logical volume groups found

LisaHawkinssMBP:~ lisahawkins$ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=500107862016; sectorsize=512; blocks=976773168

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 976773167

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

910311464 264152

910575616 66197504 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

976773120 15

976773135 32 Sec GPT table

976773167 1 Sec GPT header

LisaHawkinssMBP:~ lisahawkins$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 60801/255/63 [976773168 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 - 909901824] HFS+

*3: 07 1023 254 63 - 1023 254 63 [ 910575616 - 66197504] HPFS/QNX/AUX

4: EE 1023 254 63 - 1023 254 63 [ 910311464 - 264152] <Unknown ID>

LisaHawkinssMBP:~ lisahawkins$

And from Testdisk:

TestDisk 7.0, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org


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

Partition Start End Size in sectors

>P EFI System 40 409639 409600 [EFI]

D Mac HFS 409640 910311463 909901824

D MS Data 844265473 910518272 66252800

D MS Data 910108673 910313472 204800

D MS Data 910313472 910518271 204800

D MS Data 910518272 976771071 66252800

Of which the last one reveals this:

TestDisk 7.0, Data Recovery Utility, April 2015

Christophe GRENIER <grenier@cgsecurity.org>

http://www.cgsecurity.org

MS Data 910518272 976771071 66252800

Directory /


>dr-xr-xr-x 0 0 0 25-Dec-2014 16:18 .

dr-xr-xr-x 0 0 0 25-Dec-2014 16:18 ..

dr-xr-xr-x 0 0 0 30-Dec-2009 19:39 $Recycle.Bin

dr-xr-xr-x 0 0 0 6-Jul-2014 18:23 0b7b82811c505f63a4b555bc

dr-xr-xr-x 0 0 0 24-Jul-2014 03:01 2a2a3335c61ef1128922a4

dr-xr-xr-x 0 0 0 23-Jul-2014 03:03 527c973c361711742234a9

dr-xr-xr-x 0 0 0 5-Jul-2014 03:01 6890cb726756024788

dr-xr-xr-x 0 0 0 22-Jul-2014 03:01 6f76c71cc847e45bb28aa9351be3186a

dr-xr-xr-x 0 0 0 6-Jun-2014 03:03 733bb789d5d0761614c7bbcd

dr-xr-xr-x 0 0 0 15-Sep-2014 08:49 799c0662421ccce03c2d

dr-xr-xr-x 0 0 0 4-Jul-2014 03:01 866b0dbcffd6fb5df3265f1b0650ef

dr-xr-xr-x 0 0 0 3-Oct-2010 18:24 GridConnectCDImage

dr-xr-xr-x 0 0 0 24-Oct-2010 01:06 Intel

dr-xr-xr-x 0 0 0 22-Apr-2013 16:21 LENSRG

dr-xr-xr-x 0 0 0 6-Nov-2011 09:15 LENSarchive

dr-xr-xr-x 0 0 0 30-Oct-2010 14:40 MSOCache

dr-xr-xr-x 0 0 0 9-Nov-2014 08:52 NFDBBackup

dr-xr-xr-x 0 0 0 29-Nov-2014 21:36 NeuroField

dr-xr-xr-x 0 0 0 22-Apr-2013 10:53 NeuroFieldData

dr-xr-xr-x 0 0 0 16-Jan-2010 01:21 Nfviewer

dr-xr-xr-x 0 0 0 16-Jan-2010 01:21 PUZZLE1

dr-xr-xr-x 0 0 0 13-Jul-2009 19:37 PerfLogs

dr-xr-xr-x 0 0 0 2-Jul-2014 13:03 Program Files

dr-xr-xr-x 0 0 0 2-Jul-2014 13:03 ProgramData

dr-xr-xr-x 0 0 0 30-Dec-2009 19:39 Recovery

dr-xr-xr-x 0 0 0 15-Jan-2010 23:33 SP

dr-xr-xr-x 0 0 0 16-Jan-2010 01:21 SR1

dr-xr-xr-x 0 0 0 30-Nov-2014 17:20 System Volume Information

dr-xr-xr-x 0 0 0 27-Jan-2010 14:52 Users

dr-xr-xr-x 0 0 0 21-Jul-2014 11:58 Windows

dr-xr-xr-x 0 0 0 10-Jun-2014 03:01 a3b3b219ca2a5c0fb376ddeb

dr-xr-xr-x 0 0 0 3-Jul-2014 03:01 a8625b63c9384f3598

dr-xr-xr-x 0 0 0 10-Nov-2011 16:56 brainm.20

dr-xr-xr-x 0 0 0 6-Jul-2014 03:01 c43e89362e8563601eb5dc28c4

dr-xr-xr-x 0 0 0 15-Jan-2010 23:27 corrupt

dr-xr-xr-x 0 0 0 11-Jun-2014 03:01 f21b8af659a9edd3778ff0

dr-xr-xr-x 0 0 0 2-Jul-2014 10:13 fffbe77624226d2eeb866dff0bc91bae

dr-xr-xr-x 0 0 0 15-Jan-2010 23:27 lensdata

dr-xr-xr-x 0 0 0 6-Nov-2011 09:23 ol_install

-r--r--r-- 0 0 43425624 3-Oct-2010 12:13 AdbeRdr934_en_US.exe

-r--r--r-- 0 0 5975298 19-Apr-2011 11:22 Crash ILF T4 P4.bmz

-r--r--r-- 0 0 0 3-Oct-2010 18:16 IO.SYS

-r--r--r-- 0 0 2477 19-Apr-2011 11:21 InfraLowFrequency Mark Smith.bmz

-r--r--r-- 0 0 0 3-Oct-2010 18:16 MSDOS.SYS

Next

So I use the numbers at the top to delete GPT3 and rebuild it. The only odd thing is that when I do the MBR, after I set the boot flag to Y on the GPT3, it says there's an empty partition or something and asks if I want to "protect" it or something. I've tried this answering Y and N and both paths fail to make the overall fix (ie, can't see the bootcamp volume in Finder). Any ideas?

Thanks a million!

Apr 21, 2015 8:39 PM in response to kswint

1. GPT3 exists for OSX versions which support Recovery HD. What is your OSX version? Did this happen after a 10.10.3 Recovery Update?

2. Your disk has become an MBR type, based on the incorrect MBR entries. Usually EFI is never explicitly added via Gdisk. The first question that Gdisk asks about good for Grub, when answered as a yes, will put the EFI as MBR1.

3. The order of your partitions seems to be incorrect, most likely due to item 2.

4. Recovery HD can be re-built later. The first goal should be to get Windows up and running.

5. The following table is normally built using GPT3 and GPT4, but in your case, I have used GPT2 and GPT3.


User uploaded file


Gdisk will use sector boundary alignment. In your case a gap of 101MB is not alignment, but space, that Gdisk wants to protect, if you ask it to. You should only specify partitions 2 and 3 in your new hybrid MBR and say yes to GRUB question, and no to additional partitions.

Apr 22, 2015 2:31 PM in response to Loner T

OSX version is 10.10.3. This happened after upgrading from 10.6.X or something quite old. In the table above I assume NTFS = GPT3. I'm not sure what to do with the 2 sector offsets, but I'll attempt to rebuild and see. BTW, I originally did say yes to GRUB and no to additional partitions. Since that failed, I tried again saying yes to additional partitions. Thanks!

Apr 22, 2015 5:05 PM in response to kswint

Please see https://support.microsoft.com/en-us/kb/2622803.


1. If you have the W7 installation media, insert the USB (or DVD, if you have an Optical drive).

2. In OSX System Preferences -> Startup Disk -> select Bootcamp and click on Restart.

3. The installer should come up from the installation media. Click on Repair option, after you choose language, region, etc.


It should look like http://imgur.com/a/1DaOE#0 .

Apr 23, 2015 4:09 AM in response to kswint

From the M$ link...


There are two options to choose from during the Windows 7 installation process:

  • Upgrade. This option replaces your current version of Windows with Windows 7, and keeps your files, settings, and programs in place on your computer.
  • Custom. This option replaces your current version of Windows with Windows 7, but doesn't preserve your files, settings, and programs. It's sometimes referred to as a clean installation for that reason.

Apr 23, 2015 12:26 PM in response to Loner T

Yes, but to my understanding, to use the Upgrade option you have to be able to boot up the machine in Windows, not from an install disk, which I can't do (yet?). Any other method is the Custom option. I have an app that supposedly can fix this BOOTMGR problem, but I have to boot the machine from a .ios file on a USB in order to use it. Trying to figure that out now.

Bootcamp partition missing after yosemite installation

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