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.

Andy TLW Author

Level 1

0 points

Bootcamp gone haywire after Yosemite update

Hello

I recently updated my Macbook Pro to OS X Yosemite 10.10, and as a result, my bootcamp (Windows 7, 64-Home edition) is now gone.

I have tried to follow many of the discussions posted already but non seem to have a clear solution to my issue. I ve had no problem with Bootcamp before with the Lion and Maverick updates, but this time my guess is that the problem probably lies in the fact that I re-sized my partitions using a window software.

Basically the current situation is my Bootcamp no longer appears when I press Alt on start-up.

Upon checking my partition through Disk Utility, here is what I see:

So you see that not only Bootcamp is now changed into disk0s4, there is also a gap of hard drive space that is not used by either Mac or Windows.

I have tried the sudo MBR method but I always encounter errors despite I followed word for word on other discussions. I think they likely have a slight different situation than mine? Here is a sample of my Diskutil List: (I saw a guy with a fifth item listed as Basic Data Bootcamp, but I don't have that line...)

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

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data 200.8 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD *449.6 GB disk1

Logical Volume on disk0s2

D642C513-A4DB-4E81-9E67-546F88021205

Unlocked Encrypted

Thank you in advance for replies.

MacBook Pro, OS X Yosemite (10.10)

Posted on Oct 20, 2014 3:29 PM

43 replies

Loner T

Level 9

59,513 points

Oct 25, 2014 5:20 PM in response to Andy TLW

Since you are able to see the NTFS Header, assuming Yosemite did the "right" thing, the simpler fix is to correct the MBR and make Windows bootable.

Please ignore i386 boot error message during the following commands. Post back if there are any other errors.

sudo fdisk -e /dev/disk0

setpid 4

flag 4

Reboot.

1. Test 1 - Can you see Bootcamp volume in Finder?

2. Test 2 - Can you files in Bootcamp Volume?

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

4. Test 4- If Test1,2,3 succeed, select Bootcamp and click on Restart.

Does Window comes up?

Oct 25, 2014 5:52 PM in response to mldrum

thanks, mldrum, i will try that if i upgrade to Yosemite and have problems with Bootcamp. But i hope i won't have to.

Andy TLW Author

Level 1

0 points

Oct 25, 2014 6:43 PM in response to Loner T

Hello Loner

I tried the command, there seems an error with the sudo fdisk -e /dev/disk0

Here is the screenshot http://imgur.com/Tux7Dab

I did the thee steps test and didn't find bootcamp to be working...

Loner T

Level 9

59,513 points

Oct 25, 2014 6:54 PM in response to Andy TLW

Type q since you have written the MBR. Reboot and test.

Andy TLW Author

Level 1

0 points

Oct 25, 2014 8:49 PM in response to Andy TLW

you mean press q after the y?

Also yes! the windows finally showed up if I press Alt in the startup but it will land in a dark screen saying 'an error in reading the disk'

I tried the other tests, I can't find bootcamp anywhere in Finder, Startup Disk, or Disk Utility (still the desk04)

Loner T

Level 9

59,513 points

Oct 25, 2014 9:00 PM in response to Andy TLW

So the simple fix is not correct, which means NTFS is truly corrupted.

I have never tried other tools, but Disk Warrior X or Data Rescue X may be an option.

Andy TLW Author

Level 1

0 points

Oct 25, 2014 9:15 PM in response to Loner T

OK I found a Data Rescue X software. Will give that a try. 😢 why my tech issue always the most problematic kind?

Loner T

Level 9

59,513 points

Oct 25, 2014 10:02 PM in response to Andy TLW

1. You need to also think about the contingency if Windows cannot be recovered.

2. Couple of hundred blocks before and after the problematic cylinder can be dumped via dd to an external file and I can try to get in touch with the Testdisk team to see what they see as an issue that is causing their software to malfunction.

3. Since the area where OS X is currently sitting is creating problems for Testdisk, another option is to re-install OS X which leaves all your other files untouched and check if Testdisk can get past this area.

Andy TLW Author

Level 1

0 points

Oct 25, 2014 11:54 PM in response to Loner T

ok will do.

Right now trying to see if the DataRescue will repair windows back to normal.

I think the next step I will take is to try to reinstall OS X and re-run Testdisk.

If comes to worst, I will re-partition bootcamp and start anew as the last choice. The only problem with that is I have some important files stored on the windows side, and I need to extract those before the restart.

Thanks for your wonderful follow-ups Loner, will keep this updated till it resolves.

Loner T

Level 9

59,513 points

Oct 26, 2014 6:05 AM in response to Andy TLW

You can extract files using Testdisk. There is a sister product called PhotoRec. Test disk does allow file extraction. Please ensure that you have adequate backups of OS X side, before you start re-partitioning.

Andy TLW Author

Level 1

0 points

Oct 27, 2014 9:18 PM in response to Loner T

Helle Loner

Still trying to restore first.

I have clean installed Yosemite this time and I got this list, which one should I pick? thanks. Link

Andy TLW Author

Level 1

0 points

Oct 27, 2014 10:02 PM in response to Andy TLW

Ok Nvm I picked disk /dev/rdisk0 based on my rational guess.

The scan started at 59% this time and finished in a minute or so ...

Here are the screenshots. What should I do next?

http://imgur.com/aZrkHp9

http://imgur.com/Nq8dbYS

Loner T

Level 9

59,513 points

Oct 28, 2014 4:37 AM in response to Andy TLW

Please look in MS Data entries which are 584560633 sectors in size. They look very likely candidates. The last MS Data has a smaller size, which looks like a corrupted version, but please check that one as well. Notice the "P", which should allow you to look for files.

Do not use left/right arrows which delete partitions.