Mountain Lion installation bug on (some) late 2012 Macs?

Discussion in 'OS X Mountain Lion (10.8)' started by gnurf, Mar 4, 2013.

  1. macrumors member

    gnurf

    Joined:
    Apr 25, 2011
    #1
    There have been reports of a serious problem installing OS X on the latest models:
    http://www.mactrast.com/2013/02/som...le-to-download-or-install-os-x-mountain-lion/

    Just as I'm about to get a new Mac mini! Hopefully simply re-imaging it with my existing OS will work, and I'm getting a two-drive version so I could put my existing system on the second drive. But if even running the combo updater fails on these, I can't fix any problems from safe boot if the image doesn't work.

    Has anyone here bumped into weird installation problems with a recent model Mac?
     
  2. macrumors 68020

    Joined:
    Jun 15, 2012
    #2
    You shouldn't need to reinstall the OS for the time being. (I've only twice reinstalled OS X in ten years!)

    As for putting your existing installation on a second drive: I'm not sure that's a good idea. The 2012 Macs may use a special build of OS X that includes drivers not in your ML install from an earlier computer.

    I got a 2012 Mini and it Migrated everything from my old iMac. (Logic and Creative Suite needed reinstalling, but apart from that, it was fine.)

    If you bought ML through the App Store before buying your 2012 Mac, then I don't think you get the issue. I think it's only for people who got ML as a result of their Mac purchase.
     
  3. macrumors 68020

    Joined:
    Aug 28, 2009
    #3
    I'm going to have to try that out... *clones current setup to portable hd*
     
  4. macrumors 68040

    xgman

    Joined:
    Aug 6, 2007
  5. thread starter macrumors member

    gnurf

    Joined:
    Apr 25, 2011
    #5
    Developer. I may screw with my system beyond what a normal person considers reasonable :)

    See above - I would also presume (with reasonably good cause) that the beta combo packs also cover other existing Macs than my current one ;)

    My intent is to have a safe system on one drive and experiment on the other internal drive.

    I've got >300 gigabytes of installed software (mainly instruments) which I'd like to not have to chug through with reinstallation. Therefore the great desire to re-image the main system :)

    Yeah, I've got all the cats from my dev account. I suspected the included version might be the cause. But we'll see when I get the new Mac - I'll either be posting miserable results from my current MacBook, or success reports from the new one :)
     

Share This Page