Just to let you know:
I have 6x600GB, 2x300GB, and 3x160GB "320 series". I updated all of them with the latest firmware as offered by Intel, and this worked like a charm with the ISO CDROM.
I use all of them extensively since April 2011, for OS X, and Data storage, both internally on 3 Macs with Snow Leopard and Lion, and on external enclosure.
So far NO problem at all, before and after the firmware update.
I was also very happy with my 4x160GB X25 Postville for the last 2 years.
Hi...even that is not clear to me...I would like to see users who have the 8mb bug AFTER the firmware 0362 to show their ssd serial number!
Intel says the the firmware fixes specific Bad Context 13x Error Serial Number BAD_CTX 0000013x!!!
Plz watch at the end of this video
http://www.youtube.com/watch?v=JqNmhWL_L54 , you should see clearly that this guy has serial number BAD_CTX 000001!
There is a differerce from 0000013x which is related to unxpected power-loss
My personal believe is that every kind of hardware failure of the 320 series ssd starts with BAD_CTX xxxxxx serial number (as this guy has) and results to 8mb of drive's capacity (and that's where the confusion begins) that's why people may think that even after the firmware update their ssd has broken!
I own an 160gb 320 series ssd from April and recently have updated the firmware but I still worry for this kind of failure...
Intel should clarify this and people who had their ssd's bricked after the update must upload their exact serial numbers.
If serial numbers aren't 0000013x then I think we have to deal with normal ssd hardware failures which we all know every company has.
Sorry for my english I hope you understand THX
Well, well, well - isn't that nice. I just got bit by the bug. Another one of those who updated just to find his SSD die about a month after.
And I can reassure everyone that the NEW bug that renders the SSD useless has nothing to do with a Power Failure (Laptop in Docking Station with Akku whilst pluged in - so double failsave), it has nothing to do with if you are on a Mac or not (HP Business Class Laptop) and it has nothing to do with the OS (Win 7 x64 Professional). It has all to do with this "oh so well tested" new update that introduced an all new bug, that not ONE person experienced before upgrading the drives Firmware.
Im now going to secure erease the drive, giving Intel Support the time to contact me, which they apperantly should do. At lease thats what some users on this forum have said.
Regardless, prepare for me rasing my voice again - when I'm back. Folks start your Twitter Clients, this just got very real. Your data isn't save on this drives. Tell your friends and tell the world. Tell your local news outlets too. Save others from loosing their data.
Blue Screen popped up while I was entering an url in a Browser. Drive wasn't even under heavy load.
I just don't understand, why you all writing in this thread instead this one http://communities.intel.com/message/138621#138621 ?
This thread looks quite old after firmware is released. Nobody cares?
Hi harlekin...Can you plz provide us the exact serial of your ssd if you haven't fix it yet if possible?
Additionally I would like to inform everyone that 8mb ssd capacity still appeared in previous generations of Intel ssd's that doesn't necessarily relates to the specific Bad Context 13x error which 320 series has occuring from power loss contitions.
It seems that every hardware failure of any Intel ssd results to 8mb capacity as well but we need more feedback on this or maybe Intel tell us that 8mb is a general failure!
No one has clarified this yet and it's time to see some serial numbers or any official statement from Intel for this matter
One more thing is to remember the bad firmware from the x-25m times that bricked many ssd's (that which provided the trim support) after the firmware was applied.
That time I have read that Intel removed the link immedietly (i don't know for how long correct me) after finding that their's ssd got bricked.
The thing is shouldn't Intel remove the firmware after all this time knowing that people still got their ssd broken as mentioned many times from this community?
They even announce it as they put it in the first link in the announcement section!
thx again and sry for the english
w00thisButtonDo this thread even it's older it's more popular i think because is the first link on the featured content section and thus more people should read this
>After the crash, was your Serial Nr: BAD_CTX 0000013x or something else?
Still trying to get the SSD recogniced. So far tried with two different USB adapters and Windows installations, but the disk wont show up. Now I have to get a USB bootable Windows to see if the disc shows up, when connected via SATA. One Sata ports only on laptops - and an Intel tool that HAS to be installed under Windows to erase the SSD - what a mess.
Well, I gave an end to the Intel 8M farse, went out and bought a few of those 500G seagate momentus SSD's who don't seem to need very much help to make them perform properly, they work with pretty much all my systems and so far (for 2 weeks) I have had no issues, the price is not bad either, $139 for 500G