| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 96616 | 2009-01-16 19:07:00 | Why Seagate changed the warranty to 3 years? | pctek (84) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 739444 | 2009-01-21 10:01:00 | Hey I have always approved of both brands. Seagate won out with their 5 year warranty. Now there is no difference so the cheaper one wins, which is WD. And things change, it won't necessarily stay that way. Can't say much for WD. I bought a 250GB a while back which has been running nicely (and quiet compared to my 320GB Seagate) Also have a 40GB drive too (2nd hand) They are the only WD drives I own. Most of my stuff is predominantly Seagate or Quantum Only one I've never tried was Samsung Next time I'm buying, It'll probably be a WD, for the same reason you would Considering it was bricking drives yes I think they should "validate" it :horrified I think that's why it's not available yet. Mind you, it won't be downloadable directly. You need to contact Seagate yourself, I imagine they would email you the update with instructions Currently, only the Seagate Barracuda ES.2 series have had their new firmware validated, apparently: seagate.custkb.com Anyone keen to try it? :D |
Agent_24 (57) | ||
| 739445 | 2009-01-21 19:31:00 | Anandtech stated that the firmware bricked their working drives, by the time they went back to Seagate, the update was removed and no word, so I guess Seagate are still working on a fix. | SolMiester (139) | ||
| 739446 | 2009-01-21 20:14:00 | List of affected models: www.zdnet.com.au 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. 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. |
pctek (84) | ||
| 739447 | 2009-01-21 21:19:00 | Then hopefully the new, 'validated' firmware will be available soon I've got a ST3500320AS with SD15... Does anyone know what the "certain circumstances" are that cause the faulty firmware to fail? |
Agent_24 (57) | ||
| 739448 | 2009-01-22 03:42:00 | Then hopefully the new, 'validated' firmware will be available soon I've got a ST3500320AS with SD15... Does anyone know what the "certain circumstances" are that cause the faulty firmware to fail? I've 2 of the above disk as well and am very concerned what may happen. Unfortunately, 1 disk is my main system disk and the other is my backups. |
bk T (215) | ||
| 739449 | 2009-01-22 04:21:00 | Does anyone know what the "certain circumstances" are that cause the faulty firmware to fail? One thing I gathered from the Seagate forums is that failures are happening after restarting a powered-down system. Not sure if this is the main cause or if there are other reasons, or if hibernation etc. has the same effect. I'm not too concerned about the situation now as my drive has been fine for 7-8 months, everything's backed up and it's under warranty. It's suggested that it may just be drives manufactured in December that are affected but then there's others that contradict that. I'm planning to wait for a couple of weeks until a new firmware is released and it's confirmed that it fixes any problems (or doesn't create new ones!) |
mettaverse (12447) | ||
| 739450 | 2009-01-22 10:09:00 | New firmware updates are now available! Hopefully these ones will actually solve the problem, be flashable, and not brick the drives seagate.custkb.com Anyone keen to try?? |
Agent_24 (57) | ||
| 739451 | 2009-01-22 21:25:00 | New firmware updates are now available! Hopefully these ones will actually solve the problem, be flashable, and not brick the drives seagate.custkb.com Anyone keen to try?? Has anyone tried it? |
bk T (215) | ||
| 739452 | 2009-01-22 21:47:00 | I'm too scared to try it. I'm waiting for a week or so in case this one breaks something too! | Nermal (7077) | ||
| 739453 | 2009-01-22 22:57:00 | People have upgraded with success, even from drives bricked by the failed original SD1A upgrade: stx.lithium.com (you'll need to go to the later pages of that thread) There are some people saying that after update, they are getting issues with SMART reporting the drives as failing However, I saw no reports of any drives actually unusable after the latest SD1A upgrade |
Agent_24 (57) | ||
| 1 2 3 4 5 6 7 8 | |||||