Why are Seagate being fingered for this? It's not their SNAFU!
This is 100% Cisco's fsck up because it was Cisco that assumed rather than erred on the side of caution/professionalism by configuring the drives on receipt from their supplier - or on boot up, fancy that! - with the correct parameters/characteristics required to reliably perform the job they will be doing.
There is absolutely nothing wrong with what Seagate did, or did not do!
(Not a Seagate shill, I just think Cisco are entirely at fault here)
Biting the hand that feeds IT
