During power up, if the Event Log counter is at entry 320, or a multiple of (320 + x*256), and if a particular data fill pattern (dependent on the type of tester used during the drive manufacturing test process) had been present in the reserved-area system tracks when the drive's reserved-area file system was created during manufacturing (note this is not the Operating System's file system, but is instead an area reserved outside the drive's logical block address space that is used for drive operating data structures and storage), firmware will incorrectly allow the Event Log pointer to increment past the end of the Event Log data structure. This error is detected and results in an "Assert Failure", which causes the drive to hang as a failsafe measure. When the drive enters failsafe further updates to the counter become impossible and the condition will persist through all subsequent power cycles.
The problem can only occur if a power cycle initialization occurs when the Event Log is at 320 or some multiple of 256 thereafter. Once a drive is in this state, an end user will not be able to resolve/recover existing failed drives. Recovery of failed drive requires Seagate technical intervention. However, the problem can be prevented by updating drive firmware to a newer version and/or by keeping the drive powered on until a newer firmware version is available.
Note that in order for a drive to be susceptible to this issue, it must have both the firmware revision that contains the issue, have been tested through the specific manufacturing process, and be power cycled.
To test your drive for this vulnerability, and to obtain the firmware update, please use the Seagate link below and follow the instructions carefully. If your drives are configured in a RAID, please see the additional instructions below. Here is the link to the Seagate Knowledgebase page for this issue: http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
| Barracuda 7200.11 model | AS400 Item | Size |
|---|---|---|
| ST31000340AS | 804527, 601109, 601362, 306110, 305465 | 1TB |
| ST3750330AS | 600801 | 750GB |
| ST3500320AS | 601696 | 500GB |
| ST31500341AS | 306688, 306705, 307001, 601704 | 1.5TB |
Topic: Drive Hang after Power Cycle
Date: 1/16/09
Products: Barracuda 7200.11, Barracuda ES.2 (SATA), DiamondMax 22, FreeAgent Desk, Maxtor
OneTouch 4, SV35.3, SV35.4
For Immediate Release
The content on this page was distributed to blog sites and specific press and analysts on Friday, January 16th.
Customer Update
Seagate has isolated a potential firmware issue in certain products, including some Barracuda 7200.11 hard drives and related drive families based on their product platform*, manufactured through December 2008. In some circumstances, the data on the hard drives may become inaccessible to the user when the host system is powered on. Retail products potentially affected include the Seagate FreeAgent® Desk and Maxtor OneTouch® 4 storage solutions.
As part of our commitment to customer satisfaction, we are offering a free firmware upgrade to those with affected products. To determine whether your product is affected, please visit the Seagate Support web site at http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931.
Support is also available through Seagate's call center: 1-800-SEAGATE (1 800 732-4283)
Customers can expedite assistance by sending an email to Seagate (discsupport@seagate.com). Please include the following disk drive information: model number, serial number and current firmware revision. We will respond, promptly, to your email request with appropriate instructions.
For a list of international telephone numbers to Seagate Support and alternative methods of contact, please access http://www.seagate.com/www/en-us/about/contact_us/
Seagate has implemented a containment action to ensure that all manufacturing test processes write a "benign" data fill pattern that does not trigger the error condition. This change is already a permanent part of the test process. All drives with a date of manufacture January 12, 2009 and later are not affected by this issue as they have been manufactured with this corrected test process. In addition, Seagate is releasing updated firmware that will make a drive immune to this failure regardless of the date of manufacture.
*There is no safety issue with these products.
|