New SSD will not boot internally, only from USB.

I think i am having the same problem...just tried to add a kingston hyperX 3k and same thing... drive not recognized.. put in the old drive and its recognized... going to try the dual boot thing you did.. will keep you posted

I had the same problem, and my fix didn't involve replacing the SATA cable. I simply swapped the old HDD and new SSD BEFORE cloning. Then, I booted to my old HDD externally and cloned it to my SSD. Then, I just restarted my MBP. It took a little longer to boot the first time, but it got quicker after that. It worked after that.

Another option to consider, instead of cloning the drive immediately. Try doing a fresh install of Mavericks on the new SSD. If you can't do that, you know you have a problem. After the fresh install, clone over the top of it. I noticed the logic board recognizes the new SSD better when a fresh install is done. My HDD had a bunch of errors that were irreparable in Disk Utility, and those errors clone over to the new drive. So, Idecided to just do a fresh install of Mavericks instead of clone my HDD to the new SSD. Noticeable speed increase with a fresh install as opposed to cloning. I just copied my essential files over to the SSD after the fresh install of Mavericks and all of my software.

I hope this helps you!

My MBP is still running fine on the SSD after a month. It appears that the key may be to do the OS install while the drive is mounted internally. SailorT800 did it clean and I did it with a reinstall, but the common element is that the SSD was installed internally when the OS was installed.

iron_mike,

I don't know... I've done it both ways (putting the SSD in the enclosure AND installing the SSD into the internal bay and booting from my old drive in an enclosure) and both methods have worked for me and SHOULD work for either setup.

I'm just glad that you who've had problems have found another solution - I'll put it in my notes.

Clinton

hello from greece ,

i have the same problem , my disk is not ssd , but is the new WD RED NAS disk 1TB , disk boot as external but as internal a take the flashing folder "icon" in boot ...

an i understand the problem is in the cable , so i need to change the cable (i believe that is a apple problem and they must help us for that but any way) , how i know which cable is the right one ? have any code or something else than i must check before order it ? i found 2-3 cables with a little "differences" in the description and i am not sure what to order

thank you very much for the help

Makis

ps to APPLE ,

i cant believe that i buy a computer at 2011 that NOT SUPPORT a new hard drives , how is this possible ? in all other computer around the world just buy a new hard disk and you change it, in APPLE PRODUCTS must prey i dont know where and you must be prepared to handle the most incredible things, things that is "self-evident" for all the world EXCEPT THE APPLE !!! i am very disappointed i believe that is unacceptable and malignity !!!

thanx apple

If you look at the cable connecting it now there should be a number on it. It depends on what macbook you are using.

Live With Gratitude,

Nick Pendergrast, REALTOR®

Sales Associate to Samantha DeBianchi and Featured on BRAVO's Million Dollar Listing Miami.

1.954.616.7926 iPhone/iMessage

1.888.219.4209 Fax

nickpendergrast@gmail.com E-Mail

Visit our website to learn more about Samantha and her team

www.DeBianchiRealEstate.com

Suspect Linc's analysis correct. I have one MacPro3,1 2x2.8GHz Quad Core (8 cores) 14GB Ram (HD 5770) at home, and very very similar issues. Can't yet afford/justify new MacPro. I have another identical machine at work (RAIDed M500 Crucial 480GB) which works perfectly however. Both using M500 Crucials cos cheapest price point to vaste amounts of SSD storage, for making these video editing beasties. I've tried quite a few configurations trust me. Taking out graphics cards, 2560x1440 monitors, eSata adaptors, de-duping Font Book and validating fonts, repairing permissions etc. The 960GB Crucial M500 at home was working fine, until suddenly (maybe Mavericks only) started dying in sleep. Turned off sleep mode and it was fine. It wouldn't reboot when died in sleep. Was running 10.6 & 10.9 on two partitions. Thought maybe partitions problem with a 10.9.3 update or something. So got a new Samsung Pro 840 256GB for 10.6 . Put in an old 1TB HD to SuperDuper across the 960GB SSD. Then single partitioned 960GB (in case that was problem - KISS approach, minimise problem opportunities - log was giving me AHCI storage things). Cloned it back (SuperDuper). Anyway, she's now at least always able to boot up!!! 😉

But I have 3 system drives in there now! 256GB Samsung 840 Pro (spare no expense - the thing has to boot and if top of the range drive doesn't work, then nothing will, if u read widely you see Transcend and other cheap SSDs get this folder with question mark business). Just an hour or two ago had the non-booting issue from the 960GB again, so computer launched from my 1TB but could see Samsung but NOT 960GB at all. Changed Icy Dock adaptor cos had a spare one - updated to newer version in case it's that. I'll try and keep thread updated in case i come to any firm conclusions. My tentative conclusion is not perhaps to depend on a Crucial SSD to boot from. Can't return cos it's many months old before displayed this problem and i still love the vast space it gives me, and cos I've got 4 drive bays (good thing about old Mac Pro's) I'm fine. But all SSDs (even Samsung) seem to get some grumbles, so maybe it's just a batch thing with this modern technology and Mavericks is more twitchy? Apple give their approval only to a few drives, cos of this very thing. Trim has to be bodged via Groths (big up!), but it'll do. Who can afford Apple SSDs. Who would buy Pegasus RAIDs when they can get similar speeds for half the price by my set up above.

Peace to all, increase the knowledge, tis a fine machine. I'm running 10.9.4 and 10.6.8 now. Overall very happy with what i've got for speed. But i've nearly cried and banged my head against wall quite a few times, but as I say same set up at work has caused no problem at all, and never frozen, does a lot more work too - indicating individual drive or system set up - not clean install at home).

T

Awesome , thanks for the tip. Putting the SSD in the Macbook Pro before cloning solved the issue for me

I'm having similar problems.

MacBook Pro 13" early 2011, model ID 8,1.

Tried cloning original internal HDD to USB mounted Crucial M550 1 TB SSD using CCC.

After successful clone installed SSD and on boot question mark in folder icon.

Using USB memory stick installed from a 10.7.5 disk image (existing OS version on HDD).

Successful install and on boot used Setup Assistant to pull the data from the now USB mounted HDD.

Over the next week erratic behaviour on the MBP. Kernel panics, crashes and weird unexpected results where user input resulted in strange interface and output results.

Ordered and replaced SATA cable with Apple branded part. (Some early versions of the cable had soldering issues which resulted in faults, this new part was not one of those.)

Ran DriveDX which reported a UDMA CRC error the details of which suggested cable fault due to errors in communication or power.

Replaced SSD with the HDD.

Ran DriveDX which reported no faults.

Have returned SSD for replacement but am wondering if there is a systemic fault as opposed to individual unit failure because of the number of comments on this and other threads..

simon2010,

I monitor the Crucial user forum religiously and I've read of no systemic failures of the M550 1TB drives (I myself have a 960GB M500) so I think that you actually received a faulty unit. Please let us know the outcome when you replace the drive.

Good luck,

Clinton

Thank you clintonfrom.birmingham.

Installed replacement M550 1 TB.

Formatted, and installed clean version of 10.9.4

Ran DriveDX which reported the identical problem with previous returned M550, a UDMA CRC fault, with 205 errors.

Ran Volitans S.M.A.R.T app which returned a failing flag on the drive with CRC errors, 207 this time.

Installed a 256 GB M4 from a 2012 MBP 15" into the problem machine, the 13" MBP 2011, 8,1, i7, 2.7 GHz.

Ran DriveDX which reported no faults.

Spoke to Crucial who have taken details. Have returned the second M550 and am going to try an M500 986 GB which I have ordered.

My view is that because the SMART apps return no fault with both a mechanical and M4 drive the cable and power connections are good.

BTW ran Apple Hardware Test just to verify RAM ok. No fault returned.

Currently my view is that there must be some kind of issue with the way the M550 communicates with the motherboard given that the replacement drive exhibited the exact same fault with the same number of CRC errors. It's highly unlikely that the two M550's would be defective. (Firmware issue?)

What is strange is after speaking to Crucial it appears that only this specific model has a problem, they have no reports of issues from other users.

I have previously installed an M500 480 GB in a similar MBP, i.e. 2011, 13", 8,1 without apparent problems.

Simon,

You can usually find folks around here!

Actually, yes, most people are 'over it' and just gaining their own free pad (it doesn't seem that high price!). I don't know what I'll do, that, because the family is usually where your powerful finr drive.

fieriments

The initial test could be (and some here are older than others and some haven't Alander, time sharing, things like that! You really can't but help other's - they'll find out come.

Talk soon - call back if you have!

Clinton

I had the exact same problem, and a SATA cable ordered from Amazon (this one http://www.amazon.com/dp/B00KR5QIEU/ref=pe_385040_128020140_TE_3p_dp_1) solved the problem. A cheap solution to a potentially expensive problem.

In my case, my system booted from an external USB, demonstrating that the drive was fine. If you can't do this, then your drive is likely broken.

The SATA cable I replaced looks fine, and I wonder if anyone reading has the equipment to test it and identify the fault. Would be quite interesting.

Hi. I ran into this problem myself, with my MacBook Pro (late 2011) and an MX200 SSD by Crucial (500Gb).

After several iterations of being able to see the disc when connected via USB, and then getting nothing but the question-marked-folder when attempting to boot from the same disc now installed via SATA within the laptop, I found a post on the Crucial Community that, although far fetched but easy, worked perfectly.

Again, I wasn't able to get the MBP to recognize the SSD when installed via SATA... but when, with the same configuration (new SSD connected via the internal SATA cable within the MBP), I started my MBP with the addition of my original HD connected externally via USB, and another backup disk also connected via FireWire800, the MBP booted from the SATA-SSD like if nothing had ever been wrong.

It really makes no sense to me (fair to say, I am quite illiterate in the internal works of computers) BUT IT WORKS!

I'm going to try booting from the original externally to set up the ssd internally. This issue has had me ripping out my hair all day. Working with a mbp 13 mid 2010 on 10.6.8. When ever I try to upgrade it fails at download.