KamiKnazen
Level 1 (2 points)

Q: Bootcamp fails after Yosemite upgrade (Plz help me Loner!)

Hi,

Yesterday I upgraded my MacBook Pro 15" (late 2013) to Yosemite 10.10.5. A couple of hours later I noticed that I couldn't find Bootcamp. It was still there but now under the name "disk0s4". I think I've done my research on these forums but feel the need for your expertise help so I don't screw up.

 

Here are the results of the Terminal commands you've asked others to get:

 

terminal-commands.png

I then fired up Testdisk and went through the steps in the embedded imgur I found in a neighbouring thread. When I got to step 5 in your guide and hit "Analyze" I got a different result than you have in the guide and I don't know how to proceed. I have a clear MS Data partition labelled BOOTCAMP (see image below) which feels good.

 

testdisk-step5.png

What now? Am I clear to proceed with rebuilding GPT4 using your guide and the start/size digits for the Bootcamp partition showing up in both terminal and Testdisk above? Or do I need to dig deeper?

 

I hope I did my homework well. Not used to working with Terminal and grasping this stuff. And I'm very much hoping to get help working this out.

 

Thanks in advance and cheers,

Erik / KamiKnazen

MacBook Pro (Retina, 15-inch, Late 2013), OS X Yosemite (10.10.5), null

Posted on Sep 3, 2015 2:05 AM

by Loner T,Solvedanswer
Loner T Loner T
Level 7 (23,663 points)
Safari
A:

If you notice, your 500Gb is split into 280Gb OSX CS Container, and your Windows is 110Gb, leaving roughly about 100GB missing. The lost NTFS header indicates a size of 200+ GB (GB vs GiB calculations can be confusing a bit). Please use the following steps.


Install GPT Fdisk (aka gdisk).  Leave your Testdisk display and start a new Terminal Window. You need to 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. Please notice the'+' sign in step 8 (this is called offset notation). The text in parentheses is for informational purpose to describe the action being taken. Gdisk has one-character commands except when entering numbers.

 

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. 548554752 ( - Start offset in sectors or the start point for Bootcamp part)
  8. +428550137 ( - 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 10. Accept all other defaults that Gdisk offers. Please see the sample Q&A as an example. These steps can be repeated if you make a mistake before you get to Step 12, otherwise start from Step 1 for these steps. Step 6 has numbers which are typed with a space between the numbers. Please see the sample Q&A before you execute these steps.

  1. Sudo gdisk /dev/rdisk0
  2. P  (Print list of parts)
  3. R  (Recover)
  4. O (print current Hybrid MBR)
  5. H (chooses Hybrid)
  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 current Hybrid MBR)
  12. W (Write the new MBR)
  13. Y (Yes! write the new MBR)
  14. Reboot

 

Here is sample Q&A for this section. Please notice the 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.

Posted on Sep 3, 2015 5:32 AM

Close
KamiKnazen

Q: Bootcamp fails after Yosemite upgrade (Plz help me Loner!)

  • All replies
  • Helpful answers

Previous Page 2 of 4 last Next

  • by PS_STI,

    PS_STI PS_STI Oct 7, 2015 8:44 AM in response to Loner T
    Level 1 (0 points)
    Oct 7, 2015 8:44 AM in response to Loner T

    Hi Loner T,

     

    Answering your question: after the bootup problem, I fixed my OS X booting with Disk Warrior. However, before I created the Disk Warrior bootable drive (USB), I had played with gdisk and might have done something wrong there .

     

    Either way, the "gdisk procedure" does not work for me. Considering I have a lower number o partitions, I only put "2 4" when asked about Partitions numbers to be hybridized and set "4" as the bootable one.

     

    So here is my input:

     

    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. 726679552 ( - Start offset in sectors or the start point for Bootcamp part)
    8. +250425344 ( - 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)

     

    What am I doing wrong?

  • by PS_STI,

    PS_STI PS_STI Oct 7, 2015 8:50 AM in response to PS_STI
    Level 1 (0 points)
    Oct 7, 2015 8:50 AM in response to PS_STI

    I meant: after following the procedure above I did the test and Bootcamp did not show up on the list of startup disks. So I went into the second part of the procedure and entered:

     

    sudo gdisk /dev/disk0

     

    r <enter>        go to the recovery & transformation menu

    h <enter>        create a new hybrid MBR

    2 4 <enter>        add partions 2 and 4 to the MBR

     

    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): <enter>

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

     

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

    Enter an MBR hex code (default 07): <enter>

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

     

    n <enter>        do not protect more partitions

    o < enter>       print (display) the MBR

    w <enter>

  • by Loner T,

    Loner T Loner T Oct 7, 2015 8:59 AM in response to PS_STI
    Level 7 (23,663 points)
    Safari
    Oct 7, 2015 8:59 AM in response to PS_STI

    Can you post the output of

     

    sudo gpt -vv -r show /dev/disk0

  • by PS_STI,

    PS_STI PS_STI Oct 7, 2015 11:26 AM in response to Loner T
    Level 1 (0 points)
    Oct 7, 2015 11:26 AM in response to Loner T

    Screen Shot 2015-10-07 at 19.56.37.png

  • by Loner T,

    Loner T Loner T Oct 7, 2015 11:31 AM in response to PS_STI
    Level 7 (23,663 points)
    Safari
    Oct 7, 2015 11:31 AM in response to PS_STI

    Did you reboot after changing the GPT? Please post the output of

     

    sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C

  • by PS_STI,

    PS_STI PS_STI Oct 7, 2015 11:44 AM in response to PS_STI
    Level 1 (0 points)
    Oct 7, 2015 11:44 AM in response to PS_STI

    Loner T, one more thing: before the whole mess-up with partitions, the EFI partition was not visible in Finder. Now it is.

     

    Also, when I boot into Windows repair mode, open the DOS command prompt and do a directory listing ("dir"), the system gives me the contents of the EFI drive, which indicates that Windows considers the EFI partition to be its C: drive

  • by PS_STI,

    PS_STI PS_STI Oct 7, 2015 11:56 AM in response to Loner T
    Level 1 (0 points)
    Oct 7, 2015 11:56 AM in response to Loner T

    Yes, I did reboot.

     

    Screen Shot 2015-10-07 at 20.45.37.png

     

    PS I have a recent backup of my OS X and also of my Windows partition (using Paragon's Boot Camp Backup software) so I have no problem applying some hard measures to my drive . I would even format my Windows partition now without bothering you, but I am afraid that formatting and restoring using Paragon's BCB will not help and once I format the Bootcamp drive, there will be no way back. So I may even make it worse.

  • by Loner T,

    Loner T Loner T Oct 7, 2015 3:31 PM in response to PS_STI
    Level 7 (23,663 points)
    Safari
    Oct 7, 2015 3:31 PM in response to PS_STI

    The EFI partition may have a Microsoft directory, which contains the BCD and boot logs. You can check the logs for any specific errors.

  • by PS_STI,

    PS_STI PS_STI Oct 8, 2015 2:10 AM in response to Loner T
    Level 1 (0 points)
    Oct 8, 2015 2:10 AM in response to Loner T

    No M$ directory on the EFI partition.

     

    However there is a new thread in this mystery: I started up my system from a separate OS X installation that I keep on an external drive and that systems shows Bootcamp on the list of bootable devices in the System Preferences -> Startup Disk. I thought that my problem was solved, but unfortunately this was not the case - when I booted back again to my main OS X installation located on the internal hard drive, it did not show the Bootcamp drive in the Startup Disk. Of course Windows did not start either.

     

    I tried various combinations of restarting my PC, such as. e.g. setting Bootcamp as the Target Startup Disk when working on the secondary installation and restarting without booting from main OS X installation in the meantime, but nothing worked. So I have a feeling there is a small glitch that prevents my system from properly identifying the actual Windows partition,

     

    One more thing: when I perform the first part of the "gdisk procedure", I noticed that the values shown in step 2 and step 10 are identical, i.e. the whole procedure seems to be not changing anything. Should that be the case?

  • by PS_STI,

    PS_STI PS_STI Oct 8, 2015 2:30 AM in response to PS_STI
    Level 1 (0 points)
    Oct 8, 2015 2:30 AM in response to PS_STI

    One more thing: could it be that the EFI partition that magically showed on the list of drives (before the whole partition problem I could not see it in Finder) is causing all the havoc? When I boot from the external drive, it does not have the EFI partition, so it properly identifies the Bootcamp partition.

     

    I feel like deleting the EFI partition from the main drive using gdisk and seeing what's going to happen .

  • by Loner T,

    Loner T Loner T Oct 8, 2015 6:24 AM in response to PS_STI
    Level 7 (23,663 points)
    Safari
    Oct 8, 2015 6:24 AM in response to PS_STI

    PS_STI wrote:

     

    No M$ directory on the EFI partition.

     

    However there is a new thread in this mystery: I started up my system from a separate OS X installation that I keep on an external drive and that systems shows Bootcamp on the list of bootable devices in the System Preferences -> Startup Disk. I thought that my problem was solved, but unfortunately this was not the case - when I booted back again to my main OS X installation located on the internal hard drive, it did not show the Bootcamp drive in the Startup Disk. Of course Windows did not start either.

    What version of OS X is on the external disk?

     

    I tried various combinations of restarting my PC, such as. e.g. setting Bootcamp as the Target Startup Disk when working on the secondary installation and restarting without booting from main OS X installation in the meantime, but nothing worked. So I have a feeling there is a small glitch that prevents my system from properly identifying the actual Windows partition,

    Your Windows needs Startup Repair based on this behavior.

     

     

    One more thing: when I perform the first part of the "gdisk procedure", I noticed that the values shown in step 2 and step 10 are identical, i.e. the whole procedure seems to be not changing anything. Should that be the case?

    After the initial modifications have been written, the next iteration will show the values as set. Unless you change the values for every iteration, they should be preserved.

  • by Loner T,

    Loner T Loner T Oct 8, 2015 6:25 AM in response to PS_STI
    Level 7 (23,663 points)
    Safari
    Oct 8, 2015 6:25 AM in response to PS_STI

    PS_STI wrote:

     

    One more thing: could it be that the EFI partition that magically showed on the list of drives (before the whole partition problem I could not see it in Finder) is causing all the havoc? When I boot from the external drive, it does not have the EFI partition, so it properly identifies the Bootcamp partition.

     

    I feel like deleting the EFI partition from the main drive using gdisk and seeing what's going to happen .

    The EFI Partition is normally hidden. Various utilities or manual mounting is possible. There will also show up in Disk Utility debug menu. Connect your external disk and post the output of diskutil list.

  • by PS_STI,

    PS_STI PS_STI Oct 8, 2015 7:14 AM in response to Loner T
    Level 1 (0 points)
    Oct 8, 2015 7:14 AM in response to Loner T

    New developments: normally a new install of the OS X fixes some minor problems with partitions. So I upgraded my main installation (the one on the internal SSD) to El Capitan. And - pooof! - Bootcamp disk is visible again as one of the startup disks in my main installation.

     

    However, it does not show up when booting with the "option" key pressed. I though: "cool, I know how to deal with that, gdisk is the answer (the second part of the procedure)". The problem is gdisk does not work under El Capitan . So I am 99.9% sure my Windows will work now, the only problem is I cannot test it, as I cannot run gdisk and mark the 4th partition of my drive bootable.

     

    Did I remember to mention that in the meantime I upgraded to El Capitan also on the secondary installation on the external HD? I didn't? Well, I did upgrade to El Capitan so there is nowhere I can run gdisk from as I have El Captains olny . I have a Disk Warrior bootable USB drive ("DW USB") with an older version of OS X, so can boot from there, but it has the Applications folder locked (password protected) by the DW manufacturer, so I cannot add gdisk there. I also have a Yosemite Time Machine backup disk...

  • by PS_STI,

    PS_STI PS_STI Oct 8, 2015 7:31 AM in response to PS_STI
    Level 1 (0 points)
    Oct 8, 2015 7:31 AM in response to PS_STI

    [UPDATE] I am downloading Yosemite (available in my list of purchases in the App Store) and will try to install it on one of the USB drives. Then install gdisk there and try to fix the partitions on the main drive. We'll see how it goes...

  • by Loner T,

    Loner T Loner T Oct 8, 2015 8:39 AM in response to PS_STI
    Level 7 (23,663 points)
    Safari
    Oct 8, 2015 8:39 AM in response to PS_STI

    PS_STI wrote:

     

    The problem is gdisk does not work under El Capitan . So I am 99.9% sure my Windows will work now, the only problem is I cannot test it, as I cannot run gdisk and mark the 4th partition of my drive bootable.

     

    ELC has System Integrity Protection enabled by default. To disable it temporarily for diagnostics purposes.

     

         a. Boot into Local Recovery. Power down your Mac, power it back up, and hold the Command+R.

         b. Run Utilities -> Terminal

         c. Type csrutil disable

         d. Exit Terminal

         e. Reboot normally.

Previous Page 2 of 4 last Next