SMART Failure Predicted on Hard Disk --- Need Advice


#1

AOA,

A friend's laptop has been giving this error for a couple of days now. I googled a bit and found out that it may be related to the wear and tear of the HDD. I found a forum post asking to run HDDScan and post the results for interpretation. I am reproducing the results below and wanted some advice as regards to their interpretation and the recommended action I should take.

Any and all advice/help will be appreciated.

PS: I have already made a backup of all the data on the HDD.

HDDScan S.M.A.R.T. Report

Model: FUJITSU MHY2200BH

Firmware: 0000000B

Serial: K41KT7C2C74L

LBA: 390721968

Report By: HDDScan for Windows version 3.1

Report Date: 11/25/2010 9:09:34 PM

Num Attribute Name Value Worst Raw(hex) Threshold

001 Raw Read Error Rate 100 044 00000000-AE3E 046

002 Throughput performance 100 100 000002DA-0000 030

003 Spin Up Time 100 100 00000000-0001 025

004 Start/Stop Count 099 099 00000000-03C2 000

005 Reallocation Sector Count 100 100 07B2001E-0026 024

007 Seek Error Rate 100 100 00000000-0986 047

008 Seek time Perfomance 100 100 00000000-0000 019

009 PowerOn Hours Count 099 099 00000000-033C 000

010 Spin Retry Count 100 100 00000000-0000 020

012 Device Power Cycle Count 100 100 00000000-035B 000

192 Power-off retract count 100 100 00000000-0077 000

193 Load/unload cycle count 100 100 00000000-1582 000

194 HDA Temperature 100 100 34 C 000

195 Hardware ECC Recovered 100 100 00000000-0016 000

196 Reallocation Event Count 100 100 00011A9E-0026 000

197 Current Pending Sector Count 091 091 00000000-000A 000

198 Uncorrectable Sector Count 085 085 00000000-001F 000

199 UltraDMA CRC Error Count 200 253 00000000-0000 000

200 Write Error Rate 100 100 00000000-44AF 060


#2

What is the overall status reported by smartd ? Fail or OK ?

Considering number of UltraDMA crc error count and write error rate , would suggest getting the drive replaced. Even if error count is not very high at this time , it will eventually increase and disk would fail , specially if the i/o activity is high. If it was linux I would have suggested a longer self test using smartctl and a run with --all for complete info from smartctl to get more info, I guess same should be available from windows command prompt too...