Only 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 i

Only 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...