| View previous topic :: View next topic |
| Author |
Message |
qnx
l33t
Joined: 25 Jun 2002
Posts: 638
Location: Göteborg, Sweden
|
 Posted: Tue May 10, 2005 5:37 pm Post subject: Smartctl shows lots of errors that all look the same |
 |
|
Hi,
I have this disk drive:
| Code: | smartctl -i /dev/hda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST3120022A
Serial Number: 5JT02YD7
Firmware Version: 3.06
User Capacity: 120,034,123,776 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
Local Time is: Tue May 10 19:23:27 2005 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled |
I checked disk's error log and got a lot of errors that seem to occur after exacly the power-on time each time:
| Code: | smartctl -l error /dev/hda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 27 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 27 occurred at disk power-on lifetime: 4 hours (0 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 7a 91 00 e0 Error: UNC at LBA = 0x0000917a = 37242
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 78 08 91 00 e0 00 00:08:22.299 READ DMA EXT
25 00 7a 06 91 00 e0 00 00:08:18.317 READ DMA EXT
25 00 7c 04 91 00 e0 00 00:08:18.316 READ DMA EXT
25 00 7e 02 91 00 e0 00 00:08:18.315 READ DMA EXT
25 00 80 00 91 00 e0 00 00:08:18.314 READ DMA EXT
Error 26 occurred at disk power-on lifetime: 4 hours (0 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 7a 91 00 e0 Error: UNC at LBA = 0x0000917a = 37242
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 7a 06 91 00 e0 00 00:08:22.299 READ DMA EXT
25 00 7c 04 91 00 e0 00 00:08:18.317 READ DMA EXT
25 00 7e 02 91 00 e0 00 00:08:18.316 READ DMA EXT
25 00 80 00 91 00 e0 00 00:08:18.315 READ DMA EXT
25 00 80 80 90 00 e0 00 00:08:18.314 READ DMA EXT
Error 25 occurred at disk power-on lifetime: 4 hours (0 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 7a 91 00 e0 Error: UNC at LBA = 0x0000917a = 37242
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 7c 04 91 00 e0 00 00:08:22.299 READ DMA EXT
25 00 7e 02 91 00 e0 00 00:08:18.317 READ DMA EXT
25 00 80 00 91 00 e0 00 00:08:18.316 READ DMA EXT
25 00 80 80 90 00 e0 00 00:08:18.315 READ DMA EXT
25 00 80 00 90 00 e0 00 00:08:18.314 READ DMA EXT
Error 24 occurred at disk power-on lifetime: 4 hours (0 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 7a 91 00 e0 Error: UNC at LBA = 0x0000917a = 37242
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 7e 02 91 00 e0 00 00:08:22.299 READ DMA EXT
25 00 80 00 91 00 e0 00 00:08:18.317 READ DMA EXT
25 00 80 80 90 00 e0 00 00:08:18.316 READ DMA EXT
25 00 80 00 90 00 e0 00 00:08:18.315 READ DMA EXT
25 00 80 80 8f 00 e0 00 00:08:18.314 READ DMA EXT
Error 23 occurred at disk power-on lifetime: 4 hours (0 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 7a 91 00 e0 Error: UNC at LBA = 0x0000917a = 37242
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 80 00 91 00 e0 00 00:08:18.302 READ DMA EXT
25 00 80 80 90 00 e0 00 00:08:18.317 READ DMA EXT
25 00 80 00 90 00 e0 00 00:08:18.316 READ DMA EXT
25 00 80 80 8f 00 e0 00 00:08:18.315 READ DMA EXT
25 00 80 00 8f 00 e0 00 00:08:18.314 READ DMA EXT
|
Should I be worried, or what? 
Cheers,
Jacob
_________________
Registred Linux user #191143!
Abit NF7-S rev. 2.00 (BIOS v. 2.7)
AMD AthlonXP 2500+ (Barton)
PATA Seagate ST3120022A
SATA Seagate ST3200822AS & Silicon Image 3112 chipset
Gentoo Linux  |
|
| Back to top |
|
 |
fctk
Veteran
Joined: 28 Jan 2004
Posts: 1424
Location: Milan, Italy, EU
|
| Posted: Wed May 11, 2005 1:34 pm Post subject: |
|
|
| did you check if cables are correctly connected? also, try asking in the smartmontools mailing list... |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
