Quote Originally Posted by Tony View Post
So because your drive showed this behaviour we have a FW issue?

1 drive with this behaviour means 1million are bad? No one else has complained about this...just you

if you used the drive normally as an end user does did it show an issue?
Unless my drive is faulty, you do have a firmware issue, whether you want to believe it or not, and whether you fix it or not. I should not be able to be able to induce a complete lockup in an SSD no matter what sequence and timing of LBA writes I perform. I gave the drive ample time to recover before I ran the final write pass that locked up, so this issue is accumulative and not self correcting. Since you haven't said that you cannot reproduce my results I'll assume it is not just my drive.

And, I did not say the drives were bad, I said the drive had a issue and I was hitting it and hence I was suspending my endurance test on it. Do not put words in my mouth.

As for low write load desktop end users, sure, of course they won't notice this issue any time soon. Firmware 1.5 has only been out a couple of months. However, this kind of accelerated stress testing can show what a user will see in months/years of use.

Stress testing like what I did should really be part of your standard firmware testing. Don't peddle crap about usage models to cover for not running the hard yards in validation.