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.

Repairing Boot Camp after creating new partition

I'm running OS X 10.8 and Windows 7 x64 Pro.


After properly setting up Boot Camp to dual-boot Windows on my Mac mini, I decided to test whether or not it was true that creating another partition (a data partition for OS X) would interfere with Boot Camp. Wikipedia claims it does interfere but without citing a source, whilst the Boot Camp documentation itself only specifies that the disk must be a single partition _prior_ to setup - there's no mention of whether the disk must be _kept_ that way afterwards.


I opened Disk Utility, reduced the size of my OS X parition from 420GB to 80GB, and created a new partition in the unallocated space. Here's how it looks now:

User uploaded file

When I attempted to proceed with the process, I did receive a warning that doing this (and I quote), "may" cause problems with Boot Camp. Seeing as it was inconclusive, I thought I'd give it a shot - nothing ventured…


Of course, it borked Boot Camp, otherwise I wouldn't be posting here. Whilst OS X boots just fine, the Boot Camp partition now no longer shows up in the Startup Manager, though it does in the Startup Disk prefPane. If I do attempt to boot into Boot Camp, I receive the following message on a black screen:

No bootable device --- insert boot disk and press any key

The advice given to someone who had this same problem was, "fix your damaged Boot Camp volume." But I'm at a loss as to how to do that.


So, anyone know how to proceed now so that I can keep my partitions as is, whilst fully restoring normal Boot Camp functionality?

Mac mini (Mid 2011), Mac OS X (10.7.4)

Posted on Jul 26, 2012 11:28 PM

Reply
1,534 replies

Nov 28, 2012 8:54 AM in response to Scotch_Brawth

My problem seems parallel with this thread. I am hoping a smarter person than I on this thread can lend a hand.


I have dual boot MacPro5,1. OS X 10.7.5 on one HDD, WIN7 on the other HDD. I went to clone my "MASTER" WIN7 to another drive. Unfortunately the "ALT" drive was not clean, it had a copy of WIN7 as well. My computer booted into this "ALT" WIN7 and scrodded my "MASTER" WIN7. I can no longer boot into my "MASTER" WIN7, even when I remove "ALT" WIN7 drive. It seems like something changed on the "MASTER" WIN7. Something with it's boot record or flag. It seems awefully close to the problems in this thread.


Here are the outputs from the various commands:


macpro_09:~ scorp$ sudo gpt -r -vv show disk3

Password:

gpt show: disk3: mediasize=500107862016; sectorsize=512; blocks=976773168

gpt show: disk3: MBR at sector 0

start size index contents

0 1 MBR

1 62

63 468840897 1 MBR part 7

468840960 1536

468842496 507926528 2 MBR part 7

976769024 4144




macpro_09:~ scorp$ sudo fdisk /dev/disk3

Disk: /dev/disk3 geometry: 60801/255/63 [976773168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

*1: 07 0 1 1 - 1023 254 63 [ 63 - 468840897] HPFS/QNX/AUX

2: 07 1023 254 63 - 1023 254 63 [ 468842496 - 507926528] HPFS/QNX/AUX

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused



macpro_09:~ scorp$ sudo gdisk /dev/disk3

Password:

GPT fdisk (gdisk) version 0.8.5



Partition table scan:

MBR: MBR only

BSD: not present

APM: not present

GPT: not present





***************************************************************

Found invalid GPT and valid MBR; converting MBR to GPT format.

THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if

you don't want to convert your MBR partitions to GPT format!

***************************************************************





Command (? for help):

Nov 28, 2012 9:40 AM in response to mncrnich

After spending a good hour reading this entire thread, I found a solution which worked! Thank you Christopher Murphy.


"

It's important to use chkdsk again with /f because the journal may say the file system is clean when it isn't. So give /f a shot and see what happens.


Next read this. You may have to click on the link to show more information. It's not exactly clear what order they want you to try this in, I would do the following three in order all at once, then try a reboot.


/FixMbr

/FixBoot

/RebuildBcd


If those don't work, then I'd try this:


bcdedit /export C:\BCD_Backup

c:

cd boot

attrib bcd -s -h -r

ren c:\boot\bcd bcd.old

bootrec /RebuildBcd

"


That did it.

Nov 28, 2012 4:28 PM in response to Christopher Murphy

when i type


"sudo gdisk /dev/disk0s2"


its giving me the error again:


"sudo: gdisk: command not found"



But anyways thank you for your help. I've learnt more about gpt and mbr's.

I have temporatily solved the problem by installing rEFIt. I can now boot windows from partition 4 😀


This is enough for me so I am just goin got keep it like this for now.


Again thanks for your help 😀

Nov 29, 2012 7:36 PM in response to Christopher Murphy

Hey


I'm having a similar problem as everyone else in this posting. I have 5 partitions. 3 of which I created for my Mac OS Lion installation, Windows 7 installation and a 3rd for storage. Everything was running fine for quite sometime until recently. My Windows 7 installation has suddenly stopped booting. Instead of a start up screen I get:


Windows failed to start. A recent hardware or software change might be the cause.

File: \BOOT\BCD

Status: 0xc000000d

Info: An error occurred while attempting to read the boot configuration data


Mac OS Lion starts up fine. I'm unable to mount my "Bootcamp" partition nor the "Storage" partition. On top of that "Storage" has been renamed to "disk0s5". When I installed Windows 7 it didn't recognize the "Storage" partition that was created in Lion so it merged what it thought was free diskspace (I'm assuming the same space that Mac OS recognized as Storage) to the Root Drive of Windows 7 (Bootcamp).


Are you able to assist?

Nov 29, 2012 8:02 PM in response to KJFMusic

It doesn't seem similar to everyone else's problem in the thread at all. The error you're getting is totally different. And everyone else experienced their problem right after creating a new partition, while you're saying your problem suddenly spontaneously developed. You wouldn't get this error message if there were partition problems, so you probably need to start out with Windows Startup Repair.

Nov 30, 2012 12:32 AM in response to KJFMusic

Guys...I have experience the same with you all. I make partition on my macbook. then I make partition using disk utility.after that. I can not boot on my wndows.
I already install gdisk,xquartz (trying to do the resulution in page 1), but, actually I dont know what is that.
Could u explain again step by step.
Thanks.
I do this all in my macbook pro I bought last month.

Nov 30, 2012 12:32 AM in response to Christopher Murphy

Guys...I have experience the same with you all. I make partition on my macbook. then I make partition using disk utility.after that. I can not boot on my wndows.

I already install gdisk,xquartz (trying to do the resulution in page 1), but, actually I dont know what is that.

Could u explain again step by step.

Thanks.

I do this all in my macbook pro I bought last month.

Repairing Boot Camp after creating new partition

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