Comment 13 for bug 574462

I have an ASUS eeePC 900 (Target) with RAM upgrade and (formerly) a Patriot SSD upgrade as described in Bug 445852. I believe THIS bug bit the SSD hard on the lucid upgrade, and unfortunately I may have finally worn out the SSD with all my experiments the last few months.

Despite several "zeros" (dd if=/dev/zero etc.) I can no longer install lucid OR karmic successfully on the 32gig Patriot SSD. Before it started failing completely I was getting the 30+second hangs with the drive light on, and I didn't think to look for the HSM violations until too late. Once I saw some in the VT terminal while I was copying /dev/zero to the drive, and I took a photo in case the exact messages are helpful .

I put the 4gig stock SSD back in, and installed Lucid just fine. (But the stock SSD on this system never showed the serious corruption problems like in Bug 445852.) I haven't put lucid through the paces on the 4gig system, so it may show trouble I haven't seen yet.

Is there a place people are collecting wisdom on whether / how to test or recover failed SSDs if they don't respond to the /dev/zero treatment? Also when I go to order a replacement SSD, is there a place that lists models that are not affected by these bugs?