High SMART error values on new ST3500418AS

cjp4

Distinguished
Jun 17, 2009
14
0
18,510
Are these SMART values on a brand new ST3500418AS cause for concern? I read about some troubles needing firmware upgrades with current Seagates, but not for this model.

I used SeaTools, and its SMART check displays no problems.

Thanks!


HD Tune: ST3500418AS Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 118 100 6 181373582 Ok
(03) Spin Up Time 97 97 0 0 Ok
(04) Start/Stop Count 100 100 20 10 Ok
(05) Reallocated Sector Count 100 100 36 0 Ok
(07) Seek Error Rate 100 253 30 186966 Ok
(09) Power On Hours Count 100 100 0 2 Ok
(0A) Spin Retry Count 100 100 97 0 Ok
(0C) Power Cycle Count 100 100 20 10 Ok
(B7) (unknown attribute) 100 100 0 0 Ok
(B8) (unknown attribute) 100 100 99 0 Ok
(BB) (unknown attribute) 100 100 0 0 Ok
(BC) (unknown attribute) 100 100 0 0 Ok
(BD) (unknown attribute) 100 100 0 0 Ok
(BE) Airflow Temperature 69 63 45 521994271 Ok
(C2) Temperature 31 40 0 31 Ok
(C3) Hardware ECC Recovered 45 43 0 181373582 Ok
(C5) Current Pending Sector 100 100 0 0 Ok
(C6) Offline Uncorrectable 100 100 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 200 0 0 Ok
(F0) Head Flying Hours 100 253 0 23 Ok
(F1) (unknown attribute) 100 253 0 438778386 Ok
(F2) (unknown attribute) 100 253 0 56809112 Ok

Power On Time : 2
Health Status : Ok


HD Tune: ST3500418AS Information

Firmware version : CC34
Serial number : 6VM20SYE
Capacity : 465.8 GB (~500.1 GB)
Buffer size : 16384 KB
Standard : ATA/ATAPI-0 - SATA II
Supported mode : UDMA Mode 6 (Ultra ATA/133)
Current mode : UDMA Mode 5 (Ultra ATA/100)

S.M.A.R.T : yes
48-bit Address : yes
Read Look-Ahead : yes
Write Cache : yes
Host Protected Area : yes
Device Configuration Overlay : yes
Automatic Acoustic Management: yes
Power Management : yes
Advanced Power Management : no
Power-up in Standby : yes
Security Mode : yes
Firmware Upgradable : yes

Type : NTFS
Bootable : No

 
Since that is a 7200.12 revision of the hard drive, you 'should' be free of the firmware problems. Those as far as I know were strictly related to 7200.11 drives. So you should be good to go.

Did you simply decide to run SMART tests on the drive, or were you experiencing some problem before hand? Or perhaps receive some kind of error during boot?
 

cjp4

Distinguished
Jun 17, 2009
14
0
18,510
I simply used HDTune to take a quick look at the performance, and quickly checked up the SMART info, mainly for the temperature.

No trouble whatsoever so far, around 300 GB of space are filled from backup, so far, including the windows system partition.

HDTune updates the SMART data every few seconds, and if I just let it sit around idly (with the normal background noise of HDD accesses in an idle XP), those big numbers increase all the time.

But...

The "large" numbers (in the Data column of HDTune) seem to reset on a reboot, so I guess it's just some junk display and nothing to worry about. The "Current/Worst" columns are just finde.

Right now:

HD Tune: ST3500418AS Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 120 100 6 1689431 Ok
(03) Spin Up Time 97 97 0 0 Ok
(04) Start/Stop Count 100 100 20 13 Ok
(05) Reallocated Sector Count 100 100 36 0 Ok
(07) Seek Error Rate 100 253 30 228099 Ok
(09) Power On Hours Count 100 100 0 4 Ok
(0A) Spin Retry Count 100 100 97 0 Ok
(0C) Power Cycle Count 100 100 20 13 Ok
(B7) (unknown attribute) 100 100 0 0 Ok
(B8) (unknown attribute) 100 100 99 0 Ok
(BB) (unknown attribute) 100 100 0 0 Ok
(BC) (unknown attribute) 100 100 0 0 Ok
(BD) (unknown attribute) 100 100 0 0 Ok
(BE) Airflow Temperature 72 63 45 471269404 Ok
(C2) Temperature 28 40 0 28 Ok
(C3) Hardware ECC Recovered 45 43 0 1689431 Ok
(C5) Current Pending Sector 100 100 0 0 Ok
(C6) Offline Uncorrectable 100 100 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 200 0 0 Ok
(F0) Head Flying Hours 100 253 0 34 Ok
(F1) (unknown attribute) 100 253 0 439600695 Ok
(F2) (unknown attribute) 100 253 0 102850675 Ok

Power On Time : 4
Health Status : Ok

 

cjp4

Distinguished
Jun 17, 2009
14
0
18,510


Huh? Just because I'm paranoid that does not mean they are not after me!

:heink:
 

wuzy

Distinguished
Jun 1, 2009
900
0
19,010
You forgot to put your tinfoil hat on... :p

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.
 

cjp4

Distinguished
Jun 17, 2009
14
0
18,510
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.
 
G

Guest

Guest
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?