7 ms·
Before the ST3000DM001, the ST31500341AS became infamous, both for its failure rate, and its firmware bug. The latter, if memory serves, was the bug where the
by rincebrain 5y ago
Before the ST3000DM001, the ST31500341AS became infamous, both for its failure rate, and its firmware bug.
The latter, if memory serves, was the bug where the drive had an internal event log that was a ring of 256 entries, and if it was at the last entry on boot, the hard drive's code on bootup for handling rolling back to 0 was (usually) broken, causing the hard drive to not start up any more. (I say usually because for this particular bug, regardless of whether I'm associating it with this model correctly, there were anecdotes of repeatedly power cycling the drives causing them to eventually boot normally, whereupon you could eventually apply the firmware update.)
If you look up that model, you can find people commenting on stories about the ST3000DM001 asking "so when's the class action for the ST31500341AS?"
edit: I see someone else in this discussion also remembers that family even better than I, because I forgot (or didn't update fast enough to encounter) the bug that was present in the first firmware update to fix this.
https://news.ycombinator.com/item?id=27419342 https://news.ycombinator.com/item?id=27419342
- deleted 5y ago[deleted]
- WarOnPrivacy 5y agoIn the late 1990s there were a slew of Connor hard drives with leaking seals. The outside of the platter would become corrupt and that would proceed inward. Seagate bought Connor in the middle of this and refused to honor the warranties. From what I recall a lawsuit followed and Seagate eventually capitulated.