In case you are unaware of the news, below is a brief, followed by my FAQ’s
http://www.betanews.com/article/Seagate_confronts_an_overflow_of_bricked_hard_drives/1232564973
The scope of the problem is so massive, with so many users complaining in so many places online and attributing any drive failure to this problem, that it’s difficult to determine what exactly happened. But it appears that the majority of those posting originally had a 1 TB drive using SD15, which with no warning became not detectable by BIOS after about three months of use.
Some users felt that the problem was more likely to occur with drives made from Thailand.
A KnowledgeBase note from Seagate said the problem was occurring with 21 models of Barracuda 7200.11, ES.2 SATA, and DiamondMax 22 Drives, and provided users with several ways to check whether their models were affected. However, some users reported that, due to the configuration of their storage systems, they were not able to ascertain the identity of their drives. (Normally, it’s Control Panel -> System -> Device Manager -> Disk drives…but that’s only for systems that can still boot.)
________________
After waiting nearly an hour on hold and talking to returns and tech support I received the following info from Seagate support:
________________________
Click for Firmware Patches from Seagate
Barracuda 7200.11, Barracuda ES.2 SATA, DiamondMax 22
ST31000340AS
ST31000340NS
STM31000340AS
ST3750330AS
ST3750330NS
STM3750330AS
ST3750630AS
ST3500320NS
STM3500320AS
ST3640330AS
ST3250310NS
STM31000334AS
ST3640530AS
STM3320614AS
ST3500320AS
STM3160813AS
ST3500620AS
ST3500820AS
ST31500341AS
ST31000333AS
ST3640323AS
ST3640623AS
ST3320613AS
ST3320813AS
ST3160813AS
This website uses cookies.