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

Feb 22, 2014 6:24 PM in response to staycoldb

Good point Loner T 🙂


So normally in these situations the only official way to deal with this is to format the drive and re-install everything.

Obviously OSX still boots but I'm assuming that disk utility will refuse to allow you to delete the Bootcamp partition.

Therein lies the problem.

Have a go at that first.


If it doesn't there may be a way to delete the partition with gdisk and to create a new protective MBR.

This may fool OSX into thinking that there was never a Windows installation and it may then allow you to stretch the Macintosh HD back to the full size of the disk again.

Thereby allowing you to start again.


As I say this is not official and I haven't tried it before but it may work.

Feb 22, 2014 8:32 PM in response to Loner T

GPT: 2 409640 80005903 38.0 GiB AF00 Macintosh HD

MBR: AF 1023 254 63 - 1023 254 63 [ 409640 - 79596264] HFS+


These do not agree.



Look again. gdisk reports start and end LBA. fdisk and gpt commands report start LBA and size (not end). If you add fdisk/gpt start and size minus 1 you will get the end LBA which should match gdisk's end value.


What's probably happened here is the resize of the Windows volume stomped on the backup GPT at the end of the disk, which is why the gpt command flaked out, and why gdisk reported the backup GPT was damaged. The MBR #4 entry for Windows is probably correct because the Windows resize utility would have only updated the MBR and only the Windows entry in it. But yes it's weird that it starts at 204806144; I'll guess that the resize utility actually did a resize (shrink) and then moved the resulting volume farther back, ostensibly to make room in front of the Windows partition to grow the OS X volume?


If the GPT is repaired, that will probably cause the tail end of the Windows NTFS volume to be stepped on, just like the reverse happpened in the resize. The NTFS volume might survive but technically it's broken. So in any case this Windows volume really ought to just be nuked and start over and not use Windows resize utilities on Boot Camp'd Macs.

Feb 22, 2014 8:42 PM in response to staycoldb

Realize FAT32 has a file size limit of 2GB. So anything bigger than that is truncated. I forget if OS X warns of this or if the failure to correctly copy is silent.


I haven't read the whole thread but if the GPT has not been repaired yet, then it's possible the NTFS volume is still intact. I don't know why after resizing it wasn't bootable - buggy resize utility? No idea. But if it didn't totally bungle the job, then Windows Startup Repair should fix this. Just don't fix the GPT. It's enough to get Windows booted, and then you can do a backup of that state - I think the Windows included backup utility can do something like this, maybe it only backsup user data. But that might be useful. Another possibility is Winclone which ought to be able to clone the whole thing. The next step would be to lie like a dog, by telling gdisk to make a new hybrid MBR. That way Boot Camp Assistant can hopefully be tricked into thinking that 4th partition is a legit Boot Camp volume and properly delete it. Then you can use Boot Camp Assistant to split your OS X volume yet again to the size you really want, and then use Winclone to restore - it's capable of taking a bigger or smaller source and making it fit into a different sized destination partition.


Maybe Camptune can do this also, but I think it's just a resizing utility, not a cloning utility. And FYI there's an ancient free version of Winclone floating around, that's not what you want. You need to use the current version which is not free but I don't think it's expensive.

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.