Repairing Boot Camp after creating new partition

Can you start a new discussion, since this is marked solved, and post the output of the following OSX Terminal commands (post text if possible)?

diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0

The "sudo" commands will prompt for your password, and it will not be echoed back. You may also see a warning about improper use of "sudo" and potential data loss due to "abuse" of the command.

HI Loner T,

I had start a new discussion. The discussion is below this link:

Boot camp repaired but window crashed after creating new partition

Hope u can help. Thks

I've just made an account to say THANK YOU! I don't know who you are man, but you're a life safer. Your detailed answers are invaluable! I learned something today and I also made it unharmed. Keep up with the great work! 🙂

kopte3 wrote:

I've just made an account to say THANK YOU! I don't know who you are man, but you're a life safer. Your detailed answers are invaluable! I learned something today and I also made it unharmed. Keep up with the great work! 🙂

Thank you. 🙂 . Glad to see some of these scribblings help users. Post a new discussion if you run into any issues in the future.

Do you have any advice for users that got here by making a new partition from unused disk space? My idea was to make a FAT32 partition which i would use as a shared partition on both operating systems. Thanks!

1. On Macs prior to Late 2013 models with Windows 7 or prior BIOS-mode installations, use a shared external disk. Resizing/repartitioning causes problems, due to the use of a Hybrid MBR (http://www.rodsbooks.com/gdisk/hybrid.html). A hybrid MBR is a very fragile construct and breaks very easily as it maps a GPT to a MBR and any changes must be synced.

2. On later Macs, and using EFI Boot for W8+/W10 installations, you can create partitions using Disk Utility. Fusion drives present additional challenges, because DU does not fully support many of the command-line diskutil options.

3. Apple Software Upgrades are unforgiving when partitions get modified and cause data loss and pain and grief. For example, on my 2012 MBP, which started with Lion (10.7), i have had a Hybrid MBR Windows installation (W7 -> W8.1), upgraded to El Capitan (10.11) without any issues. I have broken many a system playing around but they were expendable.

4. If you can, consider buying the 2015 Macs which support UEFI and EFI Boot better than the 2012-2014 models.

I have an iMac (Mid 2011) with El Capitan and W10, so i guess i should be using a shared external disk?

I have another question, but i don't want to go off topic here.

SSD + HDD iMac configuration (with Bootcamp)

Hello Loner T,

I tried following your steps but once I get to the "write" portion, it tells me I don't have permission even though I am the Admin AND I entered the password at the start of the commands. Any help will be greatly appreciated!

1. You may want to start a new discussion to avoid confusion.

2. You have El Capitan, which has System Integrity Protection (SIP) which needs to be disabled.

Use the following steps.

1. Boot into Local Recovery (Command+R) during power up.

2. Run Utilities -> Terminal.

3. Type csrutil disable and press return/enter.

4. Boot normally.

5. Type csrutil status in OSX Terminal and verify that is it disabled. If still enabled, repeat.

Here's the new Discussion: Bootcamp won't boot after adding partition to HDD

I tried to disable the SIP several times. In the Local Recovery, it says I disabled it successfully yet when I check the status it says it is still enabled?

Hi Loner T, I have the same problem as MattTheMedic. It's been a long time since you helped him but can you help me. I follow everything you state but when I get to the "write" command (or "w") I get a message saying fdisk: /dev/disk0: Operation not permitted

Do you know what I can do? I have Mavrick installed in my mac book pro and I have windows on my bootcamp side. I deleted the extra partition I made already and I will not do this again. Can you help me? Please

Oops, I have the same problem as MacTavish_10 not MattTheMedic.

MacTavish_10Jul 25, 2014 8:20 AM

Hi

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

I set up Boot Camp to dual-boot Windows on my MacBook Pro Retina. Everything was fine. And just yesterday Apple released the Yosemite Beta for the public and I wanted to download this and give it a try. After some research, I found that creating a separate partition was the way to go, and so I made another partition.

I wasn't aware that this would affect my Windows partition as I thought it was completely different.

So now, when I boot up, there is no option to boot with Windows. But when I boot the Mac and select Startup Disk, it shows Boot Camp is still there and all my files etc are still there.

I have a 256SSD, 160GB was for the Mac, and I have 90GB set for Windows.

I made the new partition to 40GB (and the Mac was now 120GB).

Then once I completed that part, I restarted my Mac and the Windows boot option was no longer there.

I didn't even install the Yosemite yet. I went to Disk Utility and deleted the 40GB partition that I made.

Now I don't know what to do. I have a lot of important things which are still on my Windows. Is there a way to restore normal Boot Camp functionality?

------

I followed these steps:

1. 1. diskutil list
2. 2. sudo fdisk /dev/<DiskWhereYouHaveInstalledBootcamp>
3. 3. sudo gpt -v -r show /dev/<DiskWhereYouHaveInstalledBootcamp>

sudo fdisk -e /dev/disk0

p

setpid 4

07

flag 4

p

write

y

It may be better to start a new discussion and post details of the current state.

Hi Loner T,

I have the same issue as the original poster, and I'm assuming your string of fdisk commands will work in my case, but I'd like to be sure before destroying something. To not clutter this thread, I've started a new one with the output to the commands you requested. Any chance you could take a look here: Windows Missing from Boot Screen?

Thank you in advance!

jdavidlawence wrote:

Hi Loner T,

I have the same issue as the original poster, and I'm assuming your string of fdisk commands will work in my case, but I'd like to be sure before destroying something. To not clutter this thread, I've started a new one with the output to the commands you requested. Any chance you could take a look here: Windows Missing from Boot Screen?

Thank you in advance!

Posted on your thread.