8/13 Update on "Bad Context 13x Error" for Intel SSD 320 Series

[idata]

Status:

Intel has reproduced, identified root cause, and developed a firmware update which addresses the Bad Context 13x Error being discussed on the Communities site and elsewhere.

Response plan:

The new firmware update is in final validation testing and is targeted for release on Intel® Communities within the next two weeks. Intel takes firmware updates and issues of reliability very seriously and is taking extra steps to support a smooth release. We appreciate your patience.

What should I do if I have not experienced this issue?

To minimize occurrence, if a system requires a shut down, Intel recommends using that system's standard power shut down sequence. As with any storage device, Intel recommends users frequently back up their data. Download and install the new firmware when it is available. As with our previous firmware updates, a secure erase is not required.

What should I do if I have experienced this issue?

If you have already experienced a drive failure or encounter this problem before the firmware update is released, please contact your Intel representative or Intel customer support (via web: http://www.intel.com/ www.intel.com or phone: http://www.intel.com/p/en_US/support/contact/phone www.intel.com/p/en_US/support/contact/phone) for an SSD replacement. An alternative option is to use the Intel ® SSD Toolbox or similar tools to perform a secure erase in order to restore the SSD to an operational state; all data will be erased. After secure erase, update your SSD with the upcoming firmware. The pending firmware update will not recover user data.

Background:

For users unfamiliar with the issue, an Intel SSD 320 Series drive may exhibit a drive capacity of 8MB and an electronic serial # field containing a message of "BAD_CTX 0000013x" due to an unexpected power loss under specific conditions. Once this error occurs, no data on the SSD can be accessed and the user cannot write to or read from the SSD.

Rgds,

Scott

Intel Corporation

[idata]

May I adress the flawed logic in this arguments.

First - after the firmwareupdate we now have documented cases of the 8mb error occuring not only during boot cycles, but while a device selftest resulting in a bluescreen and a crash. Now thats progress - isn't it. Talking about edge cases, and how they seem to have broadened.

Whenever PR doesn't issue a response in the face of a massive product screwup, it is the exact opposite of "a good sign". It is the equivalent of keeping the problem down, while they assess if it would be financialy feasable to takle or neglect it. That at least one forum member was contacted in private - there is no open call to provide Intel with the information regarding the resurfacing bug - is more cause to be wary, than "a good sign".

It tends to satisfy the ones voicing complaints, while offering no official statement, or plan for action in return.

First you do everything you can to make them acknoledge the problem - then you give them all the time in the world to fix it, because they'll take it anyways.

Oh yes, and a firmwareupdate, that doesn't fix the problem shouldn't be interpreted as "well at least they tried". You can't judge the effort, because you havent seen it. You should judge the end result and this is once again - abysmal failure, a flawed quality assurance process, and a broken promise.

Well, waiting a little, sure will make it better -

[idata]

A major german (tech) news outlet has picked up the fact that the patch hasn't resolved the problem. http://www.golem.de/1108/85871.html http://www.golem.de/1108/85871.html

How about an official statement Intel? In the meantime I will continue my efforts - please, PR team, do the same.

[idata]

Please merge this thread with this one: http://communities.intel.com/thread/24205?start=0&tstart=0 http://communities.intel.com/thread/24205?start=0&tstart=0

I had only one crash in the last few weeks, and this one crash lead to the 8MB bug. Possible that the new firmware makes it worse or just bad luck? Is there a way to revert to the old firmware?

[idata]

I would like to know if all 320 series drives are able to "fail" or if it happens just to a few ones. I really rely on my machine (teaching classes, client presentations) and if this issue is not being fixed soon, I will bring back the drive and buy another brand. This is ridiculous, especially how intel does not inform customers here at all (except for some vage "found the issue, will bring firmware update soon", etc.).

I lost at least 2 days about this sh***, and opened and closed my macbook pro at least 7 times (which is not THAT easy with a pre-unibody machine). enough time lost here, and a disappointed customer lost very soon.

Edit: I know Intel does (and probably will not) care about single customers like me. But its extremely frustrating not feeling heard and treated like last-class-customers by a 'premium class' (and premium price tag) company.

[idata]

Mate we are all dependatant on our drives ... not just you ..

2 days ... wow lets see

Purchased back in may .... set up ....... 10 days ..... boom... 8 MB... lost all my data needed to use 3 day old backup ....

took 3 weeks to get the dealer here in Germany to accept it as an issue...... 3 weeks more to get the replacment..

now wait 5 weeks due to "Fix pending"... ok lets wait 2 days after fix to see what happens with early adopters....

ok lets go ....

create a bootable USB Stick with freedos... 10 mins ... done

Apply Update 5 mins ...done

Reboot on 1st Gen Inetl SSD (Win 7) ... done..

Check "Clean" (Use win7 to create a partition .... then delete....seems ok full 300 G .. wow fixed)..... done

Start Intel Migration Tool (Request As-Is Migration ... can always grow and move the partitions afterwards)....... starts ... looking real good..... done.

Restarts and tells me its doing its stuff........ FREEZE......................... BOOM cant access ... ?????

Ok reboot.... Done

OMx .... win 7 does not pick it up in the drive list .... no partition.... 8MB....aaaaaaaaaaaaaaaaaaaaaaaaaarrrrrrrrrrrrrrggggggggggggggg

So lets see now 3days later ..3*7+3*7+5*7+2 = 21+21+35+2 = 79 days .. or 3 days if we only count from the last crash...

welcome to the world of reliability... well as long as you

a) dont use the 2nd Gen

b) keep using the 1st Gen

so to answer your point ... get the first gen ... mines has been up and running in 1 macbook pro and a M$ box for over a year now