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 52 of 102 last Next
  • by SumnerRain,

    SumnerRain SumnerRain Oct 25, 2013 11:13 AM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 25, 2013 11:13 AM in response to Christopher Murphy

    At the very first screen, when you chose the drive (after chosing to make a log file or not), shoulnd't there be more than one media?  Yesterday I had two.  Nevermind, I should be chosing "sudo" right?

     

    Screen Shot 2013-10-25 at 11.07.35 AM.png

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 25, 2013 11:22 AM in response to SumnerRain
    Level 3 (555 points)
    Oct 25, 2013 11:22 AM in response to SumnerRain

    Stop.

     

    This screen says rdisk1. The previous results you gave for fdisk and gpt used rdisk0, why is there a difference?

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 25, 2013 11:24 AM in response to SumnerRain
    Level 3 (555 points)
    Oct 25, 2013 11:24 AM in response to SumnerRain

    Post the results from the command diskutil list

  • by SumnerRain,

    SumnerRain SumnerRain Oct 25, 2013 11:29 AM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 25, 2013 11:29 AM in response to Christopher Murphy

    TestDisk will try to restart itself using the sudo command to get
    root (superuser) privileges.

     

    sudo may ask your user password, it doesn't ask for the root password.
    Usually there is no echo or '*' displayed when you type your password.

     

    TestDisk 6.14, Data Recovery Utility, July 2013
    Christophe GRENIER <grenier@cgsecurity.org>
    http://www.cgsecurity.org
      [Restored]
    Last login: Fri Oct 25 11:25:38 on ttys000
    Macintosh:~ Heather$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *750.2 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            600.0 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data                         75.3 GB    disk0s4
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            Sims3EP10              *4.7 GB     disk1
    Macintosh:~ Heather$

  • by tomd007,

    tomd007 tomd007 Oct 25, 2013 12:50 PM in response to ava_Jack
    Level 1 (0 points)
    Oct 25, 2013 12:50 PM in response to ava_Jack

    Hello ava_jack,

     

    I might be comming back to you late, but if you haven't solved the problem, here are the initial steps:

     

    In order to know how to preceed, we need to know the current status of your partitions. So go to terminal and type the following:

     

    sudo fdisk /dev/rdisk0

    sudo gpt -r -v show /dev/rdisk0

     

    these commands will only work if you have already downloaded and installed "gdisk" available here: gdisk

     

    You might also need (for later) to donwload "TesDisk" available here: http://www.cgsecurity.org/wiki/TestDisk_Download

     

    Let me know the current status of your computer and what have you done so far so as I can try en see how I can help.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 25, 2013 12:51 PM in response to tomd007
    Level 3 (555 points)
    Oct 25, 2013 12:51 PM in response to tomd007

    fdisk and gpt commands are included in OS X and are not a part of gdisk so they can be run before doing anything else.

  • by SumnerRain,

    SumnerRain SumnerRain Oct 25, 2013 12:57 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 25, 2013 12:57 PM in response to Christopher Murphy

    Here is my screenshot for when I chose "sudo".

     

    Screen Shot 2013-10-25 at 12.54.14 PM.png

  • by tomd007,

    tomd007 tomd007 Oct 25, 2013 1:01 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 25, 2013 1:01 PM in response to Christopher Murphy

    well - when I first tried, Terminal didn't recognise the commands, so that I had to download that software and then it worked well. I don't know why it was like that in my case.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 25, 2013 1:06 PM in response to SumnerRain
    Level 3 (555 points)
    Oct 25, 2013 1:06 PM in response to SumnerRain

    choose the 2nd one, /dev/rdisk0

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 25, 2013 1:08 PM in response to tomd007
    Level 3 (555 points)
    Oct 25, 2013 1:08 PM in response to tomd007

    could be that there was a bungled search path for your user which was fixed when gdisk was installed. fdisk and gpt have been installed since the dawn of OS X.

  • by SumnerRain,

    SumnerRain SumnerRain Oct 25, 2013 1:14 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 25, 2013 1:14 PM in response to Christopher Murphy

    Disk0 and rdisk0 yielded the same results.  The missing partition is #4, right?  I just need the start and end numbers for the [bootcamp] before moving on to gdisk steps, correct?  Sorry if I am being a pain, I just want to make sure I don't eff this up.

     

    Screen Shot 2013-10-25 at 1.10.19 PM.png

  • by tomd007,

    tomd007 tomd007 Oct 25, 2013 1:21 PM in response to Christopher Murphy
    Level 1 (0 points)
    Oct 25, 2013 1:21 PM in response to Christopher Murphy

    Hi Chriss, is there a way I can give you points for all your help? - I don't know how to do it.

  • by Csound1,

    Csound1 Csound1 Oct 25, 2013 1:25 PM in response to tomd007
    Level 9 (51,161 points)
    Desktops
    Oct 25, 2013 1:25 PM in response to tomd007

    tomd007 wrote:

     

    Hi Chriss, is there a way I can give you points for all your help? - I don't know how to do it.

    Anf Chris certainly deserves them but unfortunately points can only be awarded by the poster that started the thread.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 25, 2013 2:01 PM in response to SumnerRain
    Level 3 (555 points)
    Oct 25, 2013 2:01 PM in response to SumnerRain

    No, that's not the correct information. Maybe tom or frank can speak up about how they got testdisk to scan the disk for their missing volume. What your screen shot shows is the quick scan (I think), which has grabbed the information from either the MBR or GPT, which has the wrong information. So if you plug these values into gdisk, you'll be plugging in the same values it already has. (So you won't make things worse, but it won't fix it either.)

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Oct 25, 2013 2:46 PM in response to SumnerRain
    Level 3 (555 points)
    Oct 25, 2013 2:46 PM in response to SumnerRain

    OK I just set this up in qemu/kvm to test it out.

     

    sudo ./testdisk /dev/rdisk0

     

    I get a menu and can use arrow keys to choose a media, there is only one, and the "button" down below is  proceed. So I just hit enter.

     

    The partition table type default is EFI GPT so I choose that.

    The Analyze option is the next default, so I choose that. So far I've only chosen defaults.

     

    Now it shows me a list of partitions, one of which I know is wrong. The default here is Quick Search so I choose that also. It immediately lists three things while continuing to analyze cylinder with a countdown, but the 3rd item is already the missing volume I'm looking for. But it's continuing to scan.

     

    So depending on the drive size, it might take a while longer than it did for my test (a tiny 8GB virtual disk) to find the NTFS volume you're after. And it might have more than one it proposes, only one is correct. Once it's done, you'll have a list and can highlight entries with the up/down arrow key. Highlight one and type P for "list files". If that's the wrong possibility, it'll probably say something like "can't open file system. filesystem seems damaged." So quit to back up, down arrow key to try the next suggestion. Then type P again.

     

    Finally, instead of "can't open file system" I get a folder structure that looks like the folders/files I'm looking for. Right above this are three numbers which are the start, end, and size values. You can also backup with quit, and see the most recent selection you chose, and this time there are column heading (kinda nice) that correspond to those same values.

     

    So the values you're after are start and end. They go in gdisk as "First sector" and "Last sector". So give that a shot.

first Previous Page 52 of 102 last Next