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]

Hey,

I got one of these drives the other day and was told by a friend that this issue existed. I was wondering if the FW upgrade will wipe the contents of the disk or not? Not sure if I should proceed with installing the drive before the FW-update comes out or not? My current magnetic drive is down on it's knees and it urging me to replace it 😃

[idata]

firware update should not erase any data, I had a brand new drive when I updated but 2 friends updated their drives with data on them (backing up before, of course) and nothing was destroyed/deleted.

[idata]

You don't think?

Get ready for another half a year of Intel not acknowledging the bug until we can drum up enough media attention, that Intel warents another look at the case - and a new firmware only months thereafter... Until then you can take your time to think about why on earth you fell for Intels "reliability" play on marketing this product - or go for another replacement which only takes three weeks to arrive...

Anyone at Intel want to issue a statement already? Each hour without a response is bad crisis management, therefore costly and enhances the subsequent anger and overall fallout - just saying...

[idata]

I don�t think that we should wait to get media attention. Instead, we should all send mails to all the tech sites that announced that intel issued a new firmware fixing the problem and point them to this thread. Especially people that had a problem after updating with new firmware.

[idata]

Mabye it's time to get some perspective on this? There's what? 50 ppl at best in this thread, not everyone of them have had the issue? Intel's sold what? 10000? 20000? 1000000? units... either way there is way for the people in this forum to get "the big picture" on how wide spread this is. The only ones that knows are intel since they can judge it based on RMA and support calls

Intel *has* confirmed that they have seen the reports of the firmware not solving it and that they are looking into it. Do you really think they are just brushing this of to the side and that there's not people doing their very best to reproduce and identify the root cause of the issue? It makes perfect sense for them to not continiously post updates on this threads with only information that is speculatory and not confirmed

They *did* release a FW upgrade that they thought (after thourough testing) solved it..but apparently there are other edge cases.. if this was you, would you be quick to jump the gun the second time?

I have a *brand new* 160GB 320-series drive laying on the desk right infront of me.. I bought it to use it.. but I don't want Intel to feed be speculations and put out a quickfix when they're not sure..

I have plenty of friends that have gotten lots of OCZ that were DOA or bricked after using them for a while (both Vertex 2's and 3's) .. so it's definitly not a brand affinity.

So instead of crying wolf.. why don't you provide detailed information like hardware configurations, bios versions etc.. the more information the better