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

[Vegan]

Just before the hard disk prices went insane I went for a 2TB eco-green disk. ST2000DL003 if you need to know. Was 70.97 now 249.00 plus tax and shipping.

I am looking at a small SSD for a cache but given the range of issues I am thinking I will push that back.

I hate errors like that. Recently I had to do some arcane work to recover a hard disk with dodgy firmware. At least that succeeded.

Today the SSD is comparatively inexpensive.

I suggest everyone with an Intel SSD grab the tollkit 3 package and use it. Check the health of your storage weekly with your weekly backups.

[idata]

It is the same error. Intels Update Tool doesnt show the last two digits of the serial. Parted Magic showed the serial as BAD_CTX 00000130 which is the 13x error we are discussing in this thread. I havent taken a screenshot from the Parted Magic info screen, but I've checked the serial twice before starting the secure erase. I'm a 100% sure of it.

Parted Magic 6.6 (Bootdisk, just burn it to a CD or DVD and boot it up) was able to secure erase the disk (no Intel SSD Toolbox, and therefore no two SATA Ports and another bootable Windows installation needed, for a step by step visit http://blog.corsair.com/?p=4484 http://blog.corsair.com/?p=4484 ) which restored the 160GB (from 8mb shown before), as with everyone who was cought by the bug, all data is lost though. Luckily (!) I had a full disk Backup from four days ago. Which is now already restoring.

About 40min left to be up and running again.

[idata]

I figure it is about time now to discuss, why suddently, after the firmware update - the 13x error starts appearing while Windows is running perfectly fine, on a Laptop with full batteries and whilst being connected to power. This was not a behavior we witnessed before. Intel has by far worsened the problem with the current firmware update - so please, give out a statement already.

Having the SSD fail once a month, with total data loss isn't a fair prospect. Fix it.

[PZ_BO]

It looks like a LOT more problems occur on Windows systems, rather than on Macs ...

[idata]

paulzeb wrote:

It looks like a LOT more problems occur on Windows systems, rather than on Macs ...

This is what I thought as well and why I asked several times in this thread if any Mac users who run solely OSX had problems after the firmwareupdate too.

My SSD runs smooth so far (osx 10.6, macbook pro) since the (painful) upgrade.