shiftynick

Q: Ran 'repair disk' from disk utility, now unable to boot into win8 partition

I made a mistake apparently and ran repair disk on my hd, and now i am unable to boot back into my bootcamp partition.

 

I've included the output from fdisk and gpt that seem to appear in most related posts.

 

Any help would be appreciated!

 

output from:

sudo fdisk /dev/disk0

 

Disk: /dev/disk0          geometry: 30515/255/63 [490234752 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 -  253148464] HFS+       

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

4: 0C 1023 254  63 - 1023 254  63 [ 294922240 -  195311616] Win95 FAT32L

 

 

 

output from:

sudo gpt -r -vv show disk0

 

gpt show: disk0: mediasize=251000193024; sectorsize=512; blocks=490234752

gpt show: disk0: Suspicious MBR at sector 0

gpt show: disk0: Pri GPT at sector 1

gpt show: disk0: Sec GPT at sector 490234751

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

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

  254827640   40094600        

  294922240  195311616      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  490233856        863        

  490234719         32         Sec GPT table

  490234751          1         Sec GPT header

MacBook Pro with Retina display, OS X Mavericks (10.9.1)

Posted on Feb 24, 2014 10:22 AM

Close

Q: Ran 'repair disk' from disk utility, now unable to boot into win8 partition

  • All replies
  • Helpful answers

Page 1 of 3 last Next
  • by Number88,

    Number88 Number88 Feb 24, 2014 10:43 AM in response to shiftynick
    Level 3 (750 points)
    Feb 24, 2014 10:43 AM in response to shiftynick

    Your Windows partition appears to have changed to type code 0C. It was most likely type 07 previously.

    It also appears not to be marked as bootable.

     

    In the GPT output there seems to be a space between partitions 3 and 4.

    I'm guessing here but have you resized a partition since installing Windows with Bootcamp?

  • by shiftynick,

    shiftynick shiftynick Feb 24, 2014 10:50 AM in response to Number88
    Level 1 (0 points)
    Feb 24, 2014 10:50 AM in response to Number88

    Correct, a while back I used Mini Tool to resize the partition with no problem.

     

    The problem started when I tried to run my Parallels VM that is using the bootcamp partition. It had been a while, I think I might have upgraded to 10.9.1 since I had used the VM. It wouldn'tr launch and the suggestion was to use Repair Disk in Disk Utils and now here I am

  • by Number88,

    Number88 Number88 Feb 24, 2014 11:00 AM in response to shiftynick
    Level 3 (750 points)
    Feb 24, 2014 11:00 AM in response to shiftynick

    You've been found out!

    Once Windows is installed via Bootcamp it is not possible to resize any existing partitions nor create any new partitions without problems ensuing. Camptune X can reportedly do this but I did not have success even with that.

     

    Normally the remedy is to remove the Windows installation by using Bootcamp Assistant's "remove Windows" option and starting again. Sometimes it is even necessary to format the drive and re-install OSX too.

     

    In your case it may be possible to get Windows booting again (maybe) but you will always have a section of the drive which is unusable, as you have now.

     

    The possibility of repair was devised, I believe, by forum user Christopher Murphy and this calls for a new hybrid MBR being created using gdisk.

    I can walk you through that process, however, there are no guarantees.

     

    Even if the process works you would be well advised to backup everything you need from the Windows partition then remove the partition as described above then start again.

  • by shiftynick,

    shiftynick shiftynick Feb 24, 2014 11:10 AM in response to Number88
    Level 1 (0 points)
    Feb 24, 2014 11:10 AM in response to Number88

    Everything worked great after the resize for quite a while.

     

    I do have a backup image of my Win8 partition on an external drive form about a month ago which I'm hoping I can just restore to if i can't get anywhere with the partition as is.

     

    Thoughts on that? Would restoring that partition even work, or would the problem still persist?

     

    I'm down with trying Christopher's fix. You mention backup up my windows files before proceeding. How exactly would I do that in this state?

  • by Number88,

    Number88 Number88 Feb 24, 2014 11:14 AM in response to shiftynick
    Level 3 (750 points)
    Feb 24, 2014 11:14 AM in response to shiftynick

    Unless that backup included the disk's MBR it would not be likely to give any better results than you already have.

     

    No, the backing up was to be done later, if we can get it booting again. If that works you would still be better to remove Windows and start again as further problems will be likely in the future.

     

    It's also possible that upgrading to 10.9.1 has over-written the MBR too.

  • by Number88,

    Number88 Number88 Feb 24, 2014 11:35 AM in response to Number88
    Level 3 (750 points)
    Feb 24, 2014 11:35 AM in response to Number88

    To try a repair you would first need to download and install the gdisk package

     

    http://sourceforge.net/projects/gptfdisk/

  • by shiftynick,

    shiftynick shiftynick Feb 24, 2014 1:38 PM in response to Number88
    Level 1 (0 points)
    Feb 24, 2014 1:38 PM in response to Number88

    Ok, got it.

  • by Number88,

    Number88 Number88 Feb 24, 2014 2:47 PM in response to shiftynick
    Level 3 (750 points)
    Feb 24, 2014 2:47 PM in response to shiftynick

    Sorry, I had to go out.

    Ok, open gdisk with the terminal command

    sudo gdisk /dev/disk0

    and enter password

     

    gdisk will open

     

    type v and press enter

     

    Are any errors reported?

  • by shiftynick,

    shiftynick shiftynick Feb 24, 2014 3:13 PM in response to Number88
    Level 1 (0 points)
    Feb 24, 2014 3:13 PM in response to Number88

    No problems found.

  • by Number88,

    Number88 Number88 Feb 24, 2014 3:21 PM in response to shiftynick
    Level 3 (750 points)
    Feb 24, 2014 3:21 PM in response to shiftynick

    Ok good.

    Type r then hit enter

    Then type h and hit enter

     

    You will see a warning that hybrid MBR's are dangerous and flaky. Ignore it.

     

    Below that you will be asked to enter between 1 and 3 partitions to be included.

     

    Type

    2 3 4 and press enter (with the spaces in between each)

     

    You will then be asked if you want to include the EFI partition first in the MBR

    Answer Y and press enter

     

    Each partition number will then appear with certain default values already entered (for start sector, end sector etc)

    Accept these defaults by just pressing enter.

     

    For partitions 2 and 3 the last question asked will be if you want to mark the current partition as bootable.

    Answer N and press enter.

     

    For partition 4 accept defaults for everything but check that partition type code is set to 07 (it probably will be).

     

    When asked if you want partition 4 to be marked bootable answer Y and enter.

     

    Once finished all of that type w and press enter (to write the changes to the disk).

    Confirm with Y when asked.

     

    Once finished type q to quit gdisk and close the terminal.

     

    Reboot holding Alt key and see if Windows shows in the boot menu.

    If it does, try booting it.

  • by shiftynick,

    shiftynick shiftynick Feb 24, 2014 3:25 PM in response to Number88
    Level 1 (0 points)
    Feb 24, 2014 3:25 PM in response to Number88

    After:

     

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

    Enter an MBR hex code (default AF):

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

     

    I get this question:

     

    Unused partition space(s) found. Use one to protect more partitions? (Y/N):

  • by Number88,

    Number88 Number88 Feb 24, 2014 3:27 PM in response to shiftynick
    Level 3 (750 points)
    Feb 24, 2014 3:27 PM in response to shiftynick

    Did you enter 2 3 4 or just 2 ?

  • by shiftynick,

    shiftynick shiftynick Feb 24, 2014 3:28 PM in response to Number88
    Level 1 (0 points)
    Feb 24, 2014 3:28 PM in response to Number88

    '2 3 4'

  • by Number88,

    Number88 Number88 Feb 24, 2014 3:29 PM in response to shiftynick
    Level 3 (750 points)
    Feb 24, 2014 3:29 PM in response to shiftynick

    hmm it could be referring to the free space between partitions 3 and 4, not sure.

    Answer N and press enter.

    Does an entry for partition 3 appear next? If so, carry on as above.

Page 1 of 3 last Next