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 39 of 102 last Next
  • by autnagrag,

    autnagrag autnagrag Mar 13, 2013 10:32 PM in response to Christopher Murphy
    Level 1 (49 points)
    Mac OS X
    Mar 13, 2013 10:32 PM in response to Christopher Murphy

    Sorry to have been confusing. I saw that you had asked the fellow above me for the output of those two commands, so to speak, so I offered it as well, without really understanding why. Should I have started a new thread?

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 13, 2013 10:36 PM in response to autnagrag
    Level 3 (555 points)
    Mar 13, 2013 10:36 PM in response to autnagrag

    Yes. Obviously I wouldn't have seen it so if you're trying to get my attention it's worth posting a link in this **** thread with a 1-2 line summary and maybe I'd poke my head in. Too late now, you have a plan to follow.

  • by autnagrag,

    autnagrag autnagrag Mar 13, 2013 10:39 PM in response to Christopher Murphy
    Level 1 (49 points)
    Mac OS X
    Mar 13, 2013 10:39 PM in response to Christopher Murphy

    So, assuming that my boot SSD is /dev/disk0, then I would be erasing slice two or /dev/disk0s2, yes?

  • by autnagrag,

    autnagrag autnagrag Mar 13, 2013 10:49 PM in response to autnagrag
    Level 1 (49 points)
    Mac OS X
    Mar 13, 2013 10:49 PM in response to autnagrag

    The second backup is running right now. I will sleep then wake up. When I wake up I will erase that slice Where now resides my apparently badly corrupted installation of data and Mountain Lion. Then, I presume I will restore or reinstall Mountain lion to that slice, and and then somehow try to restore as much that is good from my backups and the minimum amount that is bad? Do I have the general idea?

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 13, 2013 11:07 PM in response to autnagrag
    Level 3 (555 points)
    Mar 13, 2013 11:07 PM in response to autnagrag

    I would be erasing slice two or /dev/disk0s2, yes?

     

    Well yeah but in Disk Utility it will be the name of your OS X volume.

     

     

    I presume I will restore or reinstall Mountain lion to that slice, and and then somehow try to restore as much that is good from my backups and the minimum amount that is bad? Do I have the general idea?

     

    Hard to say if anything is corrupt and the backup is also corrupt. If there are no errors, it's probably OK. Ideally you'd reinstall Mountain Lion, and update it, then do the restore data only from Time machine. But often that's a PITA to get all settings back to normal. It's easier to just restore the full backup, take a chance. If there's weirdness that tossing preferences doesn't fix, then you can do a "clean" install of the system.

  • by autnagrag,

    autnagrag autnagrag Mar 14, 2013 7:38 AM in response to Christopher Murphy
    Level 1 (49 points)
    Mac OS X
    Mar 14, 2013 7:38 AM in response to Christopher Murphy

    I got no errors using CCC to make either backup.

     

    I have a "utility" boot volume that is "better" than Recovery HD in the sense that I can run CCC or DiskWarrior from it, in addition to the limted set of tools in Recovery HD.

     

    Unless you advise me to boot from Recovery HD, I'll boot from the other volume, erase my current boot volume but not repartition or reformat the whole disk and all its slices. I suppose one would use the restore function from DiskUtility on Recovery HD if using that approach to restore the backup.

  • by berkeley201,

    berkeley201 berkeley201 Mar 14, 2013 8:31 AM in response to Christopher Murphy
    Level 1 (0 points)
    Mar 14, 2013 8:31 AM in response to Christopher Murphy

    Christopher:

     

    I posted the data you reqested. I still have a bootcamp I can't boot into. Is there anything I can do to salvage it?

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 14, 2013 8:36 AM in response to autnagrag
    Level 3 (555 points)
    Mar 14, 2013 8:36 AM in response to autnagrag

    Whatever you used to create the backup is what I'd use to do the restore. Disk Utility uses asr behind the scene and I think can restore from any file based backup (like a .dmg, .iso, .img file).

  • by autnagrag,

    autnagrag autnagrag Mar 14, 2013 10:57 AM in response to Christopher Murphy
    Level 1 (49 points)
    Mac OS X
    Mar 14, 2013 10:57 AM in response to Christopher Murphy

    When I booted from my utility, I could not erase the boot volume with twisted infrastructure. I booted to Recovery HD, erased and erased again the former boot volume, mounted the read-only backup, and restored it to the boot volume with ASR. ASR restored by blocks, or so it said. I used USB3, and the 92GB backup restored to the SSD and verified in 27 minutes.

     

    I could have rebooted into the utility and used CCC to restore, but this seems to have worked.

     

    After boot, Google Drive burped unpleasantly, but I've got TRIM enabled, and have successfully run all the suggested variants of fsck from single user mode, without issue.

     

    Are there any further tests or proofs of integrity you would suggest?

     

    Thank you again!

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 14, 2013 11:31 AM in response to berkeley201
    Level 3 (555 points)
    Mar 14, 2013 11:31 AM in response to berkeley201

    0C 1023 254  63 - 1023 254  63 [ 300509184 -  189724672] Win95 FAT32L

     

    This entry for the MBR is wrong and needs to be fixed. The easiest way is to use fdisk in interactive editing mode. Interactive means you get an fdisk prompt, and commands and data entry are done by typing a single letter or number followed by return.

     

    sudo fdisk -e /dev/disk0

     

    p            [shows the partition listing]

    setpid 4     [set partition type code on partition 4]

    07           [NTFS code]

    flag 4       [set partition 4 as bootable]

    write        [write changes to disk]

    exit

     

    And now you should reboot.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 14, 2013 11:30 AM in response to autnagrag
    Level 3 (555 points)
    Mar 14, 2013 11:30 AM in response to autnagrag

    No.

  • by berkeley201,

    berkeley201 berkeley201 Mar 14, 2013 11:52 AM in response to Christopher Murphy
    Level 1 (0 points)
    Mar 14, 2013 11:52 AM in response to Christopher Murphy

    Christopher:

     

    Thanks! It seemed to work, in the sense that there has been progress. Now when I press 'option' during boot in get Windows as a boot alternative. But when I choose it, I only get a blinking cursor on a black screen

     

    A second issue is the hard drive space I released when I deleted the "MAC Stuff"partion; that space seems to simply have been lost. Can it be reclaimed?

     

       #:                   TYPE NAME                SIZE   IDENTIFIER
       0:  GUID_partition_scheme                    *251.0 GB   disk0
       1:                    EFI                     209.7 MB   disk0s1
       2:              Apple_HFS Macintosh HD        137.9 GB   disk0s2
       3:              Apple_HFS Recovery HD         650.0 MB   disk0s3
       4:   Microsoft Basic Data BOOTCAMP            97.1 GBdisk0s4
  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 14, 2013 11:59 AM in response to berkeley201
    Level 3 (555 points)
    Mar 14, 2013 11:59 AM in response to berkeley201

    The file system problems with the OS X volume need to be repaired first. At the moment the resize command is reporting it can't make the OS X volume larger. Once repaired, it might be possible to resize. If that still doesn't work, it should be possible to merge the two partitions together, but I'm not sure if the Recovery HD partition will also be absorbed since it lies in between the two partitions that need to be merged.

     

    As for Windows, you'll need to boot from the Windows install DVD, and run Startup Repair.

  • by berkeley201,

    berkeley201 berkeley201 Mar 14, 2013 12:35 PM in response to Christopher Murphy
    Level 1 (0 points)
    Mar 14, 2013 12:35 PM in response to Christopher Murphy

    I am not sure what to do with the OS X. I tried to run Startup Repair from the Win DVD, but that didn't work (the program didn't find anything to repair, it said). So I still get a black screen with a blinking cursor when trying to boot to Bootcamp (Win 7).

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Mar 14, 2013 1:09 PM in response to berkeley201
    Level 3 (555 points)
    Mar 14, 2013 1:09 PM in response to berkeley201

    http://support.microsoft.com/kb/927392

     

    After step 7 type:

    /FixMbr

    /FixBoot

    /RebuildBcd

     

    If that doesn't work, the easiest solution is to boot off another disk containing OS X or Recovery HD, repartition the disk back to 1 partition (change Current to 1 partition in the Partition tab), restore from backups. The benefit of this is, it fixes both the HFSJ file system problems as well as the Windows problem.

     

    Otherwise you're in TestDisk disaster recovery terroritory to get anything out of Windows.

first Previous Page 39 of 102 last Next