The problem with the 7200.11 series bricking, which has been in the news for the last month, was what really got the ball rolling. The Seagate employee says that is an old problem that was difficult to diagnose. A log or journal is written to in the firmware when certain events occur. If this reaches 320 entries and the drive is powered down, it will produce errors during initialization and not report information to the BIOS. Engineers quickly began work on a new firmware update to prevent this from happening.
Normally, a customer would go through the usual process of contacting customer support for the new preventative update and “this firmware had to go through five different checks to make sure it applies to the specific conditions to qualify sending to a customer, before now. 5 chances for us to go 'your drive needs the other (or none) firmware update'.” However, management, in order to quell the possibility of liability for drive failures, pushed a general public release of the firmware. “Suddenly, it's down to one check, and even that was more designed for a contingency just in case the wrong firmware was sent out.”