3 ms·
Yes, there was a well published Seagate issue [1] that I think was related to uptime, and you could fix it after the fact by grabbing a shell through the ttl se
by toast0 3y ago
Yes, there was a well published Seagate issue [1] that I think was related to uptime, and you could fix it after the fact by grabbing a shell through the ttl serial on the jumper pins. (Edit: thanks jaclaz for providing a link with more details!) It was claimed Seagate would fix it for you under warranty as well, although shipping a drive always has risks.
HPe had two rounds of enterprise SSDs that failed because the uptime counter overflowed, but I never saw content about fixing those after the fact. And I think I had seen a different SSD uptime based failure a year or so before.
IMHO, it's best to avoid same batch storage, and if that's not possible, stagger the online time to try to give enough time to notice a failure, obtain replacement storage, install replacement stotage, and migrate data. Backups are important too, but it's nicer to have a path towards mostly online recovery. And some mostly replacable data is hard to justify backups for (do I need three copies of format shifted media? probably not, if my online storage fails, I can re-rip)
I don't recall hearing about this for Western Digital drives, but there's some xbox360 stuff that I thought involved the ttl serial on WD drives... It's certainly worth exploring. WD green drives do also have a very short default timeout to park the drive, and as a result can experience a large number of parking cycles in some applications, and the parking ramp can wear out; I don't think this is really recoverable, the heads are likely to get damanged and debris may damage the platters.
[1] https://sites.google.com/site/seagatefix/ https://sites.google.com/site/seagatefix/
- jaclaz 3y agoOnly for the record, at the time the Seagate issue was due to a bug in the firmware, when the drive was powered and found a counter at certain values, it went into a sort of loop and failed to "boot" (the internal OS) further. This happened only on some disk drives because it was initially triggered by a defective testing equipment only on some production lines, see "Root cause" here: https://msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/ https://msfn.org/board/topic/128807-the-solution-for-seagate...