Sign in to follow this  
pcknt

Why did my OWC Extreme SSD die?

Recommended Posts

hi, I had a 115 OWC Mercury Extreme Pro 3g I bought in March 2011. It just died today and the Macbook Pro 13" (2010) would only display a gray screen (no logo) until I pulled it out of the Data Doubler drive bay.

I inserted the SSD into an external drive enclosure but the drive activity light when connected to a MAC and a PC would be constant red and the drive would not show up under disk utility or computer management(PC).

Do you know what might have happened to this drive and is common with Sandforce drives as I have heard?

Thanks.

Share this post


Link to post
Share on other sites

It's not common but we've seen this kind of behavior in the lab. RMA it and be happy that you'll probably get great support from OWC.

Share this post


Link to post
Share on other sites

Sandforce drives can enter a panic mode when a serious error has occurred. When a panic mode is instigated a log file is generated that provides a system snapshot of information that helps to debug the problem. The drive can accommodate 4 panic logs, after that the slots have to be cleared via a manufacturing-level format process.

If the LED light is permanently on (i.e. not blinking) it means that the drive is in panic mode and a panic log has been saved to the drive. (Some vendors do not follow the Sandforce reference design, so in some instances the LED will not follow this protocol).

If the drive is in a panic state data can only be recovered by a specialist, and even then it cannot be guaranteed. Drive Savers used to be an accredited Sandforce partner, not sure if they are now, but they are probably your best hope if you need to recover data.

As Brian mentioned, this is a rare occurrence, but a rather annoying one as you loose all data.

Share this post


Link to post
Share on other sites

Wow, this situation sucks. I hope this SSD info. is in the SSD user's manual? It's a Helleva way to find out - after the fact when you're data is at high risk of loss.

Share this post


Link to post
Share on other sites

As I mentioned it is rare, or it is now. It appeared to occur more frequently when the early firmware versions had a lot of bugs. As the bugs have been ironed out reports have diminished. I haven’t seen one report of it occurring on the 520, but then again the 520 is the only Sandforce driven SSD that underwent extensive validation and debugging before it was put on the market.

Edited by Ao1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this