5 ms·
Yikes. Cisco claims this is "an industry wide firmware index bug". Is there any validity to this claim? Are any consumer drives affected by the same issue?
by ghostly_s 4y ago
Yikes. Cisco claims this is "an industry wide firmware index bug". Is there any validity to this claim? Are any consumer drives affected by the same issue?
- zinekeller 4y agoYes, HPE is one of the SSD OEMs affected by it: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00092491en_us https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na... https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00097382en_us https://support.hpe.com/hpesc/public/docDisplay?docLocale=en... > Are any consumer drives affected by the same issue? As far as I know it doesn't affect consumer drives, but I wouldn't be surprised if some have the same defective firmware.
- fulafel 4y agoIs there any information about the provenance of this SSD controller? Sounds like enterprisey venodrs all rebranded some upstream supplier's hardware. edit: apparently sandisk: http://forum.hddguru.com/viewtopic.php?f=3&t=39964 http://forum.hddguru.com/viewtopic.php?f=3&t=39964 - also a clue about the magic 40k hour significance: "the SSD alters its performance in some way as it approaches end of life. This appears to shine some light on the reason for a trigger at 40K Power On Hours."
- zymhan 4y agoThis apparently also happened two years ago? https://www.anandtech.com/show/15673/dell-hpe-updates-for-40k-hour-essd-failures https://www.anandtech.com/show/15673/dell-hpe-updates-for-40...