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

Aug 18, 2014 8:01 PM in response to Loner T

Loner T wrote:


Christopher Murphy wrote:


I really should stick to my mantra of making thread jackers start their own thread, to avoid exactly this kind of confusion, so that everyone gets their own thread and no interruptions.


Apologies, Christopher. I mention it every time I see a new request, but some do, some do not. I will try and suggest it a bit more forcefully next time.

Correct, my fault, I apologize.

So I opened a new one here

Aug 18, 2014 9:47 PM in response to Christopher Murphy

Yes. (I removed the CSM-BIOS install last week to play with EFI. I will go back to CSM-BIOS tomorrow, so I can also post the MBR). The machine (13" 2012 MBP) has a single 256GB SSD. You can see disk0s2 and the GPT 2 partition type. All my clean OS X installs show up like this. I will preserve some screens and rebuild this machine from scratch.


diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *256.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 128.7 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Reserved 134.2 MB disk0s4

5: Microsoft Basic Data 126.4 GB disk0s5

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS OSY-MBP13 *128.3 GB disk1

Logical Volume on disk0s2

AFB7276E-51EF-478F-98A1-47D941BD9843

Unencrypted


sudo gpt -vv -r show /dev/disk0

gpt show: /dev/disk0: mediasize=256060514304; sectorsize=512; blocks=500118192

gpt show: /dev/disk0: PMBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 500118191

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 251330040 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

251739680 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

253009216 704

253009920 262144 4 GPT part - E3C9E316-0B5C-4DB8-817D-F92DF00215AE

253272064 246845440 5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

500117504 655

500118159 32 Sec GPT table

500118191 1 Sec GPT header

Aug 19, 2014 5:59 AM in response to Christopher Murphy

DU has a default which upon detecting a SSD/HDD in the machine, creates Fusion drives, but that is not the case here.


diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group ADCAE521-6032-404B-9DDC-951F9D1622ED

=========================================================

Name: OSY-MBP13

Status: Online

Size: 128680980480 B (128.7 GB)

Free Space: 0 B (0 B)

|

+-< Physical Volume A8202798-E4A1-4604-81A7-66E45DCBD599

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 128680980480 B (128.7 GB)

|

+-> Logical Volume Family ADA8D63F-CF2E-43CF-B685-9F67DBC89D78

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

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

|

+-> Logical Volume AFB7276E-51EF-478F-98A1-47D941BD9843

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

Disk: disk1

Status: Online

Size (Total): 128328658944 B (128.3 GB)

Conversion Progress: -none-

Revertible: Yes (no decryption required)

LV Name: OSY-MBP13

Volume Name: OSY-MBP13

Content Hint: Apple_HFS

Sep 5, 2014 2:04 PM in response to Christopher Murphy

Hi Christopher,


Hopefully you can help me, too. I am trying to install Windows 7 via Bootcamp but ran into the same problem that after running Bootcamp and restarting I get the error message "No bootable device --- insert boot disk and press any key".

I am running OS X 10.10 Beta with a DIY Fusion Drive consisting of a 120 GB SSD and a 1 TB HDD. I followed the steps you recommended to the original question but with no luck.


In my case I believe the interesting disk is disk1. Here is the output of the terminal commands you usually ask for:

gpt show: disk1: mediasize=1000204886016; sectorsize=512; blocks=1953525168

gpt show: disk1: Suspicious MBR at sector 0

gpt show: disk1: Pri GPT at sector 1

gpt show: disk1: Sec GPT at sector 1953525167

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 1709658208 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

1710067848 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

1711337384 88

1711337472 242186240 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

1953523712 1423

1953525135 32 Sec GPT table

1953525167 1 Sec GPT header


Disk: /dev/disk1 geometry: 121601/255/63 [1953525168 sectors]

Signature: 0xAA55

Starting Ending

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

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

1: EE 0 0 2 - 1023 254 63 [ 1 - 1711337471] <Unknown ID>

*2: 07 1023 254 63 - 1023 254 63 [1711337472 - 242186240] 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


I am a little confused by this one because all afternoon I saw a different output with 1 and 2 being <Unknown ID>, 3 being Darwin something and 4 MS-FAT, I think.


Here is also the list of my disks:

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *120.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 119.7 GB disk0s2

3: Apple_Boot Boot OS X 134.2 MB disk0s3

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_CoreStorage 875.3 GB disk1s2

3: Apple_Boot Recovery HD 650.0 MB disk1s3

4: Microsoft Basic Data BOOTCAMP 124.0 GB disk1s4

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS FusionDrive *975.5 GB disk2

Logical Volume on disk0s2, disk1s2

FFA13FBC-2001-40B7-8BBB-BE6EECF8AC11

Unencrypted Fusion Drive

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: GRMCPRXFRER_DE_DVD *3.2 GB disk3


Any help would be greatly appreciated!

Sep 5, 2014 11:21 PM in response to Loner T

I thought it might be because of the Beta version but since I could install it on the MacBook also running Yosemite and since there are several forums and YouTube videos about this error message on the internet from before Yosemite (which didn't solve my problem) I don't think it has to do with that. Anyway, I started a new thread here: https://discussions.apple.com/thread/6520991

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.