3 ms·
But 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 (
by stefan_ 7y ago
But 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.