Seagate yesterday released a fix to a bug in its current generation of drives that caused them to become undetectable by a computer. Users have found, however, that the fix breaks 500GB drives — the fix has since been retracted.
A member of Seagate's community forums raised the issue in November 2008, with Seagate taking close to two months to offer a fix.
The bug affects a significant portion of not only Seagate's Barracuda 7200.11 drives, but Barracuda ES.2 SATA and Maxtor DiamondMax 22 drives. Forums across the internet have been filled with warnings not to buy drives that feature the SD15 revision of firmware; however, Seagate's own documentation shows that SD16, SD17, SD18 and SD19 are also affected within certain model numbers.
This is not the first time Seagate has had a firmware issue with the 7200.11 series of drives. The SD04 and SD14 firmware revisions were found to be under-performing because they weren't accessing the full cache of the drives, and were replaced with version AD14 to fix this.
The new SD1A firmware was meant to be preventative only, but some users have found success updating and reviving already dead drives, according to Seagate's forums.
Users of Seagate's Barracuda 7200.11 500GB product, however, have found that the update "bricks" their drives — terminology used in the tech industry to mean that the unit is dead.
Seagate has since removed the firmware update, claiming that it is "In Validation".
US customers have been offered free data recovery should the firmware bug have resulted in data loss — CNET Australia is waiting on confirmation to see if this is also offered locally, and what impact this has on hard drives included in stand-alone units such as DVRs.
The affected drives are listed below.
| Drive type | Drive model | Firmware revision |
| Barracuda 7200.11 | ST3500320AS ST3640330AS ST3750330AS ST31000340AS |
SD15, SD16, SD17, SD18 |
| Barracuda 7200.11 | ST31500341AS ST31000333AS ST3640323AS ST3640623AS ST3320613AS ST3320813AS ST3160813AS |
All |
| Barracuda ES.2 SATA | ST3250310NS ST3500320NS ST3750330NS ST31000340NS |
All |
| DiamondMax 22 | STM3500320AS STM3750330AS STM31000340AS |
MX15 or higher |
| DiamondMax 22 | STM31000334AS STM3320614AS STM3160813AS |
All |
I'm one of those with a bricked drive after the firmware update.
Actually they released two firmwares, the first one didn't even recognize the drive. A few hours later they released the second firmware which is the one that bricked all 500gb drives.