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.

WarthogARJ Author

Level 1

8 points

Repairing Boot Camp after upgrading to Mavericks: Jarvis

Hi,

I cannot boot up into BootCamp after I upgraded to Mavericks: problem has been with me for about a year.

MacBook Pro 13: mid-2012

Mavericks 10.9.5

960 GB SSD: Mac OS etc and BootCamp partitions

1 TB HDD in the optical bay slot: HDD (data) and HDD2 for personal encrypted data.

BootCamp runs on Windows 7 Ultimate.

I am able to access the BootCamp partition with Parallel's Desktop.

But I want to be able to boot into it as well (like I used to in Lion).

Would really appreciate help from Chris Murphy or LonerT on this.

I've been following your thread:

Repairing Boot Camp after creating new partition

The output from the various Terminal commands are:

Last login: Tue Sep 23 20:25:52 on console

alans-mbp:~ arjarvis_mbp$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *960.2 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Mac_SSD 869.9 GB disk0s2

3: Apple_Boot Recovery HD 784.2 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 89.3 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS Mac_HDD 954.1 GB disk1s2

3: Apple_CoreStorage 45.6 GB disk1s3

4: Apple_Boot Boot OS X 134.2 MB disk1s4

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Mac_HDD 2 *45.3 GB disk2

alans-mbp:~ arjarvis_mbp$ sudo fdisk /dev/disk0

Password:

Disk: /dev/disk0 geometry: 116737/255/63 [1875385008 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 - 1698931968] HFS+

3: AB 1023 254 63 - 1023 254 63 [1699341608 - 1531680] Darwin Boot

4: 0C 1023 254 63 - 1023 254 63 [1700874240 - 174510080] Win95 FAT32L

alans-mbp:~ arjarvis_mbp$ sudo gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=960197124096; sectorsize=512; blocks=1875385008

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 1875385007

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

1699341608 1531680 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

1700873288 952

1700874240 174510080 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1875384320 655

1875384975 32 Sec GPT table

1875385007 1 Sec GPT header

Thanks very much,

Alan Jarvis

MacBook Pro (13-inch Mid 2012), OS X Mavericks (10.9.5), BootCamp Windows 7 Ultimate

Posted on Sep 23, 2014 12:48 PM

86 replies

WarthogARJ Author

Level 1

8 points

Sep 24, 2014 4:17 PM in response to Loner T

Great idea: maybe I'm doing something silly.

But I really don't think so.

I erased the USB stick and formatted as MS-FAT.

I added the ISO file (from Bill Gates himself).

I did the Restore in the right order.

I even slaughtered a chicken and said the magic words.

But sigh, to no avail.

And I even tried the Terminal DD method, with various success.

Sometimes it said Access denied.

Or Busy.

And once it did work, but when I tried to boot up into it nothing happened.

System just hung.

I think I need to insure this sucker and look for another Mack Truck.

Loner T

Level 9

59,513 points

Sep 24, 2014 4:22 PM in response to WarthogARJ

I cannot see the images. Do you have access to an external imaging service, like IMGUR?

For the dd method, the device should be unmounted.

WarthogARJ Author

Level 1

8 points

Sep 24, 2014 4:57 PM in response to Loner T

How about this?

https://www.dropbox.com/sh/wjuxzqn2oioe0t7/AABuxlbbrmi3279ki1yYx3Qta?dl=0

And for the dd method it was unmounted.

But it wasn't recognized during the restart.

Loner T

Level 9

59,513 points

Sep 24, 2014 5:30 PM in response to WarthogARJ

I have a Windows 64-bit.cdr file. Let me test burn it to a USB. I can see your screen shots via Dropbox. Thanks.

WarthogARJ Author

Level 1

8 points

Sep 24, 2014 5:46 PM in response to Loner T

I am running 32 bit from Windows 7 Enterprise on BootCamp.

I have a 32 bit ISO of that.

And i've tried to make a USB with Ultimate 32 bit ISO as well.

Using three different USB sticks,

I REALLY cannot understand why it's proving such a hassle just to maker a bootable USB drive.

I did that before for Mac OSX.

Loner T

Level 9

59,513 points

Sep 24, 2014 8:23 PM in response to WarthogARJ

For the dd command, try using sudo dd if=ISO of=USB bs=1024. I have tested it once, I am doing it again right now.

Loner T

Level 9

59,513 points

Sep 25, 2014 2:15 PM in response to WarthogARJ

If you have the ISO on your Mac(k), start Bootcamp Assistant, choose the first Option only (Create a W7 install drive). Point to your W ISO as source, and the USB as your destination and let it format and build a USB stick. Verify that the ALT key shows the USB.

Test the recovery by selecting your Bootcamp partition (not the USB), and try to recover W7. Use the ISO that your originally used to install the W7 installation.

WarthogARJ Author

Level 1

8 points

Sep 25, 2014 4:49 PM in response to Loner T

Hi,

OK thanks I'll try that.

What's the best way to prepare the USB for this?

Just erase it as Fat?

BootCampAssistant formats/erases it anyways, so maybe doesn't matter.

I thought I had the reason for my problems in making a notable USB, but am not 100% sure.

I have a USB hub on my desk and I think the USB stick gets knocked during the LONG preparation process.

Not sure, but it did happen once, so maybe it was happening every time.

Is not that physically secure a connection.

However after I saw that I was very careful not to know it, and it took over an hour to prepare the USB stick using Termanal sudo DD: in fact I stopped it.

Think something wasn't going right.

I HAVE used the sudo DD process at least once successfully before, so I am STILL not sure what the issue is.

I've just ordered a few new USB sticks in case maybe my current ones are the issue: never hurts to have a few extra, are cheap now.

anyways, I really appreciate your help in this.

Alan

WarthogARJ Author

Level 1

8 points

Sep 25, 2014 5:02 PM in response to WarthogARJ

I think I've found one reason for some of my hassles.

I tried using an ISO created quite a while ago from the DVD that I am pretty sure I used to create BootCamp about 2 computers ago (MacBook 2008, then mid-2012 note this mid-2012).

And that ISO copy keeps on getting an error from BootCamp Assistant saying could not create bootable USB.

Maybe it's corrupted?

So I am trying with an ISO I downloaded from the MS site recently.

It's 32bit Windows 7 Ultimate (X17- 59463).

And there IS a bit of a strange issue with what my Windows 7 Bootcamp actually is.

I never had an Enterprise DVD or ISO: I am SURE it was installed as an Ultimate 32 Bit: I still have that DVD in the original box.

However I have vague memories of a friend helping me with a spare Enterprise licence he had (he's an IT guy).

It's never given me issues, and is recognized by MS as genuine.

BootCamp claims it's Enterprise, but I think that might not matter because aren't Enterprise and Ultimate more or less the same?

Sigh, was all done a while ago.

If I didn't have so much special software etc installed I'd just delete everything and do a clean install with a brand new Windows licence.

Loner T

Level 9

59,513 points

Sep 25, 2014 5:30 PM in response to WarthogARJ

My test was...

1. Create a USB using the ISO and a 4 (or more) GB USB stick and Windows 7 (64-bit) DVD as test using Bootcamp Assistant. (You will need to use a DVD matching the 'bitness' of your Windows installation).

2. Power Cycle the Mac and hold the ALT key. (Apparently there is no Recovery Environment otherwise).

3. Choose the USB to boot from, choose Language, etc.

4. At bottom left corner there is a Repair option.

5. Click on it and repair as needed.

6. Test.

WarthogARJ Author

Level 1

8 points

Sep 25, 2014 5:40 PM in response to Loner T

Dang.

Yeah I have tried that.

- In fact I added in a USB DVD drive vas well with the original DVD Win 7 Ultimate disc.

- I made a USB with BootCamp using item 1 only.

- Rebooted and held down ALT

- saw Lots of options: OSX, BotCamp (there because of your fix), USB, DVD

I selected the USB and it took a few minutes and then went from there to nothing....just back screen.

For about 20 minutes.

Then I rebooted amnd tried the DVD.

Same thing.

I'm not able to boot up into Windows, never mind any choice of language or Repair.

Something is rotten in the State of Denmark, to quote the Bard.

I think I'm still not in the clear with fixing this Mavericks/Bootcamp thing.

How can I check that?

Loner T

Level 9

59,513 points

Sep 25, 2014 5:41 PM in response to WarthogARJ

Use both Option 1( ISO) and Bootcamp Drivers(2). Because you have moved the Bootcamp installations, the drivers for Graphics/Keyboard/Mouse may be causing problems for you.

WarthogARJ Author

Level 1

8 points

Sep 26, 2014 7:20 AM in response to Loner T

Unfortunately this didn't work.

I made two USB sticks with BootCamp this way, one with Option 1, the other with 1 and 2.

But although I can see them during a cold boot up when I press ALT, when I select them the boot up hangs.

I left it overnight and was still frozen.

And as I said it does see the Win Ultimate 7 DVD if I use an external USB drive: but that hangs also.

If I make a Win 7 ISO mounted in Disk Utility with Parallels going, it DOES ask me if I want to use it though.

So I think the problem is STILL with my BootCamp partition.

It's not completely solved.

Any ideas on anything I can try to fix the partition?

Loner T

Level 9

59,513 points

Sep 26, 2014 7:42 AM in response to WarthogARJ

Since you are using Parallels and Bootcamp, both, as a test, can you remove Parallels and have only OSX and Bootcamp and try the USB which has the Windows Media+Drivers to boot from? On my rMBP, I do have VMware, but when booting from the W7 USB stick, I do get the option to repair.

Do you have a second Mac?

Do you see the Bootcamp volume in Finder? If yes, can you check "Get Info" on the volume? See the text which says "You can only read" at the bottom.

Here is an example.

WarthogARJ Author

Level 1

8 points

Sep 26, 2014 8:04 AM in response to Loner T

Only one Mac.

Yes I can see the BootCamp partition in Finder.

Get Info says:

Created July 14 2009

Format: NTFS

Capacity: 89.35 GB

Available: 10.53 GB

Sharing & Permissions: You can only read

When you say "remove Parallels", do you mean (temporarily) delete/rename Parallels.desktop.app?

Like rename app to apk or something?

In fact I used to have VMWare but changed over to Parallels, but that was a while ago.

I don't think that caused any issues: it was before I changed to Mavericks.

Incidentally, I want to be able to boot up into BootCamp to run some resource intensive software if I need to.

At the moment I can live with access via Parallels.

Repairing Boot Camp after upgrading to Mavericks: Jarvis