Bootcamp won't start after OS X EL update.

Question

Level 1

0 points

Bootcamp won't start after OS X EL update.

I have been running a hybrid MBR to use Bootcamp for several years. With each upgrade - Mavericks, then Yosemite - I used GPT Fdisk to repair the MBR.

When I tried to do this after upgrading to El Capitan I found that GPT Fdisk will not install under OS X EL.

I originally set up the hybrid MBR because I wanted to save my Mavericks partition in case I wished to go back to the older style of icons and desktop.

That is no longer the case and I deleted the Mavericks partition.

This is frustrating since Bootcamp is still in Finder and it appears in Startup. I can access all the files and folders in Windows 10 from Finder.

It appears my only option is to remove and reinstall Bootcamp in a new partition.

Last login: Sat Oct 3 10:11:12 on console

Richards-MacBook-Pro:~ wrburgman$ diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS MacBook HD 433.3 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 60.0 GB disk0s4

Richards-MacBook-Pro:~ wrburgman$ diskutil cs list

No CoreStorage logical volume groups found

Richards-MacBook-Pro:~ wrburgman$ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060

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 977105059

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

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

847898472 12019864

859918336 117186560 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

977104896 131

977105027 32 Sec GPT table

977105059 1 Sec GPT header

Richards-MacBook-Pro:~ wrburgman$

Anyone have any other ideas?

Rick Burgman

MacBook Pro (Retina, 13 inch, Late 2012

Processor 2.9 GHz i7

8GB 1600 MHz DDR3

OS X El Capitan 10.11

Posted on Oct 3, 2015 9:38 AM

Reply

Answer 1

Loner T

Level 9

59,471 points

Oct 3, 2015 11:50 AM in response to Rick Burgman

Rick Burgman wrote:

When I tried to do this after upgrading to El Capitan I found that GPT Fdisk will not install under OS X EL.

ELC has something called SIP (System Integrity Protection) which disallows installation of GPT Fdisk. Boot into local Recovery (Command+R), and then from Utilities -> Terminal run

csrutil disable

Boot normally and install GPT Fdisk. Test and verify.

Reply

Answer 2

Rick Burgman Author

Level 1

0 points

Oct 3, 2015 2:06 PM in response to Loner T

Thanks for your response.

Sorry for being such a Noob. I can follow your explicit instructions well but can't get "csrutil disable" command to run in Terminal on System Restore. Probably because I don't use Linux.

Reply

Answer 3

Rick Burgman Author

Level 1

0 points

Oct 3, 2015 3:38 PM in response to Rick Burgman

I tried every iteration of 'csrutil disable' in Terminal (Recovery mode)

I never get a confirmation that SIP is disabled and GPT Fdisk won't install.

Did Apple disable the ability to turn off SIP in non-beta El Capitan?

When I check csrutil status in Terminal (normal mode) after reboot SIP is always enabled.

At least I don't have anything important on my Windows partition so deleting it and reinstalling will be my next step

Reply

Answer 4

Loner T

Level 9

59,471 points

Oct 3, 2015 4:06 PM in response to Rick Burgman

Can you post a screen shot of the command sequence from the Recovery console? If your Recovery HD is not functional, Internet Recovery will not allow it to be changed.

Reply

Answer 5

menneke

Level 1

8 points

Oct 5, 2015 9:29 AM in response to Rick Burgman

I found the following way around the SIP problem: open the GPT Fdisk package with a package opener (like Pacifist e.g.) and then drag the individual binaries into /usr/local/bin (or sbin if you prefer). These are not protected, unlike the default /usr/sbin where the installer wants to move them. Make sure that you set those locations in your $PATH if they aren already.

Reply

Answer 6

Misty171

Level 1

0 points

Nov 29, 2015 7:39 AM in response to Rick Burgman

Make sure Bootcamp isn't locked in Startup Disk after the update

Reply