4 ms·
>The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours). A
by voiper1 7y ago
>The issue affects SSDs with an HPE firmware version prior to HPD8 that results in SSD failure at 32,768 hours of operation (i.e., 3 years, 270 days 8 hours). After the SSD failure occurs, neither the SSD nor the data can be recovered. In addition, SSDs which were put into service at the same time will likely fail nearly simultaneously.
Looks like some sort of run time stored in a signed 2 byte integer. Oops.
- cesarb 7y agoIt's probably the SMART "hours of operation" field. I see no reason for anything else to be stored in units of hours instead of seconds. Yes, this means that a field meant for diagnosing failures was responsible for a failure. Oops.
- stefan_ 7y agoBut how does that brick the device? I guess the hour counter overflows, goes negative and that screws up a calculation later on, causing the firmware to crash (over and over again..) If only SSD vendors would do the usual cost-cutting measure of loading firmware from the host computer, this could be trivially fixed.
- mnw21cam 7y agoPlease no. I may actually want to boot from one of those devices.
- rini17 7y agoSomewhere in the UEFI kitchensink there certainly is firmware loading support already.
- lonelappde 7y agoWhat do you mean? The fix is to load a firmware update from the host computer.
- stefan_ 7y agoNot once you are past 32768 hours, apparently.
- imtringued 7y agoUsually the SMART counter just wraps around back to 0. In this case it becomes negative because it was read as a signed short.