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 97 of 102 last Next
  • by Loner T,

    Loner T Loner T Aug 19, 2014 5:59 AM in response to Christopher Murphy
    Level 7 (24,845 points)
    Safari
    Aug 19, 2014 5:59 AM in response to Christopher Murphy

    DU has a default which upon detecting a SSD/HDD in the machine, creates Fusion drives, but that is not the case here.

     

    diskutil cs list

    CoreStorage logical volume groups (1 found)

    |

    +-- Logical Volume Group ADCAE521-6032-404B-9DDC-951F9D1622ED

        =========================================================

        Name:         OSY-MBP13

        Status:       Online

        Size:         128680980480 B (128.7 GB)

        Free Space:   0 B (0 B)

        |

        +-< Physical Volume A8202798-E4A1-4604-81A7-66E45DCBD599

        |   ----------------------------------------------------

        |   Index:    0

        |   Disk:     disk0s2

        |   Status:   Online

        |   Size:     128680980480 B (128.7 GB)

        |

        +-> Logical Volume Family ADA8D63F-CF2E-43CF-B685-9F67DBC89D78

            ----------------------------------------------------------

            Encryption Status:       Unlocked

            Encryption Type:         None

            Conversion Status:       NoConversion

            Conversion Direction:    -none-

            Has Encrypted Extents:   No

            Fully Secure:            No

            Passphrase Required:     No

            |

            +-> Logical Volume AFB7276E-51EF-478F-98A1-47D941BD9843

                ---------------------------------------------------

                Disk:                  disk1

                Status:                Online

                Size (Total):          128328658944 B (128.3 GB)

                Conversion Progress:   -none-

                Revertible:            Yes (no decryption required)

                LV Name:               OSY-MBP13

                Volume Name:           OSY-MBP13

                Content Hint:          Apple_HFS

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Aug 19, 2014 8:07 AM in response to Loner T
    Level 3 (555 points)
    Aug 19, 2014 8:07 AM in response to Loner T

    Interesting, I wonder what the advantages are. It makes it impossible, for the moment, to read HFS+ volumes on Linux. And as far as I know, 3rd party HFS+ read/write support for Windows only understands HFS+, and now it needs to understand CoreStorage also or it won't work either.

  • by Loner T,

    Loner T Loner T Aug 19, 2014 8:23 AM in response to Christopher Murphy
    Level 7 (24,845 points)
    Safari
    Aug 19, 2014 8:23 AM in response to Christopher Murphy

    New thread to discuss CoreStorage and W8.1 support - OSX and Bootcamp discussion

  • by dan2784,

    dan2784 dan2784 Sep 5, 2014 1:32 PM in response to Christopher Murphy
    Level 1 (0 points)
    Sep 5, 2014 1:32 PM in response to Christopher Murphy

    Followed your steps 100% and I have to say, thank you so much! Solved the problem with no issues! You shall be receiving points!

  • by dan2784,

    dan2784 dan2784 Sep 5, 2014 1:35 PM in response to dan2784
    Level 1 (0 points)
    Sep 5, 2014 1:35 PM in response to dan2784

    Sorry! You should be receiving points! I messed that up haha!

  • by jon.schneider,

    jon.schneider jon.schneider Sep 5, 2014 2:04 PM in response to Christopher Murphy
    Level 1 (4 points)
    Sep 5, 2014 2:04 PM in response to Christopher Murphy

    Hi Christopher,

     

    Hopefully you can help me, too. I am trying to install Windows 7 via Bootcamp but ran into the same problem that after running Bootcamp and restarting I get the error message "No bootable device --- insert boot disk and press any key".

    I am running OS X 10.10 Beta with a DIY Fusion Drive consisting of a 120 GB SSD and a 1 TB HDD. I followed the steps you recommended to the original question but with no luck.

     

    In my case I believe the interesting disk is disk1. Here is the output of the terminal commands you usually ask for:

    gpt show: disk1: mediasize=1000204886016; sectorsize=512; blocks=1953525168

    gpt show: disk1: Suspicious MBR at sector 0

    gpt show: disk1: Pri GPT at sector 1

    gpt show: disk1: Sec GPT at sector 1953525167

           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  1709658208      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

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

      1711337384          88        

      1711337472   242186240      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1953523712        1423        

      1953525135          32         Sec GPT table

      1953525167           1         Sec GPT header

     

    Disk: /dev/disk1 geometry: 121601/255/63 [1953525168 sectors]

    Signature: 0xAA55

             Starting       Ending

    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]

    ------------------------------------------------------------------------

    1: EE    0   0   2 - 1023 254  63 [         1 - 1711337471] <Unknown ID>

    *2: 07 1023 254  63 - 1023 254  63 [1711337472 -  242186240] HPFS/QNX/AUX

    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     

    4: 00    0   0   0 -    0   0   0 [         0 -          0] unused

     

    I am a little confused by this one because all afternoon I saw a different output with 1 and 2 being <Unknown ID>, 3 being Darwin something and 4 MS-FAT, I think.

     

    Here is also the list of my disks:

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *120.0 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:          Apple_CoreStorage                         119.7 GB   disk0s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk1

       1:                        EFI EFI                     209.7 MB   disk1s1

       2:          Apple_CoreStorage                         875.3 GB   disk1s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3

       4:       Microsoft Basic Data BOOTCAMP                124.0 GB   disk1s4

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                  Apple_HFS FusionDrive            *975.5 GB   disk2

                                     Logical Volume on disk0s2, disk1s2

                                     FFA13FBC-2001-40B7-8BBB-BE6EECF8AC11

                                     Unencrypted Fusion Drive

    /dev/disk3

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            GRMCPRXFRER_DE_DVD     *3.2 GB     disk3

     

    Any help would be greatly appreciated!

  • by Loner T,

    Loner T Loner T Sep 5, 2014 2:52 PM in response to jon.schneider
    Level 7 (24,845 points)
    Safari
    Sep 5, 2014 2:52 PM in response to jon.schneider

    Can you post a new thread with a reference to it here? CoreStorage will allow Bootcamp only on the second disk, unless your use "trickery" to put bootcamp on the SSD.

     

    The fdisk entry has the first entry as everything up to 1711337472.

     

    BTW 10.10 is a beta release with possible bugs.

  • by jon.schneider,

    jon.schneider jon.schneider Sep 5, 2014 11:21 PM in response to Loner T
    Level 1 (4 points)
    Sep 5, 2014 11:21 PM in response to Loner T

    I thought it might be because of the Beta version but since I could install it on the MacBook also running Yosemite and since there are several forums and YouTube videos about this error message on the internet from before Yosemite (which didn't solve my problem) I don't think it has to do with that. Anyway, I started a new thread here: https://discussions.apple.com/message/26554124#26554124

  • by Loner T,

    Loner T Loner T Sep 6, 2014 4:44 AM in response to jon.schneider
    Level 7 (24,845 points)
    Safari
    Sep 6, 2014 4:44 AM in response to jon.schneider

    Hosts will take down any 10.10 threads till it is Generally Available. Please post without references to 10.10.

  • by jon.schneider,

    jon.schneider jon.schneider Sep 6, 2014 7:07 AM in response to Loner T
    Level 1 (4 points)
    Sep 6, 2014 7:07 AM in response to Loner T

    Thank you for the hint. Here is the link to the new thread: https://discussions.apple.com/message/26555252#26555252

  • by marcoac14,

    marcoac14 marcoac14 Sep 7, 2014 2:59 PM in response to Christopher Murphy
    Level 1 (0 points)
    Sep 7, 2014 2:59 PM in response to Christopher Murphy

    Hi Chris,

     

    The post thread is too long and I couldn't read it all but I know you saved many people here =)

     

    I hope you or someone else can give me a hand on this.

    I run OS X 10.9.2 with an SSD which is partitioned. I have OS X and Win 7 via bootcamp. I also use Parallels to run the bootcamp partition when I don't want to restart my computer.

     

    One day I thought I could easily resize my partitions but once I did that, I got my bootcamp ruined and I no longer can boot windows from bootcamp or Parallels.

    However I do access the files from OS X.

     

    Marco-Correas-iMac-3:~ marcoac14$ sudo gpt -r -vv show disk0

    Password:

    gpt show: disk0: mediasize=256060514304; sectorsize=512; blocks=500118192

    gpt show: disk0: Suspicious MBR at sector 0

    gpt show: disk0: Pri GPT at sector 1

    gpt show: disk0: Sec GPT at sector 500118191

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

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

      314593416   28882808       

      343476224  156641280      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      500117504        655       

      500118159         32         Sec GPT table

      500118191          1         Sec GPT header

     

    Marco-Correas-iMac-3:~ marcoac14$ sudo fdisk /dev/disk0

    Disk: /dev/disk0 geometry: 31130/255/63 [500118192 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 -  312914240] HFS+      

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

    4: 0C 1023 254  63 - 1023 254  63 [ 343476224 -  156641280] Win95 FAT32L

     

    Regards,

    Marco

  • by Loner T,

    Loner T Loner T Sep 7, 2014 4:15 PM in response to marcoac14
    Level 7 (24,845 points)
    Safari
    Sep 7, 2014 4:15 PM in response to marcoac14

    Please start a new thread, but it may be easily fixable.

     

    Your GPT#4 and MBR#4 seem to be in sync.

     

    1. Check if NTFS is intact (this should show you "R.NTFS" in the dump).

     

    sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C

     

    2. Using fdisk,

     

    sudo fdisk -e /dev/disk0

    setpid 4

    07

    flag 4

    p

    w

    y

     

    Reboot and test.

  • by marcoac14,

    marcoac14 marcoac14 Sep 7, 2014 5:53 PM in response to Loner T
    Level 1 (0 points)
    Sep 7, 2014 5:53 PM in response to Loner T
  • by gytis90210,

    gytis90210 gytis90210 Sep 14, 2014 7:13 AM in response to marcoac14
    Level 1 (0 points)
    Sep 14, 2014 7:13 AM in response to marcoac14

    Hi, I had a similar issue as the author originally had, however after making the changes suggested in this thread i am no longer able to boot into windows partition, nor I see it from OS X:

     

    Bootcamp partition is no longer visible and bootable

  • by ice1080,

    ice1080 ice1080 Sep 16, 2014 5:39 PM in response to Christopher Murphy
    Level 1 (0 points)
    Sep 16, 2014 5:39 PM in response to Christopher Murphy

    Hi Chris,

     

    I am having a similar issue but do not have five GPT partitions because I deleted the Linux partitions. I originally had set up a triple boot but then didn't really need the Linux side and wanted to reclaim the space. I no longer have the five GPT partitions but still have the "No bootable device..." error. I have a thread here. Any chance you can give me a quick walk through?

first Previous Page 97 of 102 last Next