<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update. in Archive</title>
    <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14410#M9628</link>
    <description>&lt;P&gt;I deployed eight or nine 320 series SSDs back in july/august '11. All were updateted to the 362 firmware. At this time three of these have failed, all during the last three weeks:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. 320 120GB retail, broke two days ago. Was installed in a HP laptop running XPx86sp3. Drives showes excessive End-To-End errors in the SMART status and won't boot the OS. Data could be taken off altho the drive was reluctant to give it up. RMA was approved w/o hassle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. 320 40GB retail, bricked about three weeks ago. Serial BAD_CTX 0000013F. Was installed in an older P4 desktop running XPx86sp3. The machine was running 24/7 unattended w/ very little disk activity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. 320 120GB OEM, bricked about two weeks ago. Serial BAD_CTX 00000130 Was installed in a Shuttle Intel based system running W7U64sp1. The machine was running 24/7 unattended w/ very little disk activity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No. 2 and 3 disks were restored w/ the secure erase feature of the SSD Toolbox (3.0.1). There was no apparent reason why the disks bricked, both machines are on UPSs and have new PSUs. All powersaving was turned off. As of now I don't know what I'm going to do with these...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FWIIW, here's 40GB drives details exported from the Toolbox. The 120GB drive details are identical except the following four lines:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10-19, Serial Number, BAD_CTX     00000130,&lt;/P&gt;&lt;P&gt;27-46, Model Number, INTEL SSDSA2CW120G3,&lt;/P&gt;&lt;P&gt;108-111, World Wide Name, 500151795951D0FB,&lt;/P&gt;&lt;P&gt;255, Integrity Word, 6FA5,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'ID', 'Description', 'Raw', 'Normalized', 'Threshold', 'Action',&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;'Word', 'Description', 'Value', &lt;/P&gt;0, General Configuration, 0040, ,     Bit 15 - ATA Device Identifier, 0, ,     Bit 14:8 - Retired, 00, ,     Bit 7:6 - Obsolete, 1, ,     Bit 5:3 - Retired, 0, ,     Bit 2 - Response Incomplete, 0, ,     Bit 1 - Retired, 0, ,     Bit 0 - Reserved, 0, 1, Obsolete, 3FFF, 2, Specific Configuration, C837, 3, Obsolete, 0010, 4, Retired, 0000, 5, Retired, 0000, 6, Obsolete, 003F, 7-8, Reserved, 00000000, 9, Retired, 0000, 10-19, Serial Number, BAD_CTX     0000013F, 20-21, Reserved, 00000000, 22, Obsolete, 0000, 23-26, Firmware Version, 4PC10362, 27-46, Model Number, INTEL SSDSA2CT040G3, 47, READ/WRITE MULTIPLE Support, 8010, ,     Bit 15:8, 80, ,     Bit 7:0 - Maximum Sectors, 10, 48, Trusted Computing Feature Set Options, 0000, ,     Bit 15 - Must be set to 0, 0, ,     Bit 14 - Must be set to 1, 0, ,     Bit 13:1 - Reserved, 0000, ,     Bit 0 - Trusted Computing Feature Set Supported, 0, 49, Capabilities, 2F00, ,     Bit 15:14 - Reserved, 0, ,     Bit 13 - Standby Timer Option, 1, ,     Bit 12 - Reserved, 0, ,     Bit 11 - IORDY Supported, 1, ,     Bit 10 - IORDY May Be Disabled, 1, ,     Bit 9 - LBA Supported, 1, ,     Bit 8 - DMA Supported, 1, ,     Bit 7:0 - Retired, 00, 50, Capabilities, 4000, ,     Bit 15 - Must be set to 0, 0, ,     Bit 14 - Must be set to 1, 1, ,     Bit 13:2 - Reserved, 0000, ,     Bit 1 - Obsolete, 0, ,     Bit 0 - Vendor Specific Minimum Standby timer, 0, 51-52, Obsolete, 00000000, 53, Field Validity, 0007, ,     Bit 15:8 - Vendor Recommended Free-Fall Control Sensitivity, 00, ,     Bit 7:3 - Reserved, 00, ,     Bit 2 - Word 88 is Valid, 1, ,     Bit 1 - Words 70:64 are Valid, 1, ,     Bit 0 - Obsolete, 1, 54-58, Obsolete, 00100010003F3F000000, 60-61, Total Number of user addressable sectors, 00004000, 62, Obsolete, 0000, 63, Multiword DMA Transfer, 0007, ,     Bit 15:11 - Reserved, 00, ,     Bit 10 - Multiword DMA Mode 2 Selected, 0, ,     Bit 9 - Multiword DMA Mode 1 Selected, 0, ,     Bit 8 - Multiword DMA Mode 0 Selected, 0, ,     Bit 7:3 - Reserved, 00, ,     Bit 2 - Multiword DMA Mode 2 Supported, 1, ,     Bit 1 - Multiword DMA Mode 1 Supported, 1, ,     Bit 0 - Multiword DMA Mode 0 Supported, 1, 64, PIO Transfer Modes Supported, 0003, ,     Bit 15:2 - Reserved, 0000, ,     Bit 1 - PIO Mode 4 Supported, 1, ,     Bit 0 - PIO Mode 3 Supported, 1, 65, Minimum Multiword DMA Transfer Cycle Time Per Word (ns), 0078, 66, Device Recommended Multiword DMA Cycle Time (ns), 0078, 67, Minimum PIO Transfer Cycle Time Without IORDY Flow Control (ns), 0078, 68, Minimum PIO Transfer Cycle Time With IORDY Flow Control (ns), 0078, 69, Additional Supported, 4020, ,     Bit 15 - CFast Specification Support, 0, ,     Bit 14 - Deterministic Read After Trim Supported, 1, ,     Bit 13 - Long Physical Sector Alignment Error Reporting Control Supported, 0, ,     Bit 12 - DCO IDENTIFY DMA and DCO SET DMA Supported, 0, ,     Bit 11 - READ BUFFER DMA Supported, 0, ,     Bit 10 - WRITE BUFFER DMA Supported, 0, ,     Bit 9 - SET MAX SET PASSWORD DMA and SET MAX UNLOCK DMA Supported, 0, ,     Bit 8 - DOWNLOAD MICROCODE DMA Supported, 0, ,     Bit 7 - Reserved, 0, ,     Bit 6 - Optional ATA Device 28-bit Commands Supported, 0, ,     Bit 5 - Read Zero After Trim Supported, 1, ,     Bit 4:0 - Reserved, 00, 70-74, Reserved, 000000000000 00000000, 75, Queue Depth, 001F, ,     Bit 15:5 - Reserved, 000, ,     Bit 4:0 - Maximum Queue Depth - 1, 1F, 76, Serial ATA Capabilities, 0406, ,     Bit 15:13 - Reserved, 0, ,     Bit 12 - Native Command Queuing Priority Information Support, 0, ,     Bit 11 - Unload While NCQ Commands Outstanding Support, 0, ,     Bit 10 - Phy Event Counters Support, 1, ,     Bit 9 - Receipt of Host-Initiated Interface Power Managament Requests Support, 0, ,     Bit 8 - Native Command Queuing Support, 0, ,     Bit 7:4 - Reserved, 0, ,     Bit 3 - Serial ATA Gen3 Signaling Speed (6.0 Gbps) Support, 0, , ...</description>
    <pubDate>Thu, 17 Nov 2011 00:38:13 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2011-11-17T00:38:13Z</dc:date>
    <item>
      <title>Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14379#M9597</link>
      <description>&lt;P&gt;Had my 320 ssd for a month, all going well till a usb device BSOD my win7, rebooted to find my disk at 8mb. Waited for firmware update last wednesday as lots of forum discussion. Did Secure erase and firmware update to v1.9 and restored partition on friday. Today usb BSOD again (visual studio blow up, im a software developer) and rebooted to find the drive again 8mb. Anyone else had this problem, looks to me like the firmware update did not fix this type of issue.&lt;/P&gt;&lt;P&gt;Greg.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2011 12:19:25 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14379#M9597</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-08-24T12:19:25Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14380#M9598</link>
      <description>&lt;P&gt;Greg, would you be able to provide any additional details?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would you happen to have the BSOD error code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Was it a soft reboot (system reboot by itself after BSOD memory dump) or was it a hard reboot (you hit a switch)? &lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2011 17:01:43 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14380#M9598</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-08-24T17:01:43Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14381#M9599</link>
      <description>&lt;P&gt;Sort of. I had mine brick on me for the first time AFTER applying the firmware update.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Aug 2011 17:03:30 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14381#M9599</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-08-30T17:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14382#M9600</link>
      <description>&lt;P&gt;Only after update &lt;/P&gt;</description>
      <pubDate>Sun, 04 Sep 2011 09:50:30 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14382#M9600</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-04T09:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14383#M9601</link>
      <description>&lt;P&gt;Can somebody from Intel please comment on the importance (if any) of FIRST making the ssd &lt;B&gt;powerless&lt;/B&gt; for 30-60sec, right after the flashing of the new firmware, BEFORE using it again.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Sep 2011 11:08:56 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14383#M9601</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-04T11:08:56Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14384#M9602</link>
      <description>&lt;P&gt;I did. And I got it first time after flashing it to v1.92.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firmware Version 4PC10362&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brand new (just one week) intel 320 / 120GB - SSDSA2CW120G3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On my sony vaio laptop. &lt;/P&gt;</description>
      <pubDate>Sat, 10 Sep 2011 09:17:00 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14384#M9602</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-10T09:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14385#M9603</link>
      <description>&lt;P&gt;SongV,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would you be able to provide any additional details about the circumstances leading to the "8MB bug" AFTER the update to firmware level 1.9.2?&lt;/P&gt;</description>
      <pubDate>Sat, 10 Sep 2011 10:33:32 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14385#M9603</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-10T10:33:32Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14386#M9604</link>
      <description>&lt;P&gt;I bought this intel SSD one week ago. Before I flashed its firmware to 4PC10362, it worked well. Yesterday, I just turned on my sony laptop and tried to launch Chrome browser. But the computer prompted me the browser had been damaged. And then the computer froze , as well as Hard Disk LED kept on. I tried to Ctrl + Alt + Del. But then screen became to black and system prompted me to reboot or shut down. I cold shut down the computer. when I turned on the computer again, the SSD capacity became to 8M! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sony laptop VPCEA200C. Windows 7 64 bit. Intel SSD 320 Series 120GB. &lt;/P&gt;</description>
      <pubDate>Sat, 10 Sep 2011 12:53:19 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14386#M9604</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-10T12:53:19Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14387#M9605</link>
      <description>&lt;P&gt;I am not a expert, but for me it looks like any SSD hw or firmware failure manifest as 8MB problem, so that might be only broken SSD we see after firmware update which would fail due hw &lt;/P&gt;</description>
      <pubDate>Sun, 11 Sep 2011 11:57:42 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14387#M9605</guid>
      <dc:creator>ZStan</dc:creator>
      <dc:date>2011-09-11T11:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14388#M9606</link>
      <description>&lt;P&gt;Since I had the pleasure of a bricked SSD today after updating the firmware about a month ago I can provide some information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;Would you happen to have the BSOD error code?&lt;/P&gt;&lt;P&gt;0x00000 or 00000x0 something very similar to that - I'm about 85% sure that the error code contained just zeros an one x.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;Was it a soft reboot (system reboot by itself after BSOD memory dump) or was it a hard reboot (you hit a switch)?&lt;/P&gt;&lt;P&gt;Soft reboot, I read the memory is being dumped line, and then the reboot countdown started and the system rebooted.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2011 02:56:07 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14388#M9606</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-22T02:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14389#M9607</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Today I was working and suddenly got BSoD on my SSDSA2CW300G3 with firmware 4PC10362. BSoD was telling me, that memory minidump has failed (I guess, disk was already dead at that minute). After booting from other media, disk had 8 MB and Serial Number: BAD_CTX 00000159. I did Secure Erase, and all my data has gone, for sure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dear Intel, what else should I do to prevent repetition of this issue in future and to prevent further data losts?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2011 23:26:25 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14389#M9607</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-26T23:26:25Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14390#M9608</link>
      <description>&lt;P&gt;Hi vanav...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which program indicated your serial number? (BAD_CTX 00000159) Intel Toolbox?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems now clearly to me that every ssd failure results to 8mb capacity but with different serial numbers!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a bit relaxing cause 8mb must be any hw failure or any firmware bug which has nothing to do with the firmware 0362 which fixes specifically the BAD_CTX 0000013x error due to unsafe power (as Intel say).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you confirm the serial number with other programs as well? THX &amp;amp; sry for the english&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2011 10:13:14 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14390#M9608</guid>
      <dc:creator>AKouf</dc:creator>
      <dc:date>2011-09-27T10:13:14Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14391#M9609</link>
      <description>&lt;P&gt;I've read serial number with Intel SSD Toolbox → View Drive Information → Export [to CSV].&lt;/P&gt;&lt;P&gt;You're right, last firmware update fixes only "BAD_CTX 0000013x", and I got no power loss.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But this issue looks very similar, in all cases we got:&lt;/P&gt;&lt;P&gt;1) size is 8 MB (Total Number of user addressable sectors: 00004000, Maximum User 48-Bit LBA: 0000000000004000),&lt;/P&gt;&lt;P&gt;2) S.M.A.R.T. is disabled,&lt;/P&gt;&lt;P&gt;3) Serial Number: BAD_CTX 00000xxx,&lt;/P&gt;&lt;P&gt;4) disk is fully operational after Secure Erase.&lt;/P&gt;&lt;P&gt;Looks like good hardware and bug in firmware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other codes, possibly related: /message/122329 BAD_CTX 00000166 bug, /message/138322 BAD_CTX 0000012D bug (was restored to working condition by Secure Erase).&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2011 11:25:57 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14391#M9609</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-27T11:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14392#M9610</link>
      <description>&lt;P&gt;It is very annoying that Intel does NOT comment on the expectation that firmware 4PC10362 ONLY solves the BAD_CTX0000013X error and that all other BAD_CTX000001xx errors, which are recoverable by a 'Secure Erase', are NOT related and should be seen as different firmware issues/bugs!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This Intel 320 SSD series (shipped April 2011!) declines more and more to a product, not to be recommended to anyone!&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2011 16:04:22 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14392#M9610</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-27T16:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14393#M9611</link>
      <description>&lt;P&gt;test &lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2011 22:03:10 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14393#M9611</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-29T22:03:10Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14394#M9612</link>
      <description>&lt;P&gt;&lt;B&gt;WARNING &lt;/B&gt;: Mine has just bricked again - 8MB. This time BIOS has issues recognizing it on boot. I used the replacement drive from Intel for about 6 weeks after applying the firmware update and now it is toast again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;600Gig 320 SSD&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running on Dell M6500 laptop using Dell docking station Win7 64 bit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The failure might occur when the laptop goes to Sleep or wake from sleep, I think, I have hibernate disabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Intel - do you need any more info on this from me to help. I will report tomorrow....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John Rose&lt;/P&gt;&lt;P&gt;212-999-6566&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2011 22:03:42 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14394#M9612</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-09-29T22:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14395#M9613</link>
      <description>&lt;P&gt;Decided to post here, as I had my second failure. This time it happened after firmware update (current FW 4PC10362) and few weeks of use. In the middle of operation, computer froze and HDD light was constantly on. After reset I got 8MB drive with serial BAD_CXT 13F. So not 13x, but close...&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2011 07:47:00 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14395#M9613</guid>
      <dc:creator>JNyma</dc:creator>
      <dc:date>2011-10-05T07:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14396#M9614</link>
      <description>&lt;P&gt;Mine had froze up the system. Then on forced reboot Windows started coming up normally, then I saw a brief bluescreen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Intel - any input here? Looks like another bricking scenario for these drives - I purchased this drive for it's reliability - $1200+&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2011 12:39:00 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14396#M9614</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-10-05T12:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14397#M9615</link>
      <description>&lt;P&gt;Have you contacted the Intel Support team (&lt;A href="http://www.intel.com/support/feedback.htm?group=ssd" rel="nofollow noopener noreferrer"&gt;http://www.intel.com/support/feedback.htm?group=ssd&lt;/A&gt; &lt;A href="http://www.intel.com/support/feedback.htm?group=ssd" rel="nofollow noopener noreferrer"&gt;http://www.intel.com/support/feedback.htm?group=ssd&lt;/A&gt;)  or just POSTing here on the users forum? &lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2011 18:56:44 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14397#M9615</guid>
      <dc:creator>DSilv11</dc:creator>
      <dc:date>2011-10-05T18:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.</title>
      <link>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14398#M9616</link>
      <description>&lt;P&gt;I already did it. They just told me that:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for contacting Intel Customer Support.&lt;/P&gt;&lt;P&gt;Please install the SSD as a secondary drive and perform Secure Erase to clear the SSD.  The Secure Erase function is included in Intel SSD Toolbox and is available for download here: &lt;/P&gt;&lt;A href="http://www.intel.com/support/go/ssdtoolbox" rel="nofollow noopener noreferrer"&gt;http://www.intel.com/support/go/ssdtoolbox&lt;/A&gt; &lt;A href="http://www.intel.com/support/go/ssdtoolbox" rel="nofollow noopener noreferrer"&gt;www.intel.com/support/go/ssdtoolbox&lt;/A&gt;&lt;P&gt;Please refer to the user guide for the procedure in performing Secure Erase.&lt;/P&gt;&lt;A href="http://downloadmirror.intel.com/18455/eng/Intel_SSD_Toolbox_User_Guide_2.0.pdf" rel="nofollow noopener noreferrer"&gt;http://downloadmirror.intel.com/18455/eng/Intel_SSD_Toolbox_User_Guide_2.0.pdf&lt;/A&gt; &lt;A href="http://downloadmirror.intel.com/18455/eng/Intel_SSD_Toolbox_User_Guide_2.0.pdf" rel="nofollow noopener noreferrer"&gt;http://downloadmirror.intel.com/18455/eng/Intel_SSD_Toolbox_User_Guide_2.0.pdf&lt;/A&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's it.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2011 23:49:46 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/anyone-else-had-a-repeat-8mb-brick-on-320-ssd-after-firmware/m-p/14398#M9616</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2011-10-05T23:49:46Z</dc:date>
    </item>
  </channel>
</rss>

