Repairing Boot Camp after creating new partition

1. I am a bit surprised at the MSR partition. Did you try an EFI boot or a Windows repair?

2. Your fdisk output shows partition #3 as bootable which is atypical, with Recovery HD missing from the MBR.

3. What happens when you select Bootcamp partition from Startup Manager on the OS X side? Does Windows boot correctly?

4. Could you describe the sequence of events which led to the "issue"?

I tried an EFI boot.

Initially i upgraded to Mavericks. I added Windows 8.1 on 500gb factory Macintosh HD with no issues.

I have since replaced this drive with a 128gb SSD and swapped optical drive for caddy including the 500gb HD.

I cloned Mac OS using Carbon Copy inclusive of recovery partition.

I used bootcamp to add 8.1 to the SSD and was able to do so with success. Afterward reformated the 500gb HD into 2 partitions a large one for Mac and a smaller one fore Windows files. Since then i've been unable to boot into Windows.

Within my System Preference > Starup Disk provides the option to boot from Windows Bootcamp but when restarting i get "no bootable disk"

I am able to see Bootcamp in finder, startup disk option and in disk utility. it just doesn't boot.

I have since then been in and out of this thread trying several options including creating a 5th partition and creating the Hybrid disk. I am still unsuccessful in my efforts. Here is what things are looking like now.

Your GPT partition 4, MBR partition 3 is the Bootcamp partition the way it is right now. There is a dd command that will let you look at the contents to see if you have the OS missing or not. You may need to do a Windows Recovery using a CD/DVD/USB to get windows to boot.

Windows Recovery using a usb? are you referring to install disk or a recovery disk?

Still having issues. Any assistance would be much appreciated.

https://discussions.apple.com/thread/5761240

This just saved me so much time in my lab of 22 iMacs setup to dual boot.

Thanks!

Thanks a lot, I spent hours and hours on this issue and you gave me the only solution that works !

Hi Chris,

Would you kindly have a look at this thread for me? Your help would be much appreciated.

https://discussions.apple.com/thread/5860699

Many thanks

Here is the complete step by step detailed article to achieve 2 windows partitions - http://macosxtricks.blogspot.com

Hi,

I have a similar problem; Mavericks wouldn't startup in BootCamp since I upgraded from ML.

I can run Windows 7 installed on it using Parallels Desktop OK though.

But I want the option to bootup into BootCamp (some Windows software I have is resource intensive).

I have MacBook Pro 2012 with SSD 969GB Crucial main drive, a 2nd HDD 1TB (installed in optical bay) and 16 GB RAM.

Mavericks 10.9.1 upgraded from ML.

I run Windows 7 using Parallels Desktop 9 from BootCamp.

I tried to do the same fix that Christopher Murphy suggested using GDisk but it didn't work: I could not boot up at all afterwards; not even in Mac mode.

Got a strange sort of empty flag.....

I think I damaged my Mac partition table....sigh.

I had to reformat my main SSD and re-install from my backups.

I'm not blaming Christopher: obviously something was not suitable or I made a mistake.

I am reasonably competent at using Terminal.

I thought my case was the same as Scotch-Brawth's.

Our maps looked almost identical.

So after my crash I reformated my SSD and reloaded my Mac partition from a CarbonCopyClone backup (I had a choice of CCC or TimeMachine).

And my BootCamp from a Winclone backup.

I've done this in the past, and wasn't expecting problems.

However after that I could not access Windows in BootCamp at all.

Even just from Parallels Desktop.

Remember the problem that I set out to fix was to try to bootup into BootCamp, but I had no problem running Windows with Parallels.

Before my GDisk disaster:

SSD 845 GB Mac start-up

SSD-2 25 GB NTFS (empty)

BootCamp 90 GB NTFS

(I saved diskutil list and sudo gpt of my maps, but no point in posting these since I've reformated since that).

After my GDisk disaster (self-inflicted I'm sure):

(1) First set-up was the same as before: could not access Windows and couldn't see BootCamp as a Startup option

(2) Simplified set-up I have now:

SSD 870 GB Mac start-up

BootCamp 90 GB NTFS

As soon as I went to (2) I got the option to bootup into BootCamp on startup: so obviously my partition scheme before was part of the problem.

This is what my system looks like now:

Last login: Tue Feb 4 14:22:13 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

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

Password:

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

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: 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

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

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

3: AB 1023 31 21 - 1023 118 44 [1699341608 - 1531680] Darwin Boot

*4: BF 1023 133 52 - 1023 70 5 [1700874240 - 174510080] <Unknown ID>

I now have the option on startup (Alt) to boot into Mac, Windows or Recovery.

However Windows (BootCamp) just hangs in the Windows screen.

It gets as far as the Microsoft windows start screen and then just stays there: I left it for several hours.

When booted into Mac, the Mac side works fine, but Parallels cannot access the BootCamp Windows 7 anymore: same problem: gets to Windows start screen and just stays there.

And my feeling is that it SHOULD hace run: after all I had what I thought was a good BootCamp backup using WinClone (I've tried three different versions of winclone backups, including one I KNOW is 100% good).

I've been speaking with Parallels Support but so far no success.

The problem is it's not obvious where the issue lies:

Parallels

Winclone

Apple

Microsoft

In summary I have TWO linked problems:

(1) I used to be able to access the BootCamp Windows 7 using Parallels for Mac Version 9 but it cannot now

And I restored from very good backups.

It SHOULD be able to do it: I was able to before I ran GDisk (and I did my backups BEFORE I did GDisk).

(2) I would LIKE to be able to start-up in BootCamp.

That's my main goal.

But ever since Mavericks upgrade I've had problems.

Some that might be self-inflicted though: I was trying to get fancy and add a 2nd Windows partition (which I've removed now)

So maybe that's part of the reason I had BootCamp start-up issues.

What I have now:

- main SSD partitioned as per above maps

- TimeMachine backups of system before and after my GDisk disaster

- CarbonCopyClone backup of system after I restored it from damaging my Mac partition

- Winclone backups: about six different ones (I know at least 1 of them works for 100% (the earliest one)

Any ideas?

I'm willing to be adventurous and run GPT fdisk again: I'd REALLY like to get the better of this!

Alan Jarvis

Aha!!!

I think I solved it.

I tried a few different WinClone copies of my BootCamp and I got one to work.

But there was some damage to Windows.

I think because Parallels tried to access Windows but the config files were wrong and it just hung.

So by dint of deleting the BootCamp patition and adding it again I managed to get a session that ran Windows enough to do a chkdsk.

And now I can access Windows via Parallels.

I repaired it again with chkdsk /b and now I can access it OK.

I am now going to defrag it and back it up some more before I try to bootup into bootCamp from Startup.

I think I still have a dodgy partition scheme though: nothing has changed from the last time I ran gpt

The phrase "suspicious MBR" does not look good!!

Can you post the output of sudo fdisk /dev/disk0?

In your previous post the 'id' column shows BF for the "*4" partition, but it should be '07' for Bootcamp to work.

Parallels may not care about fdisk, because it already has pointer to the NTFS partition which has bootcamp.

The "suspicious MBR" is expected because you have OSX and Bootcamp on the same disk. (You can read more about MBRs and GPTs here - http://www.rodsbooks.com/gdisk/hybrid.html )

Aha!

I did not know that.

Alans-MacBook-Pro:~ arjarvis_mbp$ sudo fdisk /dev/disk0

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

3: AB 1023 31 21 - 1023 118 44 [1699341608 - 1531680] Darwin Boot

*4: BF 1023 133 52 - 1023 70 5 [1700874240 - 174510080] <Unknown ID>

Please try the steps outlined here - https://discussions.apple.com/thread/4144252?answerId=23681966022#23681966022

This should change the 4th partition to '07'.

Dang and hot diggity razzlefrazzles!!

I need to have TWO Terminal sessons going for this...excellent.

Awesome.

OK: I will make multiple backups of everything, put on my belt AND suspenders, and have a full pot of coffee ready.

In the morning.

Will send an Action Report back.

Thanks for the help!