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]

After the crash, was your Serial Nr: BAD_CTX 0000013x or something else?

[idata]

>After the crash, was your Serial Nr: BAD_CTX 0000013x or something else?

Still trying to get the SSD recogniced. So far tried with two different USB adapters and Windows installations, but the disk wont show up. Now I have to get a USB bootable Windows to see if the disc shows up, when connected via SATA. One Sata ports only on laptops - and an Intel tool that HAS to be installed under Windows to erase the SSD - what a mess.

[AKouf]

Hi harlekin...Can you plz provide us the exact serial of your ssd if you haven't fix it yet if possible?

Additionally I would like to inform everyone that 8mb ssd capacity still appeared in previous generations of Intel ssd's that doesn't necessarily relates to the specific Bad Context 13x error which 320 series has occuring from power loss contitions.

It seems that every hardware failure of any Intel ssd results to 8mb capacity as well but we need more feedback on this or maybe Intel tell us that 8mb is a general failure!

No one has clarified this yet and it's time to see some serial numbers or any official statement from Intel for this matter

One more thing is to remember the bad firmware from the x-25m times that bricked many ssd's (that which provided the trim support) after the firmware was applied.

That time I have read that Intel removed the link immedietly (i don't know for how long correct me) after finding that their's ssd got bricked.

The thing is shouldn't Intel remove the firmware after all this time knowing that people still got their ssd broken as mentioned many times from this community?

They even announce it as they put it in the first link in the announcement section!

thx again and sry for the english

w00thisButtonDo this thread even it's older it's more popular i think because is the first link on the featured content section and thus more people should read this

[idata]

Anyone have a rough estimate of the distribution, between laptops and desktops, for the failed (both "Bad Context 13x Error" and other issues) drives?

[idata]

I just don't understand, why you all writing in this thread instead this one /message/138621# 138621 http://communities.intel.com/message/138621# 138621 ?

This thread looks quite old after firmware is released. Nobody cares?