SMART ERRORS - ST3500320AS 5 month old

[al3x]

Hi =)



SEAtools detects nothing



HDDlife pro says "urgent screenshot here" : http://pic.ipicture.ru/uploads/081026/1168dvVL24.jpg



Screenshot from mhdd smart info : http://s1.ipicture.ru/uploads/081026/B94z1GBqrm.jpg



I started to check it after i started to have probles with burning data to DVD



Any ideas?



Thank you.

[al3x]

hddscan report
Model: ST3500320AS
Firmware: SD15
Serial: 9QM22G4J
LBA: 976773168

Report By: HDDScan for Windows version 3.1
Report Date: 10/26/2008 03:34:16


Num Attribute Name Value Worst Raw(hex) Threshold

001 Raw Read Error Rate 117 093 000009D2-3B87 006

003 Spin Up Time 095 094 00000000-0000 000

004 Start/Stop Count 100 100 00000000-00CE 020

005 Reallocation Sector Count 100 100 00000000-0685 036

007 Seek Error Rate 055 053 007A02F8-3E9C 030

009 PowerOn Hours Count 096 096 00000000-0E31 000

010 Spin Retry Count 100 100 00000000-0001 097

012 Device Power Cycle Count 100 100 00000000-00CD 020

184 End to End Error 100 100 00000000-0000 099

187 Reported Uncorrectable Error 100 100 00000000-0000 000

188 Command Timeout 100 091 00000000-0294 000

189 High Fly Writes 100 100 00000000-0000 000

190 Airflow Temperature 065 060 35 C 045

194 HDA Temperature 035 040 35 C 000

195 Hardware ECC Recovered 055 030 000009D2-3B87 000

197 Current Pending Sector Count 100 100 00000000-0000 000

198 Uncorrectable Sector Count 100 100 00000000-0000 000

199 UltraDMA CRC Error Count 200 200 00000000-0000 000

[BlackST]

Have you tried different cabling and/or motherboard settings ? Are you overclocking ? Is everything else stable and optimally configured ? If the answer is always NO, probably the drive is developing a weak head. Does the MoBo SMART (if turned on) trigger an alarm ? If no, probably you can live with it, and the errors while burning DVDs are to be found elsewhere (if there were OTHER read errors, you system could crash or hang. If yes, try zero fill the drive i.e. with MHDD or other utility and check again (you'll lose your data).
Still having problems or MoBo triggers an alarm ? Zerofill the drive for privacy and send it back for RMA, and buy another drive. Maybe not Seagate nor WD...
MoBo = motherboard.

[al3x]

what i can change in motherboard settings?

yes, i changed the cable, im not overclocking- evrething else i think fine

yeah i know mwhat is mobo hhh no alarms at all -

[BlackST]

Try reporting your config. to mobo manufacturer, maybe they noticed incompatibilies. Or try a different drive, if ok replace it. Then decide what to do with okd drive. Last- check power supply capacitors for leak or dry, and don't use same rail for hdd and dvd.

[drc]

Wikipedia states:

"Read Error Rate - Indicates the rate of hardware read errors that occurred when reading data from a disk surface. A non-zero value indicates a problem with either the disk surface or read/write heads. Note that Seagate drives often report a raw value that is very high even on new drives, and does not thereby indicate a failure."

Additionally,

"Seek Error Rate - Rate of seek errors of the magnetic heads. If there is a partial failure in the mechanical positioning system, then seek errors will arise. Such a failure may be due to numerous factors, such as damage to a servo, or thermal widening of the hard disk. More seek errors indicates a worsening condition of a disk’s surface or the mechanical subsystem, or both. Note that Seagate drives often report a raw value that is very high, even on new drives, and this does not normally indicate a failure."

http://en.wikipedia.org/wiki/Self-Monit ... attributes

[Doomer]

this on is not good - 005 Reallocation Sector Count 100 100 00000000-0685 036
it means you drive has 1669 remapped bad sectors (kinda strange because Value of that attribute is still 100)

this one is not good too - 188 Command Timeout 100 091 00000000-0294 000
it means 660 commands were aborted because of timeout (drive wasn't able to read or write properly in a reasonable time period)
The other attributes are OK for Seagate

Looks like your disk might have a lot of read errors
I would start data backup