<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Intel Communities: Message List - Firmware update now available - Addresses Bad Context 13x Error</title>
    <link>http://communities.intel.com/community/tech/solidstate?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 04 Jul 2012 11:18:50 GMT</pubDate>
    <generator>Jive SBS 5.0.2.0  (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2012-07-04T11:18:50Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/160644?tstart=0#160644</link>
      <description>&lt;!-- [DocumentBodyStart:f93723a8-752f-4a20-9ae0-2287e783e805] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;Hi all,&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I'm not sure if i'm in the right place here, but I have a 320 series 160Gb that is exhibiting the "Bad Content 13x" bug. This drive only 4 months old and is running the current firmware (4PC1LE04), I have tried running the latest Toolbox and of course it will not update (as I have the current version already), does anyone know an alternative way around this problem? I need to save the data, after that Intel can have it back.....&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;ANY input would be greatly appreciated....&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks all...&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:f93723a8-752f-4a20-9ae0-2287e783e805] --&gt;</description>
      <pubDate>Wed, 04 Jul 2012 11:18:50 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/160644?tstart=0#160644</guid>
      <dc:date>2012-07-04T11:18:50Z</dc:date>
      <clearspace:dateToText>10 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/153620?tstart=0#153620</link>
      <description>&lt;!-- [DocumentBodyStart:df03a27b-4dcf-4943-b01e-0ac7c439f000] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;I am sitting here with another brand new "Bad Context 13x Error" Drive (320 series, 160 GB).&lt;/p&gt;&lt;p&gt;It was bought with the latest firmware update installed.&lt;/p&gt;&lt;p&gt;The problem is NOT solved and it is not possibel to do anything with the drive.&lt;/p&gt;&lt;p&gt;Intel, please wake up and get serious with another firmware update that will solve the problem once and for all ...&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:df03a27b-4dcf-4943-b01e-0ac7c439f000] --&gt;</description>
      <pubDate>Wed, 11 Apr 2012 19:22:37 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/153620?tstart=0#153620</guid>
      <dc:date>2012-04-11T19:22:37Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/152516?tstart=0#152516</link>
      <description>&lt;!-- [DocumentBodyStart:80f58d40-964e-4db2-8c18-001f0e14f75a] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;Agreed - problem is NOT resolved. I am on the latest firmware and have experienced this issue. Complete data loss, fixed by secure erase. GParted showed the partition size of 8MB. Intel Firmware Upgrade Utility showed BAD_CTX serial. This is despite having the most current firmware in place from the factory... I didn't even have to upgrade to the latest firmware, it was already installed and STILL failed. Received drive with a new computer just 8 weeks ago, brand new, custom built online. I created a new post in the discussion area to address this problem on the latest firmware.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Tried talking to Intel support, got blown off because my drive came in a Lenovo laptop. Despite the SSD Toolbox being expanded to support this particular drive in Lenovo systems (according to the release notes), tech support still informed me that he couldn't help me with my drive whatsoever. Lenovo confirmed for me that I do in fact have the latest firmware on the drive but that no such bugs have been reported that shrink the drive to 8mb and cause a BAD_CTX error. They'll replace the drive but that is about it.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:80f58d40-964e-4db2-8c18-001f0e14f75a] --&gt;</description>
      <pubDate>Wed, 28 Mar 2012 22:53:50 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/152516?tstart=0#152516</guid>
      <dc:date>2012-03-28T22:53:50Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/151405?tstart=0#151405</link>
      <description>&lt;!-- [DocumentBodyStart:4949d3bf-ab4c-41ac-8162-93e2407bd517] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;This issue is NOT resolved. Best advice is to backup your data and trash the drive before it fails. 200 dollars wasted. Never again, Intel.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:4949d3bf-ab4c-41ac-8162-93e2407bd517] --&gt;</description>
      <pubDate>Sun, 11 Mar 2012 22:04:08 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/151405?tstart=0#151405</guid>
      <dc:date>2012-03-11T22:04:08Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/147507?tstart=0#147507</link>
      <description>&lt;!-- [DocumentBodyStart:ba7bd1bb-d844-4f2f-99ed-8c0be1291be1] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;Of course I tried the "mac compatible"&amp;nbsp; version, (the first firmware update was supposed to be compatible, too) but none of them found an intel drive on my 2008 macbook pro.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Now I am happy with an ssd from another vendor, a LOT of time (and money for the support hotline to another country) lost.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;So much for mac compatibility.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:ba7bd1bb-d844-4f2f-99ed-8c0be1291be1] --&gt;</description>
      <pubDate>Fri, 06 Jan 2012 16:18:19 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/147507?tstart=0#147507</guid>
      <dc:date>2012-01-06T16:18:19Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/147498?tstart=0#147498</link>
      <description>&lt;!-- [DocumentBodyStart:d9444224-9d31-4e5f-baf9-c30a3874ce00] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;&lt;span&gt;The issue seems not to be fixed, in fact there are people posting in the intel community forums that they experienced the bug AFTER having updated to the new firmware (&lt;/span&gt;&lt;a class="jive-link-external-small" href="http://communities.intel.com/m" target="_blank"&gt;http://communities.intel.com/m&lt;/a&gt;&lt;span&gt;.... German tech sites have acknowledged this, too: &lt;/span&gt;&lt;a class="jive-link-external-small" href="http://www.golem.de/1108/85871" target="_blank"&gt;http://www.golem.de/1108/85871&lt;/a&gt;&lt;span&gt;...&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:d9444224-9d31-4e5f-baf9-c30a3874ce00] --&gt;</description>
      <pubDate>Fri, 06 Jan 2012 14:14:56 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/147498?tstart=0#147498</guid>
      <dc:date>2012-01-06T14:14:56Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/147474?tstart=0#147474</link>
      <description>&lt;!-- [DocumentBodyStart:b22706f6-7ec0-48ee-a695-ca141fa2bcaf] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;The latest version of the update utility has been made specifically to solve the problems to update on certain Macs! Have you tried it?&lt;/p&gt;&lt;p&gt;&lt;span&gt;Have a look at &lt;/span&gt;&lt;a class="jive-link-external-small active_link" href="http://www.intel.com/go/ssdfirmware" target="_blank"&gt;http://www.intel.com/go/ssdfirmware&lt;/a&gt;&lt;/p&gt;&lt;p&gt;and see the Release notes for version 1.92. Specifically:&lt;/p&gt;&lt;blockquote class="jive-quote"&gt;&lt;p&gt;This revision of the Firmware Update Tool:&lt;br/&gt; Fixes issues associated with correctly detecting Intel SSDs in Apple* systems.&lt;br/&gt; Updates Intel SSD 320 Series firmware specific to Lenovo* systems to the most current version.&lt;br/&gt;No other firmware changes were made from the previous release.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt; It has been released on 1 September 2011.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:b22706f6-7ec0-48ee-a695-ca141fa2bcaf] --&gt;</description>
      <pubDate>Fri, 06 Jan 2012 12:07:13 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/147474?tstart=0#147474</guid>
      <dc:date>2012-01-06T12:07:13Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/147481?tstart=0#147481</link>
      <description>&lt;!-- [DocumentBodyStart:cb323670-aabd-43b8-bb71-420761d6115c] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;the problem IS intel by not supporting the mac platform. I had a several month long painful experience similar to this one - took apart and placed the ssd forth and back between my macbook pro and a PC for updating, secure erasing, ... at least 10 times (!) because neither the update tool nor the secure erasing capable tools were supported on my mac (not even under bootcamp).&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;It's true, the situation is not much better with other manufacturers, but selling a harddrive that simply canot be updated on macs from, say the last 3 years, is not ready for the market in 2011 (my 320 ssd was not even recognized on 2 other PCs).&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:cb323670-aabd-43b8-bb71-420761d6115c] --&gt;</description>
      <pubDate>Fri, 06 Jan 2012 11:57:32 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/147481?tstart=0#147481</guid>
      <dc:date>2012-01-06T11:57:32Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/147470?tstart=0#147470</link>
      <description>&lt;!-- [DocumentBodyStart:b974ed46-05bf-4828-bc98-48e8f75999b7] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;colonelpanic, I think your problem is not the Mac, but rather the fact that you should secure erase the drive (to recover from the Bad Context situation) before trying to update the firmware. Otherwise RMA your drive to get a replacement. Please have a look to the first post in this thread and note that there other other tools out there to do secure erase without the need to use the SSD Toolbox if you can't.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I tried other SSDs from different brands (OCZ, Corsair) and I must say that the Intel's situation for upgrading the SSD firmware is in any case better...&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:b974ed46-05bf-4828-bc98-48e8f75999b7] --&gt;</description>
      <pubDate>Fri, 06 Jan 2012 09:24:55 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/147470?tstart=0#147470</guid>
      <dc:date>2012-01-06T09:24:55Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
    <item>
      <title>Re: Firmware update now available - Addresses Bad Context 13x Error</title>
      <link>http://communities.intel.com/message/147478?tstart=0#147478</link>
      <description>&lt;!-- [DocumentBodyStart:15f18054-7167-48a8-979b-a6705c874e17] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;After wrestling with this all day I can confirm the recommendation that these &lt;strong&gt;Intel 320 SSD drives should NOT be used with a Mac&lt;/strong&gt;.&amp;nbsp; Ever.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I had the drive suddenly die while waking from sleep this morning, discovered the 8MB bug, called Intel, downloaded the firmware update ISO.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The firmware updater on the ISO only sees drives on the Internal SATA bus, by the way... useless if you're in mid-recovery and have moved your defective Intel SSD to USB or other external interface on a functional computer.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The OSX Lion Disk Utility cannot manipulate this drive at all once it fails.&amp;nbsp; To my knowledge there are NO Mac OSX utilities that can affect this problem. &lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Furthermore, the DOS-based Firmware Updater cannot actually do anything to the drive on a Mid-2011 MacBook Pro.&amp;nbsp; Sees the drive, lists it as having a "BAD_CTX" serial number, and complains that it cannot complete the drive firmware update because it's password protected, which is of course false.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I'm sorry Intel, I am not about to purchase a copy of Windows, install Bootcamp (on what drive, exactly?) and run some windows-only app to try and recover my drive so that I can then run your DOS utility to upgrade the firmware on your dubiously reliable Solid State Drive.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Ironic, really, considering that reliability, next only to speed, was my major motivator for purchasing a $600 SSD in the first place.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks for nuking my data, Intel!&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:15f18054-7167-48a8-979b-a6705c874e17] --&gt;</description>
      <pubDate>Fri, 06 Jan 2012 07:23:37 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/147478?tstart=0#147478</guid>
      <dc:date>2012-01-06T07:23:37Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
  </channel>
</rss>

