CineBug

Q: Windows BootCamp Partition gone after Yosemite Upgrade

Dear Loner T

 

Here are the results of the commands. I am not able to see my older Windows Partition after upgrading to Yosemite from Mavericks.

 

Thanks

 

 

commands run#02.jpgcommands run#01.jpg

MacBook Pro

Posted on Nov 8, 2014 12:23 AM

Close

Q: Windows BootCamp Partition gone after Yosemite Upgrade

  • All replies
  • Helpful answers

  • by Loner T,

    Loner T Loner T Nov 8, 2014 5:17 AM in response to CineBug
    Level 7 (24,202 points)
    Safari
    Nov 8, 2014 5:17 AM in response to CineBug

    Can you post text output versions of the following commands, please? The image versions are not easily amenable to cut/paste and calculations.

     

    diskutil list

    diskutil cs list

    sudo gpt -vv -r show /dev/disk0

    sudo fdisk /dev/disk0

  • by CineBug,

    CineBug CineBug Nov 8, 2014 5:24 AM in response to Loner T
    Level 1 (0 points)
    Nov 8, 2014 5:24 AM in response to Loner T

    Thanks Loner T

     

    While trying to solve this I accidentally ran the sudo dd command and I believe the data on disk04 was rewritten as a different partition. I ran this command

     

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


    and when I ran diskutil list this is what I got


    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *500.1 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:          Apple_CoreStorage                         499.2 GB   disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS Macintosh HD           *498.9 GB   disk1

                                     Logical Volume on disk0s2

                                     8DB16C7D-E00D-47A2-B442-946D1404A942

                                     Unencrypted

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk2

       1:                        EFI EFI                     209.7 MB   disk2s1

       2:                  Apple_HFS MBPBackup#1             999.8 GB   disk2s2

     

    the disk2 above is the backup drive, as you can see the label, but the disk1 was created just now. Whats the solution for this?

     

    I will post the results of the commands you asked for windows in a while

     

    Thanks

  • by Loner T,

    Loner T Loner T Nov 8, 2014 5:56 AM in response to CineBug
    Level 7 (24,202 points)
    Safari
    Nov 8, 2014 5:56 AM in response to CineBug

    CineBug wrote:

     

    While trying to solve this I accidentally ran the sudo dd command and I believe the data on disk04 was rewritten as a different partition. I ran this command

     

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

     

    If you used anything other than /dev/null that may cause an issue. If you used "of=" qualifier, it would cause problems as well. If this command was keyed in exactly as it is written, it should only read "if=" and dump the first header block.

     

    CineBug wrote:

     

    the disk2 above is the backup drive, as you can see the label, but the disk1 was created just now. Whats the solution for this?

     

    Disk1 should have been created when Yosemite upgrade was applied. If the dd command was redirected to /dev/disk1, that is a problem that cannot be solved or reversed. It requires an erase and install of Yosemite.

     

    Is /dev/disk2 an external backup drive? If yes, please unplug it. You do not want new backups being created while attempting recovery, which can cause problems.

  • by CineBug,

    CineBug CineBug Nov 8, 2014 6:13 AM in response to Loner T
    Level 1 (0 points)
    Nov 8, 2014 6:13 AM in response to Loner T

    I used the dd command just as I had posted in the earlier query. I did not use the "of" qualifier. You might be right this is the partition created by the Yosemite update. As you might have guessed the Windows problem is on another mac, which is basically used for my office work.

     

    Do you recommend restarting the system on which I ran the dd command?

     

    I will post the results of the commands you have asked for the windows problem shortly.

     

    Thanks a ton for this help

  • by Loner T,

    Loner T Loner T Nov 8, 2014 6:18 AM in response to CineBug
    Level 7 (24,202 points)
    Safari
    Nov 8, 2014 6:18 AM in response to CineBug

    My suggestion would be use the Mac which has the issue to avoid confusion with commands and outputs.

  • by CineBug,

    CineBug CineBug Nov 8, 2014 7:45 PM in response to Loner T
    Level 1 (0 points)
    Nov 8, 2014 7:45 PM in response to Loner T

    Hi Loner T

     

    Here are the results of the commands. Sorry it took so long. I had to get the system from my office and it has taken a while

     

     

    Edifices-MBP:~ edificedesign$ diskutil list

     

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *250.1 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:                  Apple_HFS MAC 125 GB partition    50.3 GB    disk0s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

       4:       Microsoft Basic Data                         125.0 GB   disk0s4

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                                                   *125.0 GB   disk2

    Edifices-MBP:~ edificedesign$ diskutil cs list

    No CoreStorage logical volume groups found

    Edifices-MBP:~ edificedesign$ sudo gpt -vv -r show /dev/disk0

    Password:

    Sorry, try again.

    Password:

    gpt show: /dev/disk0: mediasize=250059350016; sectorsize=512; blocks=488397168

    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 488397167

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

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

       99923248  144333520        

      244256768  244140032      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      488396800        335        

      488397135         32         Sec GPT table

      488397167          1         Sec GPT header

    Edifices-MBP:~ edificedesign$ sudo fdisk /dev/disk0

    Disk: /dev/disk0 geometry: 30401/255/63 [488397168 sectors]

    Signature: 0xAA55

             Starting       Ending

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

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

    1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID>

    2: AF 1023 254  63 - 1023 254  63 [    409640 -   98244072] HFS+       

    3: AB 1023 254  63 - 1023 254  63 [  98653712 -    1269536] Darwin Boot

    *4: 07 1023 254  63 - 1023 254  63 [ 244256768 -  244140032] HPFS/QNX/AUX

     

    Thanks

     

    h

  • by Loner T,

    Loner T Loner T Nov 8, 2014 8:25 PM in response to CineBug
    Level 7 (24,202 points)
    Safari
    Nov 8, 2014 8:25 PM in response to CineBug

    The gap between GPT#3 and GPT#4 indicates an issue with the Yosemite upgrade. You will need to use Testdisk and GPT Fdisk (Gdisk) to find the correct but "lost" NTFS headers. I have been using Yosemite Upgrade Broke Bootcamp as a reference. If you need direct links to Testdisk and GPT Fdisk, let me know.

     

    Was you original installation modified in any way, like manual resizing of Windows, adding/deleting partitions, using OS X Disk Utility to manage Bootcamp in anyway, or using any third-party tools to manipulate the partitions from the Windows side?

  • by CineBug,

    CineBug CineBug Nov 8, 2014 9:41 PM in response to Loner T
    Level 1 (0 points)
    Nov 8, 2014 9:41 PM in response to Loner T

    Hi Loner T

     

    Yes, the problem seems to be between #3 and #4. I do not know what kind of modifications did the user of that system did. I am not aware of that and there is no way to confirm it with him.

     

    Can you run me through the process of using TestDisk and gdisk? I have not used them before. Do I first use TestDisk and later gdisk to modify the partition? I read the reference post and in it you have started in step 1 by using gdisk to delete and later modify the partition number #4. It would be much appreciated if you give me a brief step breakdown

     

    Thanks

  • by Loner T,Helpful

    Loner T Loner T Nov 9, 2014 5:34 AM in response to CineBug
    Level 7 (24,202 points)
    Safari
    Nov 9, 2014 5:34 AM in response to CineBug

    1. Download Testdisk.

    2. Start Testdisk using sudo testdisk /dev/rdisk0.

    3. Ignore the read-only warning for disk, because you are booted from the same disk.

    4. Choose the EFI partition type. Create a new log the first time, append to it if you start Testdisk again, so there is one log which can be analyzed, if necessary.

    5. Usually a quick search does not reveal anything new.

    6. Run a Deeper Search. Pick each individual MS Data entry and look for familiar windows files. In most cases, there should be a "System Volume Information" entry.

    7. The start/end/size triplet is used to recreate the GPT#4 entry.

    8. Gdisk is used to create a new hybrid MBR, as needed.

    9. Reboot and test.

  • by CineBug,

    CineBug CineBug Nov 9, 2014 7:56 AM in response to Loner T
    Level 1 (0 points)
    Nov 9, 2014 7:56 AM in response to Loner T

    Thanks a lot Loner T. I'll run through these steps and let you know

  • by iyune,

    iyune iyune Nov 24, 2014 1:48 PM in response to Loner T
    Level 1 (0 points)
    Nov 24, 2014 1:48 PM in response to Loner T

    Hi Loner T,

     

    I have the same issue

     

     

    My Windows 8.1 partition disappeared after upgrading to Yosemite

     

    here is the link to my post: Windows BootCamp Partition gone after Yosemite Upgrade

     

    Hoping you can help

     

    Thanks