cancel
Showing results for 
Search instead for 
Did you mean: 

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

idata
Esteemed Contributor III

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

177 REPLIES 177

idata
Esteemed Contributor III

Great time to sell back up software, programmers will make a killing.

idata
Esteemed Contributor III

I've never pretended the bug does not exist - it clearly does and it probably was not fixed by the firmware update. I've never said the opposite.

The belief that the lack of moving parts makes SSDs somehow more reliable than old HDDs is an illusion, supported by manufacturers. It's very difficult to get reliable data for independent report. The only one I'm aware of is http://www.tomshardware.com/reviews/ssd-reliability-failure-rate,2923.html http://www.tomshardware.com/reviews/ssd-reliability-failure-rate,2923.html, and it suggests that the difference is not that big.

I personally don't care whether there are moving parts or not - I'm interested in IOPS, price and reliability. Let there be a dwarf reading the bytes from a book, I don't care as long as the IOPS/price is high and the device is reliable.

I have no reason to change my previous statement that the logic "intel SSDs have a bug so if I buy an SSD from a different manufacturer I'll be safe" is flawed.

idata
Esteemed Contributor III

The most frustrating aspect of SSD failures is that SSDs have the potential to be the most reliable nonvolatile storage devices in the world, yet they aren't due to shoddy engineering and other cost cutting measures. Everything I've read so far indicates that NAND cells could very well last decades of abuse, but all SSDs die early because either the controller hardware fails or the software bugs out.

idata
Esteemed Contributor III

did anyone brick his ssd AFTER the firmware update running solely osx (no bootcamp, no intel tools, ...)?

idata
Esteemed Contributor III

Please don't manufacture excuses in the wake of another firmware driven problem which reduces drives capacity to 8MB regardless of the drives age or wear. You can water down the argument regarding the firmware error as much as you like, it doesnt adress the fact, that Intel hasn't fixed an acknowledged firmware bug - despite their press release. And that they now have gone silent again.

I know of at least another german tech site which has a pending information request regarding the current case, but Intel seems to be playing it stealthy right now.

Comparisons with other hard drives have no place in this thread. Please return to the topic at hand.