7 Replies Latest reply: Nov 11, 2013 5:36 PM by LowLuster
dmare Level 1 Level 1 (30 points)

We are an enterprise requiring a homogeneous SOE environment, currently ours is based on Mac OS X 10.8.5 running on 15" MacBook Pros.

 

When the new lineup of macbooks were released just a week or two ago, we could no longer buy hardware that our SOE would be supported on, but experimented with these:

  • 13-inch: 2.5GHz MacBook Pro
  • 15-inch: 2.0GHz with Retina display and 16Gb RAM

 

We placed the laptops in target disk mode and used Disk Utility to firstly create an image of the current states of the "Macintosh HD" partitions on the HDDs, then used the restore tab to copy our SOE image to the new laptops' "Macintosh HD" partitions.

 

This worked perfectly well on on the new 13" MBP - booted fine - works just as well as previous models - no problems.

 

The 15" retina model, however, does NOT boot.  We simply get the folder with a question mark sign.  We were expecting this though, so no surprises.

 

Next, we decided to put Mavericks back on by restoring the previously created backup image of "Macintosh HD" partition to the "Macintosh HD" partition of the retina 15" 's HDD using Disk Utility, however, it still wouldn't boot - same folder with a question mark sign.

 

This is unexpected - it obviously means Disk Utility makes some changes to other sections of the HDD instead of just the partition specified in the GUI...  I'd like to know what exactly this is.

 

Since then we've tried all kinds to get it working, including:

  • Restoring again to each "Macintosh HD" and HDD root using different image to before - one that was created in Disk Utility of the original state of the top level HDD of the 15" HDD instead of the image of the original state of the Macintosh HD partition.
  • Internet Recovery (command-R) - loads for about half an hour then says: "apple.com/support   Error -2101F"
  • Booting from USB created on another Mavericks machine (Downloaded Mavericks from App Store, then created USB using DiskMaker X
  • Truly zero'ing low level (dd if=/dev/zero of=/dev/disk4) - let it go for about 600Mb, then tried USB boot again - same problem.
  • Tried internet recovery again after above zeroing using dd - same -2101F error.
  • Tried PRAM reset (holding down option-command-p-r when booting), then above again - same errors.

 

Not sure what to do next and I don't understand why previous attempts haven't worked.  What hidden stuff does Apple put into Disk Utility and HDD formats, etc...?  I know for one the "Recovery Partition" doesn't show up in Disk Utility - not sure how Apple implements its command-R recovery thing?

 

Anyone have any clues or ideas or able to offer any more information that might assist?


MacBook Pro with Retina display, OS X Mountain Lion (10.8.5)
  • 1. Re: New 15" retina MacBook Pro won't boot
    LowLuster Level 6 Level 6 (11,905 points)

    Try Command + Oprion/Alt + r keys at startup and hold them down until you see a globe on the screen.

     

    That is for the Real Online Internet Recovery system. What you booted into, using Command + r, was the built in Recovery HD partition whcih more than likely got overwritten with an older version when you image the drive.

     

    Once the system load from over the internet, you need to connect to a WiFi network, use Disk Utility to Repartition the drive as One Partition to wipe out everything on the drive, including the old recovery HD partition.

     

    Then reinstall OS X.

  • 2. Re: New 15" retina MacBook Pro won't boot
    dmare Level 1 Level 1 (30 points)

    Ok, just got it booted again by doing this:

     

    Truly zero'ing low level (dd if=/dev/zero of=/dev/disk4) - let it go for about 600Mb, then tried USB boot again - same problem.

    Use Disk Utility to create a partition on it.

    Restore original image of "Macintosh HD" onto newly created partition.

     

    Now it boots into Mavericks fine.

     

    Not marking as solved yet - still trying to figure out why previous attempts wouldn't work, i.e. what other stuff does Disk Utility do to the disks when restoring an image to a partition - obviously it doesn't limit changes to that partition?  Also keen to find out how the Recover mode (command-R) works - is it an actual separate partition or is it simply a folder on the "Macintosh HD" partition?  If it's an actual separate partition in the GPT table, why doesn't it show up in Disk Utility?

     

    Next test will be to zero the disk again, create a new partition again using Disk Utility, then putting 10.8.5 image on the newly created partition again to see if it works this time after zero'ing the disk... will report on findings in case anyone is looking for similar answers.

  • 3. Re: New 15" retina MacBook Pro won't boot
    dmare Level 1 Level 1 (30 points)

    Thanks LowLuster,

     

    It was saying that it was entering Internet Recovery, so I assumed that if command - R recovery failed, it defaulted over to Internet Recovery - this is what it indicated on the screen, however, my assumption might be wrong and I guess it might possibly be different to the command + option / Alt + r keys.

  • 4. Re: New 15" retina MacBook Pro won't boot
    LowLuster Level 6 Level 6 (11,905 points)

    Really don't you read. Repartition the drive as one partition. Do NOT Erase, Repartition as one partition. Use the Partition tab. Select the top entery in the left panel, the drive model number and size, and One partition from the partition Layout drop down.

  • 5. Re: New 15" retina MacBook Pro won't boot
    LowLuster Level 6 Level 6 (11,905 points)

    Did you see a Globe in the center of the screen? If you didn't it was not the Online Internet Recovery system.

  • 6. Re: New 15" retina MacBook Pro won't boot
    dmare Level 1 Level 1 (30 points)

    Yes, I did see the spinning Globe in the center of the screen as does the internet recovery tool usually show, so seems command-R fails back to internet recovery if it can't boot from recovery partition.

  • 7. Re: New 15" retina MacBook Pro won't boot
    LowLuster Level 6 Level 6 (11,905 points)

    Right. Problem is with every new Mac version that comes out Apple take weeks to update the Online servers for these new models. The system is handing out its system Code to the server and if that code is not recognized you get an error.

     

    If you plan on returning these system, because they don't work with your corp image, don't worry about doing the reinstall of OS X. Just return them. Apple will sort it out.