Grinchpaws

Q: New SSD will not boot internally, only from USB.

I'm trying to install a 480gb Crucial m500 SSD in my late 2011 13 inch macbook pro (i5 2.4 ghz).  I can connect the ssd via usb and format/partition/erase/clone it however I want.  Once it is cloned from my current HD, I can boot from the ssd while it is still connected via the USB port.  If I replace the internal HD with the ssd and attempt to power on the mac, I receive a white screen with a flashing question mark inside of a folder icon.

 

I am running Mavericks and I have erased and cloned the ssd using both super duper and carbon copy cloner.  The ssd is formatted as Mac OS Extended (Journaled).  I am seeing this problem on the Crucial forums where users update the firmware, replace the drive, etc, but the issue persists.  Crucial is stating "I would also recommend contacting Apple about this issue as I personally don't think it's a fault with the SSD."  Here is a link, http://forums.crucial.com/t5/Solid-State-Drives-SSD/MBP-Mid-2010-doesn-t-see-M50 0-960GB-when-installed-in-the/td-p/138529/highlight/false/page/2.

 

PLEASE HELP!

MacBook Pro (13-inch Late 2011), OS X Mavericks (10.9)

Posted on Dec 13, 2013 8:10 AM

Close

Q: New SSD will not boot internally, only from USB.

  • All replies
  • Helpful answers

Page 1 of 7 last Next
  • by Leoboe,

    Leoboe Leoboe Dec 13, 2013 9:13 AM in response to Grinchpaws
    Level 1 (0 points)
    Dec 13, 2013 9:13 AM in response to Grinchpaws

    I have the same problem with my MacBook Pro late 2012, although my OS was still running (with a lot of beachballs).

     

    I found a different discussion where someone brought his MacBook to the AppleStore and got it repaired with a simple new SATA-Connector:

    http://apple.stackexchange.com/questions/99521/macbook-pro-boots-successfully-wh en-using-hard-drive-in-usb-enclosure-but-doesn

     

    This may or may not help. I will either try this or replace the SuperDrive and install the SSD via that connection and hope it will fix the problem.

  • by Linc Davis,

    Linc Davis Linc Davis Dec 13, 2013 9:26 AM in response to Grinchpaws
    Level 10 (208,037 points)
    Applications
    Dec 13, 2013 9:26 AM in response to Grinchpaws

    If you can still boot from the original internal drive, then return the SSD and buy another one that works.

  • by Grinchpaws,

    Grinchpaws Grinchpaws Dec 13, 2013 10:11 AM in response to Linc Davis
    Level 1 (1 points)
    Dec 13, 2013 10:11 AM in response to Linc Davis

    The ssd works fine via usb.  I can browse through, boot from it, etc.  I just can't boot from it when I install it internally.  I've read a few posts on Crucial's site stating that user's problems continued after receiving a replacement drive.  At the same time, it has been proven that the Crucial m500 is compatible with Mac/OSX from user experience and Crucial themselves.

     

    If I can't find a solution that works, I'll return the drive.

  • by Grinchpaws,

    Grinchpaws Grinchpaws Dec 14, 2013 6:40 AM in response to Grinchpaws
    Level 1 (1 points)
    Dec 14, 2013 6:40 AM in response to Grinchpaws

    I started from scratch last night, erasing the SSD and then performing a fresh install of mavericks onto it via USB.  I booted from the SSD via USB multiple times with no problem.  I then replaced the internal HD with the SSD and it won't boot.  I'm still getting a flashing question mark like there is no drive connected.

  • by keg55,

    keg55 keg55 Dec 14, 2013 7:01 AM in response to Grinchpaws
    Level 6 (8,514 points)
    Mac OS X
    Dec 14, 2013 7:01 AM in response to Grinchpaws

    I don't know if you've tried this before, but maybe worth a shot before you try a different brand SSD.

     

    Try installing the SSD internally and then boot from a USB installer of Mavericks. If you don't have one you can use DiskMaker X 3.0.3 which will use the Install OS X Mavericks.app file within the /Applications folder. After creating a USB installer, boot from it and use Disk Utility to format Mac OS Internal (Journaled) and GUID partition table. Install Mavericks to the SSD. I don't know if your SSD is ever seen once it's installed internally.

     

    If the above doesn't work, then I would send it back for a refund to Crucial. I have used Samsung 840 Pro/EVO Series SSDs and Intel 520 Series SSDs without any issues. I think Intel has the 530 Series now.

  • by Leoboe,

    Leoboe Leoboe Dec 14, 2013 7:27 AM in response to Grinchpaws
    Level 1 (0 points)
    Dec 14, 2013 7:27 AM in response to Grinchpaws

    Let's just recap, what you know so far:

     

    You know the Macbook-Logicboard can't be broken because your system, works fine via USB.

    You know the SSD can't be broken, because it runs via USB.

    The SSD doesn't work as soon as you put it in the MacBook.

    So either it's something on the SATA-Controller (which as some computer-technicians told me is very unlikely) or there is something wrong with the drive connector (quite a common problem with the MacBook Pro series).

     

    I would recommend you to visit an Apple-store and suggest replacing the connector (they would most likely do that anyway) or buy one and replace it yourself (mine is already on the way).

  • by clintonfrombirmingham,

    clintonfrombirmingham clintonfrombirmingham Dec 14, 2013 7:34 AM in response to Grinchpaws
    Level 7 (30,009 points)
    Mac OS X
    Dec 14, 2013 7:34 AM in response to Grinchpaws

    I'm almsot 99% certain that your problem lies with a faulty SATA cable. They're widely available (just search for your model and "SATA cable" on eBay or buy from ifixit.com) and very easy to replace.

     

    SSDs are just much more sensitive to a faulty cable than hard drives. So many folks have the same problems that you present and a quick replacement of the cable solves the problem.

     

    Good luck,

     

    Clinton

  • by Grinchpaws,

    Grinchpaws Grinchpaws Dec 14, 2013 1:43 PM in response to clintonfrombirmingham
    Level 1 (1 points)
    Dec 14, 2013 1:43 PM in response to clintonfrombirmingham

    I would love to order a new sata cable and that would fix the problem, but I'm reluctant.  I've tried putting the SSD into an optibay enclosure and installed it in place of the super drive with the same result.  Do you think the problem with the sata cable is that they are both damaged, or that it is just a matter of older specs not working with a newer technology?  AND if this were the solution, I feel like Apple and/or Crucial would come right out and say there might be an issue with certain sata cables.

  • by Linc Davis,

    Linc Davis Linc Davis Dec 14, 2013 3:08 PM in response to Grinchpaws
    Level 10 (208,037 points)
    Applications
    Dec 14, 2013 3:08 PM in response to Grinchpaws

    The cable is not the problem. The drive is the problem. Send it back and order an SSD from Other World Computing.

  • by julienvs,

    julienvs julienvs Feb 21, 2014 5:18 AM in response to Grinchpaws
    Level 1 (0 points)
    Feb 21, 2014 5:18 AM in response to Grinchpaws

    Same here. Anyone else ran into the issue and got it figured out?

  • by BobRz,

    BobRz BobRz Feb 21, 2014 5:26 AM in response to julienvs
    Level 5 (6,115 points)
    Feb 21, 2014 5:26 AM in response to julienvs

    Just chiming in. I have to agree with Clinton. I've helped several people on here with this same issue when upgrading to an SSD, and the SATA cable has been the culprit. I've been running a Crucial flawlessly for 2 years on a 2010 model. As for the optical bay, a Superdrive is MUCH slower with data transfer, so it may not show the problem.

  • by julienvs,

    julienvs julienvs Feb 21, 2014 5:53 AM in response to BobRz
    Level 1 (0 points)
    Feb 21, 2014 5:53 AM in response to BobRz

    Thanks for the info.

    In my case, even booting externaly from my SSD doesn't work. (Though I get to the grey screen and the cursor appears)

    I'm starting to guess it's the drive itself.

  • by BobRz,

    BobRz BobRz Feb 21, 2014 6:04 AM in response to julienvs
    Level 5 (6,115 points)
    Feb 21, 2014 6:04 AM in response to julienvs

    If you can't boot externally with a known good enclosure, then yes... the drive is the likely suspect.

  • by julienvs,

    julienvs julienvs Feb 21, 2014 6:06 AM in response to BobRz
    Level 1 (0 points)
    Feb 21, 2014 6:06 AM in response to BobRz

    I'm now installing a fresh system, will look into the reported firmware issues (it's a Crucial) and will report back here.

Page 1 of 7 last Next