Windows 7 bootcamp partition not bootable after updating to 10.10.3

Can you use Bootcamp partition missing after yosemite installation as a reference and get started with a Testdisk scan? The gap between GPT3 and GPT4 is most likely where you will find a lost NTFS header.

Initial Testdisk UI steps are shown here - https://imgur.com/a/PjmnK.

You are looking for a MS Data entry in Testdisk which looks similar to the following when you use 'P - List Files'.

The following table shows what you should have.

Can you post the output of

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0

Leave your Testdisk display and start a new Terminal Window. Please use the following steps. If you see any error messages during the following steps, please stop and post back here with the error message. The following steps have values from your Testdisk output (and you can verify) in Steps 7 and 8.

Rebuild GPT4 using start/end offsets

1. Sudo gdisk /dev/rdisk0
2. P (print the full list of parts)
3. D (delete)
4. 4 (part 4)
5. N (new part)
6. 4 (part 4)
7. 148150272 - Start offset in bytes (start point for Bootcamp part)
8. +342083577 (Size offset as opposed to End offset)
9. 0700 (Windows part type)
10. P (print list of all parts just to see what changes will be made)
11. W (Write the new GPT)
12. Y (Yes! really write the new GPT)

This will delete and re-write the GPT partition info for /dev/disk0s4.

Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes). The only values that need modifications are the Boot flags and step 7. Accept all other defaults that Gdisk offers.

1. Sudo gdisk /dev/disk0
2. P (Print list of parts)
3. R (Recover)
4. H (chooses Hybrid)
5. O (Print current MBR)
6. Partitions numbers to be hybridized: 2 3 4
7. Y (Good for GRUB question)
8. N (part 2 boot flag)
9. N (part 3 boot flag)
10. Y (part 4 boot flag make NTFS bootable partition)
11. O (Print updated MBR)
12. W (Write the new MBR)
13. Y (Yes! write the new MBR)
14. Reboot

Here is a sample Q&A for the second set of Gdisk steps. Please make sure you see Press Enter/Return .

Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y

Creating entry for GPT partition #2 (MBR partition #2)

Enter an MBR hex code (default AF): Press Enter/Return

Set the bootable flag? (Y/N): N

Creating entry for GPT partition #3 (MBR partition #3)

Enter an MBR hex code (default AB): Press Enter/Return

Set the bootable flag? (Y/N): N

Creating entry for GPT partition #4 (MBR partition #4)

Enter an MBR hex code (default 07): Press Enter/Return

Set the bootable flag? (Y/N): Y

Test 1 - Does Bootcamp Volume show up in Finder?

Test 2 - Can you see files in Bootcamp Volume?

Test 3 - Can you select Bootcamp in System Preferences -> Startup Disk?

Test 4 - If Test 3 is successful, select Bootcamp and Click Restart.

If Yosemite upgrades stay clean, you should not need this again.

Hi Loner T,

This happened again when I upgraded to El Capitan! ****! I wish I understood why Apple would not make sure this doesn't happen but it has so I've got to fix it.

One question. Unlike the previous times, the Bootcamp partition passes all of the three tests but still will not boot. Do I still have to follow the procedure described above or is there a shortcut to just setting it as bootable? I think I already know the answer but I'll await confirmation.

BTW, I did use the system prefs startup disk tool to set it as bootable and when I restart it gives me the "no bootable device found..." message.

Jeff

Can post the output of the same commands on a new discussion, to avoid confusion?

Ok, I get command not found on gdisk so it's not installed. I also don't have Testdisk. Where are these found?

I'm a little confused because I had to add a bunch of command line tools and I have the app store command line tools for xcode but I now they're not here.

I wish I could find the email or the site from the last time this happened. It was all sequential including the installation of the needed command line programs.

If GPT Fdisk was installed then

type gdisk

gdisk is /usr/sbin/gdisk

If Testdisk was downloaded, it should be in the Downloads directory, or the designated directory where you saved it.

I just wanted to pop in here and update this thread with some important information.

First of all there is a problem installing GPT fdisk because it tries to put the binaries in /usr/sbin which is now off-limits to third party binaries. The developer is working on a new version that will put them in /usr/local/bin but I don't have a hard date. You can also get the source and compile it yourself but that is beyond me and the scope of this thread I believe.

The other issue is that El Capitan has a new "feature" called System Integrity Protection which does not allow gdisk to do anything useful. It needs to be disabled for gdisk to work. Here is an article about it:

http://osxdaily.com/2015/10/05/disable-rootless-system-integrity-protection-mac- os-x/

Finally, in case any of this doesn't sound familiar, it's because it's the result of me using this NERDr.com post because it worked like a charm for me before.

http://nerdr.com/bootcamp-partition-lost-repairing-mac-partitions/

The author took the (then) 45 page Apple support forum thread and distilled it down to the steps you see. All I know is it saved me a TON of time and he deserves any praise he can get. Unfortunately, it doesn't look like he's done anything on that site since 2014.

Before anybody does anything I will tell you again that I am in the process of using this tutorial again and can't verify that it works with the current version of OS X. I'll be happy to follow up after I've done it to let you know how it's gone.

Fair?

Jeff

gronesy wrote:

First of all there is a problem installing GPT fdisk because it tries to put the binaries in /usr/sbin which is now off-limits to third party binaries. The developer is working on a new version that will put them in /usr/local/bin but I don't have a hard date. You can also get the source and compile it yourself but that is beyond me and the scope of this thread I believe.

The other issue is that El Capitan has a new "feature" called System Integrity Protection which does not allow gdisk to do anything useful. It needs to be disabled for gdisk to work. Here is an article about it:

http://osxdaily.com/2015/10/05/disable-rootless-system-integrity-protection-mac- os-x/

/usr/local/bin also has similar issues. It addresses installation issues, but not execution issue. Fdisk built-in has the same issue, and it is part of OS X and already installed in /usr/sbin.

Finally, in case any of this doesn't sound familiar, it's because it's the result of me using this NERDr.com post because it worked like a charm for me before.

http://nerdr.com/bootcamp-partition-lost-repairing-mac-partitions/

The linked article is irresponsible and causes data loss. You cannot and must not sync the GPT and overwrite MBR. Quite a few third-party partitioning/resizing tools do not understand GPT vs MBR and and cause problems. Some that do (like iPartition) cause other issues by re-ordering entries in the MBR. Unless the user sitting behind the keyboard understand both constructs, it usually causes data loss.