Anyone else had a repeat 8mb brick on 320 ssd AFTER firmware update.

[idata]

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.

Greg.

[idata]

I'm having the same brick issue, But there is another issue on top of this. When i go to do the firmware update I get asked the 2 y/n questions about the license and then the app scans for devices, but always I get the Intel ssd not attached or disabled.

i don't know if anyone else ran into this. when i plug the ssd into a diff computer and got to MMC and Disk Management the SSD comes up has a basic disk and it want me to convert the disk to dynamic or gpt. but both fail. so if there is a step that I am missing, can someone please provide that.

thanks.

[idata]

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:

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.

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.

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.

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...

FWIIW, here's 40GB drives details exported from the Toolbox. The 120GB drive details are identical except the following four lines:

10-19, Serial Number, BAD_CTX 00000130,

27-46, Model Number, INTEL SSDSA2CW120G3,

108-111, World Wide Name, 500151795951D0FB,

255, Integrity Word, 6FA5,

'ID', 'Description', 'Raw', 'Normalized', 'Threshold', 'Action',

'Word', 'Description', 'Value',

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, , ...

[idata]

With the latest 320 series firmware installed (v0362) and than three drive failures within the 9 installed SSD drives is IMHO very shocking! And Intel still playing deaf. 

[idata]

Small business here with about 35 SSD's installed in HP laptops and desktops, of which 19 are Intel Based. We have never had an Intel SSD failure. We run 80G Gen2 through 180G 520's, and one 120G 320, running on current hardware.

I won't knock or praise other competitors on Intel's board, but we also run other brands and have only had issues with one of those. I'll never use that brand again, because the failure rates were high and the vendor refused refund.

[idata]

I got a failure on new drive that came with 362. Really not liking my options here.