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 70 of 102 last Next
  • by The Rooks Family,

    The Rooks Family The Rooks Family Feb 10, 2014 12:37 PM in response to Christopher Murphy
    Level 1 (0 points)
    Feb 10, 2014 12:37 PM in response to Christopher Murphy

    Christopher,

     

    Thank you very much.  You have saved my data!  Testdisk worked like a charm and provided me on the past to recovery and being able to boot into my Windows Bootcamp partition.  I truly appreciate everything you have done for us all.

     

    God Bless You,

     

    Laurence

  • by staycoldb,

    staycoldb staycoldb Feb 22, 2014 4:11 PM in response to Scotch_Brawth
    Level 1 (0 points)
    Feb 22, 2014 4:11 PM in response to Scotch_Brawth

    Is that Christopher guy still around here helping people? I just got my macbook pro and have spent the last 4 days configured bootcamp to the way I wanted Windows, I went and tried to extend the bootcamp partition with a windows tool like an idiot.

     

    If anyone around here can walk me through repairing the MBR via terminal I will seriously paypal you some money.

     

    I'm not bad with windows command line but I am a total noob to OSX. Please Help!

  • by Loner T,

    Loner T Loner T Feb 22, 2014 4:17 PM in response to staycoldb
    Level 7 (24,862 points)
    Safari
    Feb 22, 2014 4:17 PM in response to staycoldb

    Do you want to post a new thread with a reference here and the output of the following commands in the new thread?

     

    The assumption is that your OSX and Bootcamp are on the same disk (/dev/disk0). Please use OS X Terminal (found in Applications -> Utilities)

     

    diskutil list

    sudo gpt -r -vv show disk0

    sudo fdisk /dev/disk0

  • by staycoldb,

    staycoldb staycoldb Feb 22, 2014 4:23 PM in response to Scotch_Brawth
    Level 1 (0 points)
    Feb 22, 2014 4:23 PM in response to Scotch_Brawth

    gpt show: disk0: mediasize=320072933376; sectorsize=512; blocks=625142448
    gpt show: disk0: Suspicious MBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: error: bogus map
    gpt show: unable to open device 'disk0': No such file or directory

     

    Disk: /dev/rdisk0    geometry: 38913/255/63 [625142448 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 -   79596264] HFS+       
    3: AB 1023 254  63 - 1023 254  63 [  80005904 -    1269536] Darwin Boot
    *4: 07 1023 254  63 - 1023 254  63 [ 204806144 -  420335616] HPFS/QNX/AUX

     

    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *320.1 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            40.8 GB    disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data BOOTCAMP                278.5 GB   disk0s4

  • by Loner T,

    Loner T Loner T Feb 22, 2014 4:28 PM in response to staycoldb
    Level 7 (24,862 points)
    Safari
    Feb 22, 2014 4:28 PM in response to staycoldb

    For the GPT command, please try

     

    sudo gpt -r -vv show /dev/disk0

  • by staycoldb,

    staycoldb staycoldb Feb 22, 2014 4:31 PM in response to Loner T
    Level 1 (0 points)
    Feb 22, 2014 4:31 PM in response to Loner T

    Ok, this is precisely the output I got:

     

    gpt show: /dev/disk0: mediasize=320072933376; sectorsize=512; blocks=625142448
    gpt show: /dev/disk0: Suspicious MBR at sector 0
    gpt show: /dev/disk0: Pri GPT at sector 1
    gpt show: error: bogus map
    gpt show: unable to open device '/dev/disk0': Undefined error: 0

  • by Loner T,

    Loner T Loner T Feb 22, 2014 4:33 PM in response to staycoldb
    Level 7 (24,862 points)
    Safari
    Feb 22, 2014 4:33 PM in response to staycoldb

    It is strange to see such an error which makes me suspicious of the GPT. Please try

     

    sudo gpt -r -vv show /dev/rdisk0

  • by staycoldb,

    staycoldb staycoldb Feb 22, 2014 4:41 PM in response to Loner T
    Level 1 (0 points)
    Feb 22, 2014 4:41 PM in response to Loner T

    It's more or less returning the same result:

     

    gpt show: /dev/rdisk0: mediasize=320072933376; sectorsize=512; blocks=625142448

    gpt show: /dev/rdisk0: Suspicious MBR at sector 0

    gpt show: /dev/rdisk0: Pri GPT at sector 1

    gpt show: error: bogus map

    gpt show: unable to open device '/dev/rdisk0': Undefined error: 0

  • by staycoldb,

    staycoldb staycoldb Feb 22, 2014 4:48 PM in response to Scotch_Brawth
    Level 1 (0 points)
    Feb 22, 2014 4:48 PM in response to Scotch_Brawth

    I can install team viewer if you wanna remote in and run some commands to see the status of the MBR and parttion table. I don't mind. Just want this fixed. Seriously dreading the thought of having to wipe the hdd and start over.

  • by Loner T,

    Loner T Loner T Feb 22, 2014 4:49 PM in response to staycoldb
    Level 7 (24,862 points)
    Safari
    Feb 22, 2014 4:49 PM in response to staycoldb

    There is another utility called gdisk (http://sourceforge.net/projects/gptfdisk/?source=dlp) which may be worth looking at, otherwise testdisk is one of last resort.

  • by Loner T,

    Loner T Loner T Feb 22, 2014 4:51 PM in response to staycoldb
    Level 7 (24,862 points)
    Safari
    Feb 22, 2014 4:51 PM in response to staycoldb

    staycoldb wrote:

     

    I can install team viewer if you wanna remote in and run some commands to see the status of the MBR and parttion table. I don't mind. Just want this fixed. Seriously dreading the thought of having to wipe the hdd and start over.

    Please do not invite a total stranger on the internet (who you have known for less than 10 minutes) to remote into your system. Just for your safety and mine as well.

  • by staycoldb,

    staycoldb staycoldb Feb 22, 2014 4:58 PM in response to Loner T
    Level 1 (0 points)
    Feb 22, 2014 4:58 PM in response to Loner T

    LOL, ya I know. But I know enough to know if they're doing something suspect. Let me check out these tools and I will post back...

  • by Loner T,

    Loner T Loner T Feb 22, 2014 5:00 PM in response to staycoldb
    Level 7 (24,862 points)
    Safari
    Feb 22, 2014 5:00 PM in response to staycoldb

    Once you install the utility, here is an example from my system. Please try it with both /dev/disk0 and /dev/rdisk0.

     

    sudo gdisk /dev/disk0

    Password:

    GPT fdisk (gdisk) version 0.8.9

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: hybrid

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with hybrid MBR; using GPT.

     

    Command (? for help): ?

    b          back up GPT data to a file

    c          change a partition's name

    d          delete a partition

    i          show detailed information on a partition

    l          list known partition types

    n          add a new partition

    o          create a new empty GUID partition table (GPT)

    p          print the partition table

    q          quit without saving changes

    r          recovery and transformation options (experts only)

    s          sort partitions

    t          change a partition's type code

    v          verify disk

    w          write table to disk and exit

    x          extra functionality (experts only)

    ?          print this menu

     

    Command (? for help): p

    Disk /dev/disk0: 1954210120 sectors, 931.8 GiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 6ED0C429-00D1-4759-B50E-04B6FB80D0E3

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 1954210086

    Partitions will be aligned on 8-sector boundaries

    Total free space is 1293 sectors (646.5 KiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640      1452940543   692.6 GiB   AF00  Customer

       3      1452940544      1454210079   619.9 MiB   AB00  Recovery HD

       4      1454211072      1954209791   238.4 GiB   0700  BOOTCAMP

     

    Command (? for help): q

  • by Number88,

    Number88 Number88 Feb 22, 2014 5:02 PM in response to Scotch_Brawth
    Level 3 (750 points)
    Feb 22, 2014 5:02 PM in response to Scotch_Brawth

    I think the MBR is good but the GPT doesn't look well.

    There's an option in gdisk to load the MBR and build a fresh GPT from it - sadly I've never used it and don't know whether that would help you.

    It could be an option.

  • by staycoldb,

    staycoldb staycoldb Feb 22, 2014 5:03 PM in response to Loner T
    Level 1 (0 points)
    Feb 22, 2014 5:03 PM in response to Loner T

    Okay T Loner, is gdisk an alternative cmd line tool to Terminal? I have it installed, but what is the default install location for it? Like I said, I am so new to OSX so forgive my ignorance.

first Previous Page 70 of 102 last Next