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

    Loner T Loner T Jun 10, 2014 3:14 PM in response to JeffJev1741
    Level 7 (24,800 points)
    Safari
    Jun 10, 2014 3:14 PM in response to JeffJev1741

    Would you consider posting a new thread with your issue and a referernce to such a new thread here?

  • by JeffJev1741,

    JeffJev1741 JeffJev1741 Jun 10, 2014 3:23 PM in response to Loner T
    Level 1 (0 points)
    Jun 10, 2014 3:23 PM in response to Loner T

    Sure!

  • by Magiccam,

    Magiccam Magiccam Jun 10, 2014 6:49 PM in response to JeffJev1741
    Level 1 (0 points)
    Jun 10, 2014 6:49 PM in response to JeffJev1741

    You should not have deleted any partions... you only needed to move it. My guess is you will now need to start from scratch. Go to first page of this forum thread. Read, digest, understand and comprehend what is being said.

     

    Don't go deleting partitions willy nilly.

  • by JeffJev1741,

    JeffJev1741 JeffJev1741 Jun 10, 2014 7:15 PM in response to Magiccam
    Level 1 (0 points)
    Jun 10, 2014 7:15 PM in response to Magiccam

    I'm looking for solutions going forward, not critiques of what has already been done.

    Yes you could be right, but who knows.

  • by Loner T,

    Loner T Loner T Jun 10, 2014 8:09 PM in response to JeffJev1741
    Level 7 (24,800 points)
    Safari
    Jun 10, 2014 8:09 PM in response to JeffJev1741

    One "hole" that is a mystery is this entry...

     

    674592688    9211984  

     

    If there is a diskutil/gpt output before any changes were made, it would be helpful. Has a Windows recovery been attempted (using install media) after selecting it to boot either via "Startup Disk" or using the Option key during powerup?

  • by JeffJev1741,

    JeffJev1741 JeffJev1741 Jun 10, 2014 8:26 PM in response to Loner T
    Level 1 (0 points)
    Jun 10, 2014 8:26 PM in response to Loner T

    Unfortunately no, changes were made before finding this thread...

     

    I tried repairing with the install disc but it throws up an error that its the wrong version (could be that the disc is SP1, Windows 7, and the installed version is updated some way).

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Jun 10, 2014 11:06 PM in response to JeffJev1741
    Level 3 (555 points)
    Jun 10, 2014 11:06 PM in response to JeffJev1741

    I'm currently copying from the Bootcamp HD, which I can see when booted into Mac

     

    The fact it mounts in OS X means the GPT is correct and the Windows NTFS volume is intact (mounted read-only I assume). That means most likely this is a bootloader problem and can be fixed with the Windows install media and using Windows Startup Repair.

  • by Christopher Murphy,

    Christopher Murphy Christopher Murphy Jun 10, 2014 11:07 PM in response to Christopher Murphy
    Level 3 (555 points)
    Jun 10, 2014 11:07 PM in response to Christopher Murphy

    If Windows Startup Repair doesn't like it then you'll want to search for the Microsoft technote on bootrec.exe and use that manually.

  • by JeffJev1741,

    JeffJev1741 JeffJev1741 Jun 11, 2014 12:06 PM in response to Christopher Murphy
    Level 1 (0 points)
    Jun 11, 2014 12:06 PM in response to Christopher Murphy

    I didn't even do anything...but it works now! I was booting up to my Windows install DVD to try what you suggested and it went right into Bootcamp. I was able to go back into Mac and re-reboot in Windows, so all is well. Thank you everyone who offered suggestions!

  • by themsbg,

    themsbg themsbg Jun 13, 2014 5:52 PM in response to Christopher Murphy
    Level 1 (0 points)
    Jun 13, 2014 5:52 PM in response to Christopher Murphy

    You are a saviour. For me it was partition 4 not partition 5. But without you, I was about to completely wipe my bootcamp partition and have to restore everything from a backup and reinstall all my software. Thank you thank you thank you.

  • by G0dJohn,

    G0dJohn G0dJohn Jun 14, 2014 1:26 PM in response to Christopher Murphy
    Level 1 (1 points)
    Jun 14, 2014 1:26 PM in response to Christopher Murphy
  • by Puding666,

    Puding666 Puding666 Jun 14, 2014 9:54 PM in response to Christopher Murphy
    Level 1 (0 points)
    Jun 14, 2014 9:54 PM in response to Christopher Murphy

    Hello there. I have a Macbook Pro Retina 15', I created an new partition for the Yosemite but I didn't know it would mess up with my Boot Camp.

    Before I reach to this thread, I had the same issue of the first post (No bootable device --- insert boot disk and press any key), so I just used my bootable flash drive and try to repair the windows, of course its failed and starting showing up a new message error: "An error occurred while attempting to read the boot config data"

     

    Then I made everything like you said, but the windows keeping showing the same error (An error occurred while attempting to read the boot config data).

    What I need to do know?

  • by Puding666,

    Puding666 Puding666 Jun 14, 2014 10:14 PM in response to Puding666
    Level 1 (0 points)
    Jun 14, 2014 10:14 PM in response to Puding666

    Oh, I don't have Yosemite partition anymore, just BootCamp and Main (4 in total).

  • by Gmouse1,

    Gmouse1 Gmouse1 Jun 15, 2014 6:16 AM in response to Puding666
    Level 1 (16 points)
    Mac OS X
    Jun 15, 2014 6:16 AM in response to Puding666

    Test post

  • by Gmouse1,

    Gmouse1 Gmouse1 Jun 15, 2014 6:17 AM in response to Gmouse1
    Level 1 (16 points)
    Mac OS X
    Jun 15, 2014 6:17 AM in response to Gmouse1

    Soooo...coming new to this thread, after reading of it on NERDR.COM.

     

    Have new iMac 27" and have been TRYING to load and use Win 8.1 Enterprise (MSDN) on BootCamp in Mavericks 10.9.3.

     

    Could not even get setup to load until after I removed my three external G-Drives, finally got it to load, and actually got Windows pretty much configured and activated, and loaded Office 2013 and VISIO.  But, I have an increasing number of BSOD (I assume it is) issues with kernel_security_check_failure which stop the computer, nothing works, and I have to power off.  This has caused drive issues, and while I've been repairing them, I can no longer boot into Windows.  Tried repairing that with the original Win 8.1 DVD, but, Automatic Repair can't fix, and I was unsure if using BootRec was a good idea.

     

    So ran the three SUDO commands on my Drive 0, and here are the results:

first Previous Page 87 of 102 last Next