I would just give it up and return that drive then install a SATA II drive that is known to work. Unless you are doing a lot of work with huge data files, you won't notice the difference with a SATA III drive anyway.
I would just give it up and return that drive then install a SATA II drive that is known to work. Unless you are doing a lot of work with huge data files, you won't notice the difference with a SATA III drive anyway.
I would just give it up and return that drive then install a SATA II drive that is known to work. Unless you are doing a lot of work with huge data files, you won't notice the difference with a SATA III drive anyway.
Plus the SATA II upgrade over your old HDD is still HUGE!
Just return it and get a Crucial M4. Save some change and headache.
I just installed a 256MB M4 and it gave me a major headache, although I solved the constant beachballs and freezing it now runs blazing fast and stable.
The M4 came with firmware 2 which I then upgraded to the lastest version 9. It was still freezing almost constantly. So I done a PRAM reset (about 4 or 5 cycles) and a SMC reset, now it is giving me absolutely zero problems and is very stable and fast.
So... after a long time of having the same issues, I've decided to see how the SSD works in the Optibay. So I swapped the HDD and the SSD.
Well it works! No hang ups!! It's just a little slower though, which sucks because of the reduced link speed. It just bites that the Optical drive is only 3 gigabit.
Don't know how long I'm gonna live with this, but I'm happy that there's no more hangs. I just wish I could come to a better conclusion as to what was causing the problem.
There's so many factors it could be to honest. This is a newer drive and firmware plays a big role in drive stability. The new Sandforce drives are know to have problems though, you can get more insight into this on the OCZ forums.
Definitely. I just wish they wouldn't have struck a deal with Sandforce so they could get first exclusivity... it's so dumb because really it just screws those who really need the updates. That's the world for ya.
Kingston kept telling me it's not the firmware... I believe it is, but I'm just going off what they told me.
It's up to you what you choose but the M4s are solid, you bought a SATA III drive to use it for those speeds. I'd just return it, the Crucial runs on a Marvell chip which seems to be the sweet spot for the MBPs SATA III Controller. Another thing about firmware is you want to go with a company that has a proven track record of producing firmware updates. OCZ and Crucial are strong performers in that category.
This is not true. The Crucial M4s have exactly the same problems as all the other SATA III drives.
I agree, it's not the SSD but Apple. Crucial M4 had also problems and they released a fw update.
I am also experiencing the same issues with a OCZ Vertex 3 and have searched the web far and wide for solutions/discussions about this shortcoming. Many forums have pointed out that it is indeed a hardware related issue, something about the graphics card switching (sandy bridge). Initially some sources pointed out it was a cable issue, and they had released a replacement cable/foil addon, to which I installed, and found no fix. I am now firmly believing that it is indeed a hardware issue.
refer to here:
https://discussions.apple.com/thread/3137488?start=0&tstart=0
and also here:
http://www.ocztechnologyforum.com/forum/showthread.php?89970-A-call-to-all-Macbook-Pro-2011-Users-with-SATA3-Issues
Unfortunately this problem is widespread across all SATA3 SSD's, and the fact that Apple claims to support the technology but doesn't have an active SATA3 SSD out in the market, favours the problem. I believe they are releasing a SATA3 in the future, but as of now all SATA3 SSD's are experiencing the lagging/beachball/stuttering issue. And to add salt to the wound, Apple is not admitting the issue (some say because Apple doesn't want to damage their reputation, and also wishes to minimize the financial burden of having to replace the affected).
Some people have communicated with Apple over the phone, and geniuses (of whom are aware of the problem, but deny it) and have had their logic board replaced (most probable culprit) after reproducing the problem.
I am extremely frustrated with Apple since this (2011 MBP + SSD) is my first foray into the MAC OSX world coming from 20 years of PC usage. There are days where my MBP is working wonders, and then there are days where constant freezing/beachballing occurs. Sadly, I am going to have to clone my SSD over to a 7200 HDD, and in the meantime, wait for a solution to which Apple has become ignorant over.
I think we need to be represented on a larger scale as the SSD userbase + 2011 MBP is rather small, especially since this only affects SATA3 SSD's.
Unfortunately this problem is widespread across all SATA3 SSD's, and the fact that Apple claims to support the technology but doesn't have an active SATA3 SSD out in the market, favours the problem.
Apple doesn't support SATA3, no where on the specs does it say SATA3.
I have lots of these "_FCMIGUserCanLogin failed with error 268451843" errors, with associated freezes (about a minute each) like you describe, on a 2009 MBP with a Seagate Momentus XT hybrid drive on Lion (no such problems on SL).
What I found is that when I force the rebuild of the spotlight index (there are many ways to do it, using Onyx is one of the simplest) they go away and the computer becomes usable again. They would eventually reappear after some time, and the same remedy helps.
It's been too short to fully confirm this, but I suspect that what may trigger those problems is when I'm away from my desk for a longer time, and the computer goes for a couple of days without a proper TM backup. The new backup mechanism introduced with Lion (the one that writes to /Volumes/MobileBackups) may be to blame in a weird interaction with some HDD controllers.
I think that the more people there are that actually report the problem to Apple, just by calling them or something, the more likely they'll address the problem some point soon. They won't fix it if there's only very few people reporting it.