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, would you be able to provide any additional details?
Would you happen to have the BSOD error code?
Was it a soft reboot (system reboot by itself after BSOD memory dump) or was it a hard reboot (you hit a switch)?
Since I had the pleasure of a bricked SSD today after updating the firmware about a month ago I can provide some information.
>Would you happen to have the BSOD error code?
0x00000 or 00000x0 something very similar to that - I'm about 85% sure that the error code contained just zeros an one x.
>Was it a soft reboot (system reboot by itself after BSOD memory dump) or was it a hard reboot (you hit a switch)?
Soft reboot, I read the memory is being dumped line, and then the reboot countdown started and the system rebooted.
Can somebody from Intel please comment on the importance (if any) of FIRST making the ssd powerless for 30-60sec, right after the flashing of the new firmware, BEFORE using it again.
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?
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!
Sony laptop VPCEA200C. Windows 7 64 bit. Intel SSD 320 Series 120GB.
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
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.
Dear Intel, what else should I do to prevent repetition of this issue in future and to prevent further data losts?
Which program indicated your serial number? (BAD_CTX 00000159) Intel Toolbox?
It seems now clearly to me that every ssd failure results to 8mb capacity but with different serial numbers!
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).
Did you confirm the serial number with other programs as well? THX & sry for the english
I've read serial number with Intel SSD Toolbox → View Drive Information → Export [to CSV].
You're right, last firmware update fixes only "BAD_CTX 0000013x", and I got no power loss.
But this issue looks very similar, in all cases we got:
1) size is 8 MB (Total Number of user addressable sectors: 00004000, Maximum User 48-Bit LBA: 0000000000004000),
2) S.M.A.R.T. is disabled,
3) Serial Number: BAD_CTX 00000xxx,
4) disk is fully operational after Secure Erase.
Looks like good hardware and bug in firmware.
Other codes, possibly related: /message/122329 BAD_CTX 00000166 bug, /message/138322 BAD_CTX 0000012D bug (was restored to working condition by Secure Erase).
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!
This Intel 320 SSD series (shipped April 2011!) declines more and more to a product, not to be recommended to anyone!
WARNING : 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.
600Gig 320 SSD
Running on Dell M6500 laptop using Dell docking station Win7 64 bit.
The failure might occur when the laptop goes to Sleep or wake from sleep, I think, I have hibernate disabled.
Intel - do you need any more info on this from me to help. I will report tomorrow....
My 600GB SSD 320 was bricked again a couple of minutes ago. First time bricked a month ago, did secure erase and applied firmware update. Now it is bricked again after waking up from sleep mode. Dell M6500, Win 7 x64, secondary drive.
Ya the first time mine bricked was definitely from sleep mode as there were no power issues. Second time I'm almost postive it was either entering or leaving sleep mode. My guess is that this occurs under at least 2 circumstances. Intel fixed one of them, the power interruption scenario, not the sleep mode scenario. There could be other scenarios like hibernate as well....
Same issue: 1 month after updating to FW 4PC10362, System freeze, then after reboot: Serial number = BAD_CTX 0000013F and size=8,4MB.
iMac 27" core i5 MacOS 10.7.2, without TRIM (I used TRIM before).
I can't secure erase the SDD using Intel Tool as it needs to unplug/replug the SSD from SATA to bypass security and the SSD is embedded inside the core of the iMac.
Anyone has a solution to secure erase without accessing to the SSD?
Same problem for me. My Intel SSD 320 600GB now shows 8MB while running in my laptop as it was the second hard disk. No loss of power or anything similar occurded. I am now afraid that my first Intel SSD 320 600GB will get the same problem. So firmware 10362 has not solved the problem. Intel will exchange the disk, but I had to live with the risk.
Bad news. TC