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]

Trying to figure out why the word hard was blocked out of my post? SMH.

[Vegan]

I still urge daily backups if you use your rig for work.

I have a server so I use it for dynamic backups using LIve Mesh, this way its transparent.

[idata]

I hear you and have dozens of servers. I have yet to find a solution that handles my PST on the fly well but have not tried Live Mesh for this yet.

Yes I have a PST file as I manage a few companies with a few exchange servers so I have a few identities. Live Mesh huh..if it can os the PST file while outlook is running I am sold.

[idata]

Mozy works for your PST file. It takes a while the first backup (my PST is 7-8GB). But once it has it backed up, it will make backups daily of only the changes in your PST. Takes about 1-2 minutes per day to backup depending on how many emails I get.

I use Mozy for my PST and I use sugarsync for everything else. Mozy is not very user friendly as far as access from my phone, tablet, etc.. But that PST file is my business. I have contracts and legal documents in and out all day. The loss of even a day is quite a mess.

[Vegan]

Outlook PST files are usually pretty busy. Still using an account on a Windows Server, I log in and I can still sync anything I select.

Live Mesh uses the Passport to share files with specificed users. Limit is 9 users.

More than that you best up another server

Now if its only 1 user, easy for a single server to have multiple backups as the share limit is with people not server accounts

if tom shares only with his own account, then its 1 user of many on the server

if tom shares with dick the mesh sees two of 9 but the server will also have 2 users, tom and dick

Mesh is on top of the server etc