Scotch_Brawth

Q: Repairing Boot Camp after creating new partition

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

 

After properly setting up Boot Camp to dual-boot Windows on my Mac mini, I decided to test whether or not it was true that creating another partition (a data partition for OS X) would interfere with Boot Camp.  Wikipedia claims it does interfere but without citing a source, whilst the Boot Camp documentation itself only specifies that the disk must be a single partition _prior_ to setup - there's no mention of whether the disk must be _kept_ that way afterwards.

 

I opened Disk Utility, reduced the size of my OS X parition from 420GB to 80GB, and created a new partition in the unallocated space.  Here's how it looks now:

/___sbsstatic___/migration-images/190/19047693-1.png

When I attempted to proceed with the process, I did receive a warning that doing this (and I quote), "may" cause problems with Boot Camp.  Seeing as it was inconclusive, I thought I'd give it a shot - nothing ventured…

 

Of course, it borked Boot Camp, otherwise I wouldn't be posting here.  Whilst OS X boots just fine, the Boot Camp partition now no longer shows up in the Startup Manager, though it does in the Startup Disk prefPane.  If I do attempt to boot into Boot Camp, I receive the following message on a black screen:

No bootable device --- insert boot disk and press any key

The advice given to someone who had this same problem was, "fix your damaged Boot Camp volume."  But I'm at a loss as to how to do that.

 

So, anyone know how to proceed now so that I can keep my partitions as is, whilst fully restoring normal Boot Camp functionality?

Mac mini (Mid 2011), Mac OS X (10.7.4)

Posted on Jul 26, 2012 11:28 PM

Close

Q: Repairing Boot Camp after creating new partition

  • All replies
  • Helpful answers

first Previous Page 79 of 102 last Next
  • by Nuvect,

    Nuvect Nuvect Mar 2, 2014 2:55 PM in response to Loner T
    Level 1 (0 points)
    Mar 2, 2014 2:55 PM in response to Loner T

    The instructions call for you to create a Bootcamp partition using Bootcamp assistant (Winclone needs an appropriately sized partition.) I had to use DiskUtil, but otherwise yes, that is what I tried.

  • by Loner T,

    Loner T Loner T Mar 2, 2014 8:05 PM in response to Nuvect
    Level 7 (24,869 points)
    Safari
    Mar 2, 2014 8:05 PM in response to Nuvect

    Nuvect wrote:

     

    The instructions call for you to create a Bootcamp partition using Bootcamp assistant (Winclone needs an appropriately sized partition.) I had to use DiskUtil, but otherwise yes, that is what I tried.

     

    I have read the following two links.

     

    https://twocanoes.com/winclone/support/migrating-a-boot-camp-partition-with-winc lone-4

    http://twocanoes.com/winclone/support/create-a-boot-camp-partition

     

    Can you check the output of bless --info --verbose on your new MacPro?

     

    Message was edited by: Loner T

  • by Nuvect,

    Nuvect Nuvect Mar 2, 2014 9:25 PM in response to Loner T
    Level 1 (0 points)
    Mar 2, 2014 9:25 PM in response to Loner T

    Loner T wrote:

    Can you check the output of bless --info --verbose on your new MacPro?

     

    Message was edited by: Loner T

    Bless output below:

     

    EFI found at IODeviceTree:/efi

    Current EFI boot device string is: '<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia </string><key>IOPropertyMatch</key><dict><key>UUID</key><string>76471791-9D49-41 66-8B30-6866C5AEFE99</string></dict></dict><key>BLLastBSDName</key><string>disk0 s2</string></dict></array>'

    Boot option is 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080

    Processing boot option 'Mac OS X'

    Boot option matches XML representation

    Found device: disk0s2

    Disk boot device detected

    mount: /

    Mount point for / is /

    GPT detected

    No auxiliary booter partition required

    System partition found

    Preferred system partition found: disk0s1

    Returning booter information dictionary:

    <CFBasicHash 0x7f8aea407de0 [0x7fff794aef00]>{type = mutable dict, count = 3,

    entries =>

              0 : <CFString 0x10cd40e70 [0x7fff794aef00]>{contents = "System Partitions"} = (

        disk0s1

    )

              1 : <CFString 0x10cd41650 [0x7fff794aef00]>{contents = "Data Partitions"} = (

        disk0s2

    )

              2 : <CFString 0x10cd41670 [0x7fff794aef00]>{contents = "Auxiliary Partitions"} = (

    )

    }

     

    finderinfo[0]:     47 => Blessed System Folder is /System/Library/CoreServices

    finderinfo[1]: 2067987 => Blessed System File is /System/Library/CoreServices/boot.efi

    finderinfo[2]:      0 => Open-folder linked list empty

    finderinfo[3]:      0 => No alternate OS blessed file/folder

    finderinfo[4]:      0 => Unused field unset

    finderinfo[5]:     47 => OS X blessed folder is /System/Library/CoreServices

    64-bit VSDB volume id:  0x26D2ABDEBBDDC52F

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 2, 2014 10:05 PM in response to peterjanbrone
    Level 3 (555 points)
    Mar 2, 2014 10:05 PM in response to peterjanbrone

    I am sorry for the confusion.

     

    That's more clear. Your problem isn't partitioning related. I don't know what Mavericks installer did or could have done to cause the problem. So my suggestion is to focus on Windows Startup Repair and bootrec.exe to get Windows XP booting again. The fact you get a logo and a BSOD means that it's at least getting well past the bootloader stage which means I'm not going to be of any help. It's possible the BCD is corrupt, so it's worth going through the longer set of steps of rebuilding the BCD.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 2, 2014 10:12 PM in response to ipecek
    Level 3 (555 points)
    Mar 2, 2014 10:12 PM in response to ipecek

    I need your help, fast!

    I hope it's possible to repair it somehow because of the data on it I wish not to lose...

    Could you guide me through it please?

     

    No doubt it's not your intent to be rude, but asking for free help and asking for it quickly is in fact rude. Plus your data is clearly not that important to you if you're not backing it up, so why should anyone else care about it? Anyway, your case is the easiest type to do a quick fix so you can make a backup. Use fdisk to change the type code for partition 4 from 0C to 07 using the setpid command, and then use the flag command to set the boot flag on partition 4 also. This doesn't fix the large gap of free space you now have. The simplest fix for that is to totally reformat the drive with a single partition, and restore OS X and Windows from backups.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 2, 2014 10:18 PM in response to BobTheFisherman
    Level 3 (555 points)
    Mar 2, 2014 10:18 PM in response to BobTheFisherman

    BobTheFisherman: Saying there's no way to repair it is obviously untrue, and you know this. It just seems like you want to punish people additionally for their bad choices and don't want to bother with the truly tedious explanation of how to repair the problem. But if you don't want to help them, fine, just unsubscribe from the thread. But telling people untrue things isn't good advice. That Apple doesn't provide tools that fix this problem, and in fact provides tools that actually cause the problem in the first place is where most of the ire should be directed.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 2, 2014 10:20 PM in response to Loner T
    Level 3 (555 points)
    Mar 2, 2014 10:20 PM in response to Loner T

    That was to "ipecek".

    Our posts crossed.

     

    This is why I generally ask people to stop posting to this thread, start a new one, and post its URL here. Otherwise it's just encouraging people to thread jack, which isn't good forum ettiquette. But it most just gets really confusing when more than one person is asking for help for different problems in the same thread.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 2, 2014 10:24 PM in response to Nuvect
    Level 3 (555 points)
    Mar 2, 2014 10:24 PM in response to Nuvect

    Your problem isn't a partition problem. The partitions are sync'd. The 4th MBR partition has the proper type code and is flagged bootable. So that points to a bootloader problem, for whatever reason Winclone hasn't restored the MBR boot strap code. Windows Startup Repair ought to be able to detect this, but if it doesn't then the bootrec.exe /FixBoot command ought to do that.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 2, 2014 10:28 PM in response to Loner T
    Level 3 (555 points)
    Mar 2, 2014 10:28 PM in response to Loner T

    The 2000 entry makes me question the MBR.

     

    It's just a gap of blank space less than 1MB, because Winclone likes to align the start of new partitions on 1MB boundaries.

  • by Nuvect,

    Nuvect Nuvect Mar 2, 2014 10:39 PM in response to Christopher Murphy
    Level 1 (0 points)
    Mar 2, 2014 10:39 PM in response to Christopher Murphy


    Christopher Murphy wrote:

     

    Your problem isn't a partition problem. The partitions are sync'd. The 4th MBR partition has the proper type code and is flagged bootable. So that points to a bootloader problem, for whatever reason Winclone hasn't restored the MBR boot strap code. Windows Startup Repair ought to be able to detect this, but if it doesn't then the bootrec.exe /FixBoot command ought to do that.

     

    Unfortunately, Startup Disk refuses to set the volume as a boot volume and it doesn't show when I boot with the option key down, so I can't tell whether Windows will boot or not. Is there a Mac OS X equivalent of bootrec.exe?

  • by ipecek,

    ipecek ipecek Mar 2, 2014 10:58 PM in response to Christopher Murphy
    Level 1 (0 points)
    Mar 2, 2014 10:58 PM in response to Christopher Murphy

    Sorry about that. I didn't mean to be rude, I was just out of my mind when this happened.

     

    I changed the code and set the flag, then I was able to see Bootcamp partition, but I got operating system missing message when tried to boot.

     

    I did the bootrec.exe set of commands, but installation couldn't be found. Booted back to OSX to see if Finder recognized the partition, but it didn't.

     

    Guess the partition is in RAW.

     

    Backup can't help because the things that matter the most were the documents made yesterday, and the day before. Ofcourse, backup was made some time before that.

  • by Nuvect,

    Nuvect Nuvect Mar 3, 2014 12:49 AM in response to Nuvect
    Level 1 (0 points)
    Mar 3, 2014 12:49 AM in response to Nuvect

    I ran across this on the twocanoes site:

     

    It's a walkthourgh on how to set up a bootcamp partition remotely (using command lines.) At one point it shows how to bless a windows partition.

     

    Set the remote Mac to boot from the Windows volume

    1. In ARD, choose your remote Macs, then click UNIX in the toolbar.
    2. Enter bless --device /dev/disk0s4 --legacy --setBoot (replace disk0s4 with the appropriate device if necessary)

     

    So I gave it a shot:

     

    [promptpro:~] prompt% sudo bless --device /dev/disk0s4 --legacy --setBoot

    Password:

    Legacy mode not supported on this system

     

    I think I'm hosed.

  • by Loner T,

    Loner T Loner T Mar 3, 2014 4:33 AM in response to Nuvect
    Level 7 (24,869 points)
    Safari
    Mar 3, 2014 4:33 AM in response to Nuvect

    Christopher Murphy wrote:

     

    So that points to a bootloader problem, for whatever reason Winclone hasn't restored the MBR boot strap code. Windows Startup Repair ought to be able to detect this, but if it doesn't then the bootrec.exe /FixBoot command ought to do that.

    @Nuvect... Did you try this? You will need appropriate CD/USB to boot and repair.

     

    On my system...

     

    bless --info --verbose

    EFI found at IODeviceTree:/efi

    Current EFI boot device string is: '<array><dict><key>MemoryType</key><integer size="64">0xb</integer><key>StartingAddress</key><integer size="64">0xff990000</integer><key>IOEFIDevicePathType</key><string>HardwareMem oryMapped</string><key>EndingAddress</key><integer size="64">0xffb2ffff</integer></dict><dict><key>IOEFIDevicePathType</key><strin g>MediaFirmwareVolumeFilePath</string><key>Guid</key><string>2B0585EB-D8B8-49A9- 8B8C-E21B01AEF2B7</string></dict><dict><key>IOEFIBootOption</key><string>HD</str ing></dict></array>'

    Boot option is 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080

    Processing boot option 'Mac OS X'

    Boot option matches XML representation

    Could not find disk device for string

    Could not find network interface.

    Firmware feature mask: 0xE003FF37

    Firmware features: 0xE003F537

    Legacy mode suppported

    Boot option is a legacy device

    Searching for legacy type 'HD'

    filesystem[0] '/dev/disk0s2' => '/'

    Firmware feature mask: 0xE003FF37

    Firmware features: 0xE003F537

    Legacy mode suppported

    Got IODeviceTree:/rom

    Got start address ff990000

    Got size 1a0000

    Found PCI interconnect in protocol characteristics

    IOGUIDPartitionScheme

    APPLE SSD SM1024F Media

      IOBlockStorageDriver

       IOAHCIBlockStorageDevice

        AppleAHCIDiskDriver

         IOAHCIDevice

          PRT0

           AppleAHCI

            SSD0

             IOPP

              RP05

               AppleACPIPCI

                PCI0

                 AppleACPIPlatformExpert

                  MacBookPro11,3

                   Root

    filesystem[2] '/dev/disk0s4' => '/Volumes/BOOTCAMP'

    Firmware feature mask: 0xE003FF37

    Firmware features: 0xE003F537

    Legacy mode suppported

    Got IODeviceTree:/rom

    Got start address ff990000

    Got size 1a0000

    Found PCI interconnect in protocol characteristics

    IOGUIDPartitionScheme

    APPLE SSD SM1024F Media

      IOBlockStorageDriver

       IOAHCIBlockStorageDevice

        AppleAHCIDiskDriver

         IOAHCIDevice

          PRT0

           AppleAHCI

            SSD0

             IOPP

              RP05

               AppleACPIPCI

                PCI0

                 AppleACPIPlatformExpert

                  MacBookPro11,3

                   Root

    Matching legacy device 'disk0s4'

    Legacy boot device detected

    mount: /Volumes/BOOTCAMP

    Mount point for /Volumes/BOOTCAMP is /Volumes/BOOTCAMP

    GPT detected

    Booter partition required at index 5

    System partition found

    Preferred system partition found: disk0s1

    Returning booter information dictionary:

    <CFBasicHash 0x7fd15340ae50 [0x7fff7c5bff00]>{type = mutable dict, count = 3,

    entries =>

              0 : <CFString 0x10e874e70 [0x7fff7c5bff00]>{contents = "System Partitions"} = (

        disk0s1

    )

              1 : <CFString 0x10e875650 [0x7fff7c5bff00]>{contents = "Data Partitions"} = (

        disk0s4

    )

              2 : <CFString 0x10e875670 [0x7fff7c5bff00]>{contents = "Auxiliary Partitions"} = (

    )

    }

     

    sudo gpt -vv show /dev/disk0

    Password:

    gpt show: /dev/disk0: mediasize=1000555581440; sectorsize=512; blocks=1954210120

    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 1954210119

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

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

      1454210080         992        

      1454211072   499998720      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1954209792         295        

      1954210087          32         Sec GPT table

      1954210119           1         Sec GPT header

     

     

    sudo fdisk /dev/disk0

    Disk: /dev/disk0          geometry: 121643/255/63 [1954210120 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 - 1452530904] HFS+       

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

    *4: 07 1023 254  63 - 1023 254  63 [1454211072 -  499998720] HPFS/QNX/AUX

     

     

    You may want to pose this question on the Winclone Support forum as well. (Also see help for --legacydrivehint).

     

    @Christopher... The 1MB boundary alignment can be confusing.

     

    Message was edited by: Loner T

  • by Loner T,

    Loner T Loner T Mar 3, 2014 4:39 AM in response to Nuvect
    Level 7 (24,869 points)
    Safari
    Mar 3, 2014 4:39 AM in response to Nuvect

    Nuvect wrote:

     

    It's a walkthourgh on how to set up a bootcamp partition remotely (using command lines.) At one point it shows how to bless a windows partition.

    Do you have the original Windows install (without SysPrep) that can be used from the old MP 2008 in target disk mode? I would also check the bless --info on that volume?

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 3, 2014 10:57 AM in response to Nuvect
    Level 3 (555 points)
    Mar 3, 2014 10:57 AM in response to Nuvect

    Mac OS X equivalent of bootrec.exe?

     

    No. It's a Windows tool. It's available on the install media.

first Previous Page 79 of 102 last Next