Seriously tho, while it's good you check HDD for any errors before entrust your data onto them, you sound as if you expect them to have problems. The majority of HDD failures I've seen doesn't even get picked up by SMART. Like jerreece said, the 7200.11 with its firmware glitch was just a fluke (and wouldn't have been detectable by SMART anyway). It has nothing to do with other Seagate products nor future ones.
If anyone is more paranoid with the integrity of their data it'd have to me. I expect every one of them to fail, with the possibility some could fail within their warranty period. That's why I run them on hardware RAID5, the four 1TB drives I use for personal data archival. And it just so happen those four 1TB had the failure-prone 7200.11 firmware SD15 (drives were ST31000340AS). Since I was running RAID5 already I didn't have to worry a single bit about my data, I just updated all of them to SD1A one-by-one when I had the time and from then on they're back to the 'usual' failure rate I expect from them again.
Huh? Now, all joking aside, I'm not sure where that "paranoid" thingy comes from.
Put in a new HDD, do a quick SMART check, notice failure numbers in the thousands/hundreds of thousands, send a quick enquiry... can't see what's more natural.
I prefer normal backups to RAID5 though. RAID doesn't protect against human (or viral) failures... but I guess you do have a standalone backup as well.
October 18, 2010 10:33:36 AM
My log shows 25 errors during active or idle state of unknown type. The first errors occurred 98 hours into lifetime. The last error occurred 366 hours.
Usually what happens is the drive goes offline if I try to download anything to it. Have no trouble moving data back and forth. I use the drive as a secondary backup. It is formatted NTFS but I am running Ubuntu Linux with Ext4 on the main drive, so it could be related to some kind of file-system incompatablity. Problem is once or twice, I've rebooted my machine and the drive hasn't come up, so it appears also controller related. Is there a firmware update?