HDD reads slower and slower...

A

ANTant

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No (K60BMHKC). I noticed the HDD was reading
slow like less than 3 MB/sec. Today I noticed it went under 1 MB/sec in some benchmark tests (hdparm
/dev/hda command in Debian/Linux). It is not consistent. It never goes above 5 MB/sec. recently. My other
HDD (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.

Does this mean my Maxtor HDD is dying? I didn't see any disk errors. SMART didn't say anything. What do you
guys think?

Thank you in advance. :)
--
Allah's Apostle said, "Once while a prophet amongst the prophets was taking a rest underneath a tree, an ant bit him. He, therefore, ordered that his luggage be taken away from underneath that tree and then ordered that the dwelling place of the ants should be set on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari, Book 54, Number 536
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
R

Rod Speed

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
(K60BMHKC). I noticed the HDD was reading slow like less than 3
MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
tests (hdparm /dev/hda command in Debian/Linux). It is not
consistent. It never goes above 5 MB/sec. recently. My other HDD
(even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
Does this mean my Maxtor HDD is dying? I didn't see any disk
errors. SMART didn't say anything. What do you guys think?

Show the SMART data using Everest off the Super WinPE bootable CD.
 
B

Bob Willard

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No (K60BMHKC). I noticed the HDD was reading
slow like less than 3 MB/sec. Today I noticed it went under 1 MB/sec in some benchmark tests (hdparm
/dev/hda command in Debian/Linux). It is not consistent. It never goes above 5 MB/sec. recently. My other
HDD (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.

Does this mean my Maxtor HDD is dying? I didn't see any disk errors. SMART didn't say anything. What do you
guys think?

Thank you in advance. :)
Run HDtach, and look at the graph. If you have large areas of bad sectors,
they should show up as performance dips.
 
A

Arno Wagner

Previously said:
Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No (K60BMHKC). I noticed the HDD was reading
slow like less than 3 MB/sec. Today I noticed it went under 1 MB/sec in some benchmark tests (hdparm
/dev/hda command in Debian/Linux). It is not consistent. It never goes above 5 MB/sec. recently. My other
HDD (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
 
A

Arno Wagner

Previously said:
Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
(K60BMHKC). I noticed the HDD was reading slow like less than 3
MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
tests (hdparm /dev/hda command in Debian/Linux). It is not
consistent. It never goes above 5 MB/sec. recently. My other HDD
(even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
Does this mean my Maxtor HDD is dying? I didn't see any disk
errors. SMART didn't say anything. What do you guys think?
Thank you in advance. :)

Can you post the output from smartctl -a /dev/hd<whatever> here?

Arno
 
A

ANTant

Rod Speed said:
(e-mail address removed) wrote:
Show the SMART data using Everest off the Super WinPE bootable CD.

How about the one from Linux's smartctl?

# smartctl -a /dev/hda
smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 40 series (Ultra ATA 66 and Ultra ATA 100)
Device Model: Maxtor 53073U6
Serial Number: K60BMHKC
Firmware Version: DA620CQ0
User Capacity: 30,735,581,184 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 4
ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
Local Time is: Fri Dec 9 12:09:04 2005 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 22) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 1030792418682
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail Always - 73
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 473
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 0
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 132 111 000 Old_age Always - 575525689929
8 Seek_Time_Performance 0x0027 245 245 187 Pre-fail Always - 177648438657628
9 Power_On_Minutes 0x0032 248 248 000 Old_age Always - 1836h+35m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail Always - 65
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 61
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 469
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 5588
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 450483
201 Soft_Read_Error_Rate 0x000a 247 247 000 Old_age Always - 14280766526842
202 TA_Increase_Count 0x000a 001 001 000 Old_age Always - 1692217382266
203 Run_Out_Cancel 0x000b 250 250 180 Pre-fail Always - 6820408333690
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 267642
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 267642
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 65
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 65
209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age Offline - 0
96 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
97 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
98 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 2163 inconsistent with error log pointer 5

ATA Error Count: 2163 (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 2163 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 20d+11:41:17.536 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2162 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
ca 00 02 4b 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2161 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 2d+14:32:27.616 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2160 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2159 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 1d+12:26:58.176 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 1d+12:26:58.128 DEVICE RESET
ca 00 02 8b 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 6f 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 5d c0 07 e0 08 1d+12:26:49.696 WRITE DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


Device does not support Selective Self Tests/Logging


All this was over my head. :)
--
Allah's Apostle said, "Once while a prophet amongst the prophets was taking a rest underneath a tree, an ant bit him. He, therefore, ordered that his luggage be taken away from underneath that tree and then ordered that the dwelling place of the ants should be set on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari, Book 54, Number 536
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
A

ANTant

Bob Willard said:
(e-mail address removed) wrote:
Run HDtach, and look at the graph. If you have large areas of bad sectors,
they should show up as performance dips.

It requires Windows though. I don't have Windows nor want to install it. Thanks though.
--
Allah's Apostle said, "Once while a prophet amongst the prophets was taking a rest underneath a tree, an ant bit him. He, therefore, ordered that his luggage be taken away from underneath that tree and then ordered that the dwelling place of the ants should be set on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari, Book 54, Number 536
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
A

ANTant

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
Can you post the output from smartctl -a /dev/hd<whatever> here?

Arno, here you go. I didn't know this one.

# smartctl -a /dev/hda
smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 40 series (Ultra ATA 66 and Ultra ATA 100)
Device Model: Maxtor 53073U6
Serial Number: K60BMHKC
Firmware Version: DA620CQ0
User Capacity: 30,735,581,184 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 4
ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
Local Time is: Fri Dec 9 12:09:04 2005 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 22) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 1030792418682
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail Always - 73
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 473
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 0
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 132 111 000 Old_age Always - 575525689929
8 Seek_Time_Performance 0x0027 245 245 187 Pre-fail Always - 177648438657628
9 Power_On_Minutes 0x0032 248 248 000 Old_age Always - 1836h+35m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail Always - 65
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 61
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 469
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 5588
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 450483
201 Soft_Read_Error_Rate 0x000a 247 247 000 Old_age Always - 14280766526842
202 TA_Increase_Count 0x000a 001 001 000 Old_age Always - 1692217382266
203 Run_Out_Cancel 0x000b 250 250 180 Pre-fail Always - 6820408333690
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 267642
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 267642
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 65
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 65
209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age Offline - 0
96 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
97 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
98 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 2163 inconsistent with error log pointer 5

ATA Error Count: 2163 (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 2163 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 20d+11:41:17.536 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2162 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
ca 00 02 4b 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2161 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 2d+14:32:27.616 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2160 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2159 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 1d+12:26:58.176 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 1d+12:26:58.128 DEVICE RESET
ca 00 02 8b 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 6f 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 5d c0 07 e0 08 1d+12:26:49.696 WRITE DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


Device does not support Selective Self Tests/Logging


All this information went over my head. :(
--
Allah's Apostle said, "Once while a prophet amongst the prophets was taking a rest underneath a tree, an ant bit him. He, therefore, ordered that his luggage be taken away from underneath that tree and then ordered that the dwelling place of the ants should be set on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari, Book 54, Number 536
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
R

Rod Speed

(e-mail address removed) wrote
How about the one from Linux's smartctl?

Not as readable as the everest display, but it will do fine.
Main problem is that its pretty hard to read when quoted.

The problem clearly isnt due to bad sectors.

Not at all clear what some of the other values are actually about.

Try running Maxtor's PowerMax and see what it thinks of the drive.
# smartctl -a /dev/hda
smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 40 series (Ultra ATA 66 and
Ultra ATA 100)
Device Model: Maxtor 53073U6
Serial Number: K60BMHKC
Firmware Version: DA620CQ0
User Capacity: 30,735,581,184 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 4
ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
Local Time is: Fri Dec 9 12:09:04 2005 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection
activity was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status: ( 0) The previous self-test
routine completed without
error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline
immediate. Auto Offline data
collection on/off support.
Suspend Offline collection
upon new command. Offline
surface scan supported.
Self-test supported. No
Conveyance Self-test
supported. No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging
support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 22) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000a
253 252 000 Old_age Always - 1030792418682 3
Spin_Up_Time 0x0027 199 195 063 Pre-fail Always
- 73 4 Start_Stop_Count 0x0032 253 253 000
Old_age Always - 473 5 Reallocated_Sector_Ct 0x0033
253 253 063 Pre-fail Always - 0 6
Read_Channel_Margin 0x0001 253 253 100 Pre-fail
Offline - 0 7 Seek_Error_Rate 0x000a 132 111
000 Old_age Always - 575525689929 8
Seek_Time_Performance 0x0027 245 245 187 Pre-fail Always
- 177648438657628 9 Power_On_Minutes 0x0032 248 248
000 Old_age Always - 1836h+35m 10 Spin_Retry_Count
0x002b 253 252 223 Pre-fail Always - 65 11
Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always
- 61 12 Power_Cycle_Count 0x0032 252 252 000
Old_age Always - 469 196 Reallocated_Event_Count 0x0008
253 253 000 Old_age Offline - 0 197
Current_Pending_Sector 0x0008 253 253 000 Old_age Offline
- 0 198 Offline_Uncorrectable 0x0008 253 253 000
Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0008
199 199 000 Old_age Offline - 5588 200
Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always
- 450483 201 Soft_Read_Error_Rate 0x000a 247 247 000
Old_age Always - 14280766526842 202 TA_Increase_Count
0x000a 001 001 000 Old_age Always -
1692217382266 203 Run_Out_Cancel 0x000b 250 250 180
Pre-fail Always - 6820408333690 204
Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always
- 267642 205 Shock_Rate_Write_Opern 0x000a 253 252 000
Old_age Always - 267642 207 Spin_High_Current
0x002a 253 252 000 Old_age Always - 65 208
Spin_Buzz 0x002a 253 252 000 Old_age Always
- 65 209 Offline_Seek_Performnce 0x0024 253 253 000
Old_age Offline - 0 96 Unknown_Attribute 0x0004
253 253 000 Old_age Offline - 0 97
Unknown_Attribute 0x0004 253 253 000 Old_age Offline
- 0 98 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0 99 Unknown_Attribute 0x0004
253 253 000 Old_age Offline - 0 100
Unknown_Attribute 0x0004 253 253 000 Old_age Offline
- 0 101 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 2163 inconsistent with error log pointer 5

ATA Error Count: 2163 (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 2163 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 20d+11:41:17.536 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2162 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
ca 00 02 4b 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2161 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 2d+14:32:27.616 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2160 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2159 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 1d+12:26:58.176 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 1d+12:26:58.128 DEVICE RESET
ca 00 02 8b 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 6f 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 5d c0 07 e0 08 1d+12:26:49.696 WRITE DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


Device does not support Selective Self Tests/Logging


All this was over my head. :)

Yeah, its a very cryptic report compared with the everest report.
 
A

ANTant

Rod Speed said:
(e-mail address removed) wrote
Not as readable as the everest display, but it will do fine.
Main problem is that its pretty hard to read when quoted.

You can read
http://groups.google.com/group/[email protected]&hl=en&#doc_f04eab657113476b
or http://tinyurl.com/ayja5 (if the above URL is too long). Be sure to use fixed width font.

The problem clearly isnt due to bad sectors.
Not at all clear what some of the other values are actually about.
Try running Maxtor's PowerMax and see what it thinks of the drive.

OK. I am going to use the one from Ultimate Boot CD: http://www.ultimatebootcd.com/ ... I hope it is 4.21.

# smartctl -a /dev/hda
smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 40 series (Ultra ATA 66 and
Ultra ATA 100)
Device Model: Maxtor 53073U6
Serial Number: K60BMHKC
Firmware Version: DA620CQ0
User Capacity: 30,735,581,184 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 4
ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
Local Time is: Fri Dec 9 12:09:04 2005 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection
activity was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status: ( 0) The previous self-test
routine completed without
error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline
immediate. Auto Offline data
collection on/off support.
Suspend Offline collection
upon new command. Offline
surface scan supported.
Self-test supported. No
Conveyance Self-test
supported. No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging
support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 22) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000a
253 252 000 Old_age Always - 1030792418682 3
Spin_Up_Time 0x0027 199 195 063 Pre-fail Always
- 73 4 Start_Stop_Count 0x0032 253 253 000
Old_age Always - 473 5 Reallocated_Sector_Ct 0x0033
253 253 063 Pre-fail Always - 0 6
Read_Channel_Margin 0x0001 253 253 100 Pre-fail
Offline - 0 7 Seek_Error_Rate 0x000a 132 111
000 Old_age Always - 575525689929 8
Seek_Time_Performance 0x0027 245 245 187 Pre-fail Always
- 177648438657628 9 Power_On_Minutes 0x0032 248 248
000 Old_age Always - 1836h+35m 10 Spin_Retry_Count
0x002b 253 252 223 Pre-fail Always - 65 11
Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always
- 61 12 Power_Cycle_Count 0x0032 252 252 000
Old_age Always - 469 196 Reallocated_Event_Count 0x0008
253 253 000 Old_age Offline - 0 197
Current_Pending_Sector 0x0008 253 253 000 Old_age Offline
- 0 198 Offline_Uncorrectable 0x0008 253 253 000
Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0008
199 199 000 Old_age Offline - 5588 200
Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always
- 450483 201 Soft_Read_Error_Rate 0x000a 247 247 000
Old_age Always - 14280766526842 202 TA_Increase_Count
0x000a 001 001 000 Old_age Always -
1692217382266 203 Run_Out_Cancel 0x000b 250 250 180
Pre-fail Always - 6820408333690 204
Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always
- 267642 205 Shock_Rate_Write_Opern 0x000a 253 252 000
Old_age Always - 267642 207 Spin_High_Current
0x002a 253 252 000 Old_age Always - 65 208
Spin_Buzz 0x002a 253 252 000 Old_age Always
- 65 209 Offline_Seek_Performnce 0x0024 253 253 000
Old_age Offline - 0 96 Unknown_Attribute 0x0004
253 253 000 Old_age Offline - 0 97
Unknown_Attribute 0x0004 253 253 000 Old_age Offline
- 0 98 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0 99 Unknown_Attribute 0x0004
253 253 000 Old_age Offline - 0 100
Unknown_Attribute 0x0004 253 253 000 Old_age Offline
- 0 101 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 2163 inconsistent with error log pointer 5

ATA Error Count: 2163 (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 2163 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 20d+11:41:17.536 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2162 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
ca 00 02 4b 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2161 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 2d+14:32:27.616 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2160 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2159 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 1d+12:26:58.176 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 1d+12:26:58.128 DEVICE RESET
ca 00 02 8b 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 6f 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 5d c0 07 e0 08 1d+12:26:49.696 WRITE DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


Device does not support Selective Self Tests/Logging


All this was over my head. :)
Yeah, its a very cryptic report compared with the everest report.
--
Allah's Apostle said, "Once while a prophet amongst the prophets was taking a rest underneath a tree, an ant bit him. He, therefore, ordered that his luggage be taken away from underneath that tree and then ordered that the dwelling place of the ants should be set on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari, Book 54, Number 536
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
F

Folkert Rienstra

Rod Speed said:
(e-mail address removed) wrote


Not as readable as the everest display, but it will do fine.
Main problem is that its pretty hard to read when quoted.

What a rotten excuse.
No problem at all, just use a proper and properly setup newsclient.
The problem clearly isnt due to bad sectors.

Not at all clear what some of the other values are actually about.

Try running Maxtor's PowerMax and see what it thinks of the drive.
# smartctl -a /dev/hda
smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 40 series (Ultra ATA 66 and
Ultra ATA 100)
Device Model: Maxtor 53073U6
Serial Number: K60BMHKC
Firmware Version: DA620CQ0
User Capacity: 30,735,581,184 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 4
ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
Local Time is: Fri Dec 9 12:09:04 2005 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection
activity was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status: ( 0) The previous self-test
routine completed without
error or no self-test has ever been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline
immediate. Auto Offline data
collection on/off support.
Suspend Offline collection
upon new command. Offline
surface scan supported.
Self-test supported. No
Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 22) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 1030792418682
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail Always - 73
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 473
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 0
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 132 111 000 Old_age Always - 575525689929
8 Seek_Time_Performance 0x0027 245 245 187 Pre-fail Always - 177648438657628
9 Power_On_Minutes 0x0032 248 248 000 Old_age Always - 1836h+35m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail Always - 65
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 61
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 469
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 5588
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 450483
201 Soft_Read_Error_Rate 0x000a 247 247 000 Old_age Always - 14280766526842
202 TA_Increase_Count 0x000a 001 001 000 Old_age Always - 1692217382266
203 Run_Out_Cancel 0x000b 250 250 180 Pre-fail Always - 6820408333690
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 267642
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 267642
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 65
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 65
209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age Offline - 0
96 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
97 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
98 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 2163 inconsistent with error log pointer 5

ATA Error Count: 2163 (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 2163 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 20d+11:41:17.536 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2162 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
ca 00 02 4b 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2161 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 2d+14:32:27.616 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2160 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2159 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 1d+12:26:58.176 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 1d+12:26:58.128 DEVICE RESET
ca 00 02 8b 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 6f 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 5d c0 07 e0 08 1d+12:26:49.696 WRITE DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


Device does not support Selective Self Tests/Logging


All this was over my head. :)

Yeah, its a very cryptic report compared with the everest report.
 
R

Rod Speed

Folkert Rienstra said:
What a rotten excuse.
No problem at all, just use a proper and properly setup newsclient.

Pity yours wrapped, ****wit pseudokraut.
The problem clearly isnt due to bad sectors.

Not at all clear what some of the other values are actually about.

Try running Maxtor's PowerMax and see what it thinks of the drive.
# smartctl -a /dev/hda
smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5
Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 40 series (Ultra ATA 66 and
Ultra ATA 100)
Device Model: Maxtor 53073U6
Serial Number: K60BMHKC
Firmware Version: DA620CQ0
User Capacity: 30,735,581,184 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 4
ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
Local Time is: Fri Dec 9 12:09:04 2005 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection
activity was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status: ( 0) The previous self-test
routine completed without
error or no self-test has
ever been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline
immediate. Auto Offline data
collection on/off support.
Suspend Offline collection
upon new command. Offline
surface scan supported.
Self-test supported. No
Conveyance Self-test
supported. No Selective
Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before
entering power-saving mode.
Supports SMART auto save
timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging
support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 22) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000a
253 252 000 Old_age Always - 1030792418682 3
Spin_Up_Time 0x0027 199 195 063 Pre-fail
Always - 73 4 Start_Stop_Count 0x0032 253
253 000 Old_age Always - 473 5
Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail
Always - 0 6 Read_Channel_Margin 0x0001 253
253 100 Pre-fail Offline - 0 7 Seek_Error_Rate
0x000a 132 111 000 Old_age Always -
575525689929 8 Seek_Time_Performance 0x0027 245 245 187
Pre-fail Always - 177648438657628 9 Power_On_Minutes
0x0032 248 248 000 Old_age Always -
1836h+35m 10 Spin_Retry_Count 0x002b 253 252 223
Pre-fail Always - 65 11 Calibration_Retry_Count 0x002b
253 252 223 Pre-fail Always - 61 12
Power_Cycle_Count 0x0032 252 252 000 Old_age
Always - 469 196 Reallocated_Event_Count 0x0008 253
253 000 Old_age Offline - 0 197
Current_Pending_Sector 0x0008 253 253 000 Old_age
Offline - 0 198 Offline_Uncorrectable 0x0008 253
253 000 Old_age Offline - 0 199
UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
Offline - 5588 200 Multi_Zone_Error_Rate 0x000a 253
252 000 Old_age Always - 450483 201
Soft_Read_Error_Rate 0x000a 247 247 000 Old_age
Always - 14280766526842 202 TA_Increase_Count
0x000a 001 001 000 Old_age Always -
1692217382266 203 Run_Out_Cancel 0x000b 250 250 180
Pre-fail Always - 6820408333690 204
Shock_Count_Write_Opern 0x000a 253 252 000 Old_age
Always - 267642 205 Shock_Rate_Write_Opern 0x000a
253 252 000 Old_age Always - 267642 207
Spin_High_Current 0x002a 253 252 000 Old_age
Always - 65 208 Spin_Buzz 0x002a 253
252 000 Old_age Always - 65 209
Offline_Seek_Performnce 0x0024 253 253 000 Old_age
Offline - 0 96 Unknown_Attribute 0x0004 253
253 000 Old_age Offline - 0 97 Unknown_Attribute
0x0004 253 253 000 Old_age Offline - 0 98
Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0 99 Unknown_Attribute 0x0004 253
253 000 Old_age Offline - 0 100 Unknown_Attribute
0x0004 253 253 000 Old_age Offline - 0 101
Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 2163 inconsistent with error log pointer 5

ATA Error Count: 2163 (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 2163 occurred at disk power-on lifetime: 1721 hours (71 days
+ 17 hours)
When the command that caused the error occurred, the device was in
an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 20d+11:41:17.536 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2162 occurred at disk power-on lifetime: 1721 hours (71 days
+ 17 hours)
When the command that caused the error occurred, the device was in
an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
ca 00 02 4b 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2161 occurred at disk power-on lifetime: 1721 hours (71 days
+ 17 hours)
When the command that caused the error occurred, the device was in
an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 2d+14:32:27.616 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2160 occurred at disk power-on lifetime: 1721 hours (71 days
+ 17 hours)
When the command that caused the error occurred, the device was in
an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2159 occurred at disk power-on lifetime: 1721 hours (71 days
+ 17 hours)
When the command that caused the error occurred, the device was in
an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 1d+12:26:58.176 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 1d+12:26:58.128 DEVICE RESET
ca 00 02 8b 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 6f 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 5d c0 07 e0 08 1d+12:26:49.696 WRITE DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl
-t]


Device does not support Selective Self Tests/Logging


All this was over my head. :)

Yeah, its a very cryptic report compared with the everest report.
 
A

Arno Wagner

Arno, here you go. I didn't know this one.

I think the clue is in attribute 7 and 8. It seems seeking correctly
has really become a challenge for this drive. That would explain the
slowdown. It seems when it finds a sector it can read and write
correctly, since it has no reallocated secors at all. The high
read-error rates are likely not accurate head positioning.

It could be the PSU. It could be (unlikely) a servo driver
in the drive going bad. It could be (also unlikely) strong
vibration from something else (other drive?).

My first guess would be a PSU with weak or overloaded 12V line. The
head-servo is droven from that. Have you added any power-hungry
hardware before this problem became obvous, like a modern graphics
card or a fater CPU?

Can you describe you PSU a bit? Modeal, manufacturer, power rating,
current ratings on the individual outputs (5V and 12V are what matters)?
Can you also state the CPU and graphics card you have?

Arno
 
A

ANTant

I think the clue is in attribute 7 and 8. It seems seeking correctly
has really become a challenge for this drive. That would explain the
slowdown. It seems when it finds a sector it can read and write
correctly, since it has no reallocated secors at all. The high
read-error rates are likely not accurate head positioning.
It could be the PSU. It could be (unlikely) a servo driver
in the drive going bad. It could be (also unlikely) strong
vibration from something else (other drive?).

I doubt it. I haven't changed anything recently since summer.

My first guess would be a PSU with weak or overloaded 12V line. The
head-servo is droven from that. Have you added any power-hungry
hardware before this problem became obvous, like a modern graphics
card or a fater CPU?

Not changed recently. See my secondary machine on
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ... :)

Can you describe you PSU a bit? Modeal, manufacturer, power rating,
current ratings on the individual outputs (5V and 12V are what matters)?
Can you also state the CPU and graphics card you have?

Enlight Power Supply (EN-8341934; Model: HPC-340-101; 340 watts).
--
Allah's Apostle said, "Once while a prophet amongst the prophets was taking a rest underneath a tree, an ant bit him. He, therefore, ordered that his luggage be taken away from underneath that tree and then ordered that the dwelling place of the ants should be set on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari, Book 54, Number 536
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
A

ANTant

As a follow-up, I did some HDD benchmarks outside of my installed Debian/Linux.

I can confirm that with KNOPPIX v4.0.2's bootable CD, hdparm -tT showed the same results for
slow disk access speeds.

I also used Ultimate Boot CD v3.3 (Full) from http://www.ultimatebootcd.com/... I ran its System
Speed Test 32 v4.78 (http://user.rol.ru/~dxover/speedsys/) and got:

PIO 4 UDMA 4(4) Cache: 2048 KB

--

Fast Test:

Average/Max Seek Time: 12.41/152.8 ms
Random Seek Time: 14.32 ms
Track-to-track seek: 2.31 ms
Random Access Time: 18.82 ms
Buffered Read Speed: 786227 KB/sec
Linear Verify Speed: 5094 KB/sec
Linear Read Speed: 1294 KB/sc

23.83 HD Speed (don't know how fast this is: MB? KB?). It did say slower than SHD3062(110 MB)
according to the graph.

--

Full Test:

Average/Max Seek Time: 12.67/233.64 ms
Random Seek Time: 10.44 ms
Track-to-track seek: 2.52 ms
Random Access Time: 18.33 ms
Buffered Read Speed: 795757 KB/sec
Linear Verify Speed: <unknown and it was going super slow so I aborted here> ... Going from
track 0 to 57 took like 10 minutes!
Linear Read Speed: 2130 KB/sec (only up to 0 to 800 tracks before I aborted it)


These results look bad, right?


Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No (K60BMHKC). I noticed the HDD was reading
slow like less than 3 MB/sec. Today I noticed it went under 1 MB/sec in some benchmark tests (hdparm
/dev/hda command in Debian/Linux). It is not consistent. It never goes above 5 MB/sec. recently. My other
HDD (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
Does this mean my Maxtor HDD is dying? I didn't see any disk errors. SMART didn't say anything. What do you
guys think?
Thank you in advance. :)

--
"The general, unable to control his irritation, will launch his men to the assault like swarming ants, with the result that one-third of his men are slain, while the town still remains untaken. Such are the disastrous effects of a siege." --Chapter 3 in Sun Tzu's The Ancient Art of War (Translated by Lionel Giles)
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
R

Rod Speed

As a follow-up, I did some HDD benchmarks outside of my installed
Debian/Linux.

I can confirm that with KNOPPIX v4.0.2's bootable CD, hdparm -tT
showed the same results for slow disk access speeds.

I also used Ultimate Boot CD v3.3 (Full) from
http://www.ultimatebootcd.com/... I ran its System Speed Test 32
v4.78 (http://user.rol.ru/~dxover/speedsys/) and got:

PIO 4 UDMA 4(4) Cache: 2048 KB

--

Fast Test:

Average/Max Seek Time: 12.41/152.8 ms
Random Seek Time: 14.32 ms
Track-to-track seek: 2.31 ms
Random Access Time: 18.82 ms
Buffered Read Speed: 786227 KB/sec
Linear Verify Speed: 5094 KB/sec
Linear Read Speed: 1294 KB/sc

23.83 HD Speed (don't know how fast this is: MB? KB?). It did say
slower than SHD3062(110 MB) according to the graph.

--

Full Test:

Average/Max Seek Time: 12.67/233.64 ms
Random Seek Time: 10.44 ms
Track-to-track seek: 2.52 ms
Random Access Time: 18.33 ms
Buffered Read Speed: 795757 KB/sec
Linear Verify Speed: <unknown and it was going super slow so I
aborted here> ... Going from track 0 to 57 took like 10 minutes!
Linear Read Speed: 2130 KB/sec (only up to 0 to 800 tracks before I
aborted it)


These results look bad, right?

Slow, certainly. Much worse than the 250G Samsung in the PVR
with System Speed Test 32 v4.78 from the Ultimate Boot CD.
 
R

Rod Speed

Slow, certainly. Much worse than the 250G Samsung in the PVR
with System Speed Test 32 v4.78 from the Ultimate Boot CD.

Just ran it on a rather dinsoaury old Compaq with an 8G seagate
and its much faster than yours. You've clearly got a real problem.

See what PowerMax has to say about the drive.
 
A

ANTant

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0)
Not as readable as the everest display, but it will do fine.
Main problem is that its pretty hard to read when quoted.
The problem clearly isnt due to bad sectors.
Not at all clear what some of the other values are actually about.
Try running Maxtor's PowerMax and see what it thinks of the
drive.

I ran all of Maxtor PowerMax v4.21's tests (quick, full read, and
burn-in) that took many hours (8?). No errors from them (all
passed). Weird, huh?

I posted results of HDD benchmarks from Ultimate Boot CD v3.3
(Full) from http://www.ultimatebootcd.com/ ... I ran its System
Speed Test 32 v4.78 (http://user.rol.ru/~dxover/speedsys/). See my
other newsgroup reply on that.

USE FIXED WIDTH FONT (E.G., COURIER FONT) TO VIEW THIS SECTION
PROPERLY:
# smartctl -a /dev/hda
smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 40 series (Ultra ATA 66 and
Ultra ATA 100)
Device Model: Maxtor 53073U6
Serial Number: K60BMHKC
Firmware Version: DA620CQ0
User Capacity: 30,735,581,184 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 4
ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
Local Time is: Fri Dec 9 12:09:04 2005 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection
activity was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status: ( 0) The previous self-test
routine completed without
error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline
immediate. Auto Offline data
collection on/off support.
Suspend Offline collection
upon new command. Offline
surface scan supported.
Self-test supported. No
Conveyance Self-test
supported. No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging
support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 22) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000a
253 252 000 Old_age Always - 1030792418682 3 Spin_Up_Time
0x0027 199 195 063 Pre-fail Always - 73 4 Start_Stop_Count
0x0032 253 253 000 Old_age Always - 473 5
Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 0
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 132 111 000 Old_age Always -
575525689929 8 Seek_Time_Performance 0x0027 245 245 187
Pre-fail Always - 177648438657628 9 Power_On_Minutes 0x0032
248 248 000 Old_age Always - 1836h+35m 10 Spin_Retry_Count
0x002b 253 252 223 Pre-fail Always - 65 11
Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always -
61 12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always -
469 196 Reallocated_Event_Count 0x0008 253 253 000 Old_age
Offline - 0 197 Current_Pending_Sector 0x0008 253 253 000
Old_age Offline - 0 198 Offline_Uncorrectable 0x0008 253 253
000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0008 199
199 000 Old_age Offline - 5588 200 Multi_Zone_Error_Rate
0x000a 253 252 000 Old_age Always - 450483 201
Soft_Read_Error_Rate 0x000a 247 247 000 Old_age Always -
14280766526842 202 TA_Increase_Count 0x000a 001 001 000
Old_age Always - 1692217382266 203 Run_Out_Cancel 0x000b 250
250 180 Pre-fail Always - 6820408333690 204
Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always -
267642 205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age
Always - 267642 207 Spin_High_Current 0x002a 253 252 000
Old_age Always - 65 208 Spin_Buzz 0x002a 253 252 000 Old_age
Always - 65 209 Offline_Seek_Performnce 0x0024 253 253 000
Old_age Offline - 0 96 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0 97 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0 98 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0 99 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0 100 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0 101 Unknown_Attribute 0x0004 253 253 000
Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 2163 inconsistent with error log pointer 5

ATA Error Count: 2163 (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 2163 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 20d+11:41:17.536 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2162 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
ca 00 02 4b 00 08 e0 08 20d+11:41:07.952 WRITE DMA

Error 2161 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 2d+14:32:27.616 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2160 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA

Error 2159 occurred at disk power-on lifetime: 1721 hours (71 days +
17 hours) When the command that caused the error occurred, the
device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 1d+12:26:58.176 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 1d+12:26:58.128 DEVICE RESET
ca 00 02 8b 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 6f 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 5d c0 07 e0 08 1d+12:26:49.696 WRITE DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


Device does not support Selective Self Tests/Logging


All this was over my head. :)
Yeah, its a very cryptic report compared with the everest report.

Yeah, but it shows more datas than Everest. I just don't have
Windows installed on this box. :( So far, two people said HDD
seems to be having problems reading even though I have NO idea
what all that information meant. :)
--
"The general, unable to control his irritation, will launch his men to the assault like swarming ants, with the result that one-third of his men are slain, while the town still remains untaken. Such are the disastrous effects of a siege." --Chapter 3 in Sun Tzu's The Ancient Art of War (Translated by Lionel Giles)
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
A

ANTant

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
Can still be the PSU. They degrade over time.

If it was PSU, wouldn't my other HDD be affected too?

You have a second machine? Then put the HDD in there and run
the hdparm benchmarks there!
Nope.
--
"The general, unable to control his irritation, will launch his men to the assault like swarming ants, with the result that one-third of his men are slain, while the town still remains untaken. Such are the disastrous effects of a siege." --Chapter 3 in Sun Tzu's The Ancient Art of War (Translated by Lionel Giles)
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top