HDD reads slower and slower...

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

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

How about the one from Linux's smartctl?

# smartctl -a /dev/hda

I just reran this to get an updated since I ran disk utilities, turned system
off including its power supply, rebooted to Linux/Debian, etc. I don't see
anything new with a quick glance:

Please use a fixed width font (e.g., Courier) to view this smartctl results
correctly:

# 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: Mon Dec 12 15:32:30 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: (0x00) Error logging NOT 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
ys - 1211181091848
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail
s - 74
4 Start_Stop_Count 0x0032 253 253 000 Old_age
ys - 474
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail
s - 0
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail
ine - 0
7 Seek_Error_Rate 0x000a 164 111 000 Old_age
ys - 343597442371
8 Seek_Time_Performance 0x0027 247 245 187 Pre-fail
s - 161645390127284
9 Power_On_Minutes 0x0032 248 248 000 Old_age
ys - 1839h+20m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail
s - 66
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
s - 63
12 Power_Cycle_Count 0x0032 252 252 000 Old_age
ys - 470
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age
line - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age
line - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age
line - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
line - 0

That one has actually dropped to zero. Presumably it must have been reset by
something.

Probably because I turned the computer off completely for a few minutes?

Those have mostly increased quite a bit, particularly the last pair. Not at all
clear
what those params are supposed to be about, particularly with such high numbers.

Ironic, this guy had problems too like mine:
http://groups.google.com/group/comp...ite_Opern+Shock_Rate_Write_Opern&rnum=5&hl=en
(or http://tinyurl.com/9eowu).

Reading http://scottstuff.net/blog/articles/2005/01/08/anatomy-of-a-drive-failure
was interesting, but a bit technical. Maybe useful to you?

http://smartmontools.sourceforge.net/#FAQ has interesting stuff related to the
tool. A bit technical to me though. Let me know if I should run any other
parameters to try.

207 Spin_High_Current 0x002a 253 252 000 Old_age
ys - 66
208 Spin_Buzz 0x002a 253 252 000 Old_age
ys - 66
209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age
line - 0
96 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
97 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
98 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0

Warning: device does not support Error Logging
SMART Error Log Version: 1
Warning: ATA error count 2186 inconsistent with error log pointer 5

ATA Error Count: 2186 (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 2186 occurred at disk power-on lifetime: 1724 hours (71 days + 20 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 00:00:12.688 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 00:00:12.656 DEVICE RESET

Error 2185 occurred at disk power-on lifetime: 1724 hours (71 days + 20 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 00:00:12.656 DEVICE RESET

Error 2184 occurred at disk power-on lifetime: 1724 hours (71 days + 20 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 0b 4f c2 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
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 50 4f c2 a0 00 35d+06:23:06.720 SMART WRITE LOG
b0 d6 01 50 4f c2 a0 00 35d+06:22:59.712 SMART WRITE LOG
41 ff e0 00 fd 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fc 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fb 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]

Error 2183 occurred at disk power-on lifetime: 1724 hours (71 days + 20 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 0b 4f c2 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
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 50 4f c2 a0 00 35d+06:23:06.720 SMART WRITE LOG
b0 d6 01 50 4f c2 a0 00 35d+06:22:59.712 SMART WRITE LOG
41 ff e0 00 fd 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fc 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fb 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]

Error 2183 occurred at disk power-on lifetime: 1724 hours (71 days + 20 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 0b 4f c2 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
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 50 4f c2 a0 00 35d+06:22:59.712 SMART WRITE LOG
41 ff e0 00 fd 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fc 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fb 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fa 93 e3 00 35d+06:22:59.696 READ VERIFY SECTOR(S) [OBS-5]

Error 2182 occurred at disk power-on lifetime: 1724 hours (71 days + 20 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 40 40 17 03 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
-- -- -- -- -- -- -- -- ---------------- --------------------
c3 ff 01 01 00 00 a0 00 35d+03:54:00.016 [VENDOR SPECIFIC]
b0 da 01 00 4f c2 a0 00 35d+03:53:59.968 SMART RETURN STATUS
c3 e6 01 01 00 00 a0 00 35d+03:53:59.968 [VENDOR SPECIFIC]
c3 ff 01 01 00 00 a0 00 35d+03:53:59.952 [VENDOR SPECIFIC]
b0 da 01 00 4f c2 a0 00 35d+03:53:59.904 SMART RETURN STATUS

Warning: device does not support Self Test Logging
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline Completed without error 00% 1722 -

Device does not support Selective Self Tests/Logging

Main question is why PowerMax doesnt say anything
about it, but the PoweMax has always been rather flakey.

I'd personally just bin the drive.

Yeah, that is what I am planning to do. The drive was from 1999 so that's
about six years. I will try another HDD ribbon cable to check.

--
"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.
( )

 

[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.

How about the one from Linux's smartctl?

# smartctl -a /dev/hda

I just reran this to get an updated since I ran disk utilities, turned
system
off including its power supply, rebooted to Linux/Debian, etc. I don't see
anything new with a quick glance:

Please use a fixed width font (e.g., Courier) to view this smartctl results
correctly:

# 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: Mon Dec 12 15:32:30 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: (0x00) Error logging NOT 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
ys - 1211181091848
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail
s - 74
4 Start_Stop_Count 0x0032 253 253 000 Old_age
ys - 474
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail
s - 0
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail
ine - 0
7 Seek_Error_Rate 0x000a 164 111 000 Old_age
ys - 343597442371
8 Seek_Time_Performance 0x0027 247 245 187 Pre-fail
s - 161645390127284
9 Power_On_Minutes 0x0032 248 248 000 Old_age
ys - 1839h+20m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail
s - 66
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
s - 63
12 Power_Cycle_Count 0x0032 252 252 000 Old_age
ys - 470
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age
line - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age
line - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age
line - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
line - 0

That one has actually dropped to zero. Presumably it must have been reset by
something.

Probably because I turned the computer off completely for a few minutes?

I wouldnt have expected that one to reset on power off.

Ironic, this guy had problems too like mine:
http://groups.google.com/group/comp...ite_Opern+Shock_Rate_Write_Opern&rnum=5&hl=en
(or http://tinyurl.com/9eowu).

Yeah, tho like with many of those, no useful outcome.

Reading
http://scottstuff.net/blog/articles/2005/01/08/anatomy-of-a-drive-failure
was interesting, but a bit technical. Maybe useful to you?

Doesnt look relevant, just the much more common problem of reallocated sectors.

http://smartmontools.sourceforge.net/#FAQ has interesting stuff related to the
tool. A bit technical to me though. Let me know if I should run any other
parameters to try.

Its basically just doing what we are doing manually,
watching the SMART values changing.

I couldnt find any useful documentation on just what
those ones with high numbers with your drive means.

Bit academic really, looks like its whats making it run
very slowly and its a bit academic exactly why that is so.

207 Spin_High_Current 0x002a 253 252 000 Old_age
ys - 66
208 Spin_Buzz 0x002a 253 252 000 Old_age
ys - 66
209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age
line - 0
96 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
97 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
98 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age
line - 0

Warning: device does not support Error Logging
SMART Error Log Version: 1
Warning: ATA error count 2186 inconsistent with error log pointer 5

ATA Error Count: 2186 (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 2186 occurred at disk power-on lifetime: 1724 hours (71 days + 20
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 00:00:12.688 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 00:00:12.656 DEVICE RESET

Error 2185 occurred at disk power-on lifetime: 1724 hours (71 days + 20
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 00:00:12.656 DEVICE RESET

Error 2184 occurred at disk power-on lifetime: 1724 hours (71 days + 20
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 0b 4f c2 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
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 50 4f c2 a0 00 35d+06:23:06.720 SMART WRITE LOG
b0 d6 01 50 4f c2 a0 00 35d+06:22:59.712 SMART WRITE LOG
41 ff e0 00 fd 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fc 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fb 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]

Error 2183 occurred at disk power-on lifetime: 1724 hours (71 days + 20
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 0b 4f c2 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
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 50 4f c2 a0 00 35d+06:23:06.720 SMART WRITE LOG
b0 d6 01 50 4f c2 a0 00 35d+06:22:59.712 SMART WRITE LOG
41 ff e0 00 fd 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fc 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fb 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]

Error 2183 occurred at disk power-on lifetime: 1724 hours (71 days + 20
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 0b 4f c2 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
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d6 01 50 4f c2 a0 00 35d+06:22:59.712 SMART WRITE LOG
41 ff e0 00 fd 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fc 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fb 93 e3 00 35d+06:22:59.712 READ VERIFY SECTOR(S) [OBS-5]
41 ff 00 01 fa 93 e3 00 35d+06:22:59.696 READ VERIFY SECTOR(S) [OBS-5]

Error 2182 occurred at disk power-on lifetime: 1724 hours (71 days + 20
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 40 40 17 03 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
-- -- -- -- -- -- -- -- ---------------- --------------------
c3 ff 01 01 00 00 a0 00 35d+03:54:00.016 [VENDOR SPECIFIC]
b0 da 01 00 4f c2 a0 00 35d+03:53:59.968 SMART RETURN STATUS
c3 e6 01 01 00 00 a0 00 35d+03:53:59.968 [VENDOR SPECIFIC]
c3 ff 01 01 00 00 a0 00 35d+03:53:59.952 [VENDOR SPECIFIC]
b0 da 01 00 4f c2 a0 00 35d+03:53:59.904 SMART RETURN STATUS

Warning: device does not support Self Test Logging
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline Completed without error 00%
2 -

Device does not support Selective Self Tests/Logging


Main question is why PowerMax doesnt say anything
about it, but the PoweMax has always been rather flakey.

I'd personally just bin the drive.

Yeah, that is what I am planning to do. The drive was from 1999 so that's
about six years. I will try another HDD ribbon cable to check.

 

[Folkert Rienstra]

[snip]

Probably because I turned the computer off completely for a few minutes?

I wouldnt have expected that one to reset on power off.

UDMA_CRC errors aren't necessarily the drive's fault.

Yeah, tho like with many of those, no useful outcome.


Doesnt look relevant, just the much more common problem of reallocated sectors.


Its basically just doing what we are doing manually,
watching the SMART values changing.

I couldnt find any useful documentation on just what
those ones with high numbers with your drive means.

http://www.t13.org/docs2005/e05173r0-ACS-SMARTAttributes_List.pdf

Bit academic really, looks like its whats making it run
very slowly and its a bit academic exactly why that is so.

Yeah, god forbid that it turns out to be severe shock related,
as I suggested.

[snip]

 

[Rod Speed]

It does to mine. Nothing wrong with it except very very slow.
Nothing wrong that is, until you run DFT: Excessive Shock.

I meant that power brownouts dont produce a very slow drive.

 

[Rod Speed]

UDMA_CRC errors aren't necessarily the drive's fault.
Duh.

http://www.t13.org/docs2005/e05173r0-ACS-SMARTAttributes_List.pdf

Like I said, those with the increasing high numbers
mostly dont get a mention there, most obviously the
two Shock* attributes and the TA_Increase_Count.

The others in the block I specified are obvious enough.

Yeah, god forbid that it turns out to be
severe shock related, as I suggested.

Not exactly rocket science given the two Shock* attributes.
They clearly arent just shock events with numbers like that
tho. Not at all clear what they are supposed to indicate,
particularly why they always have the same value either.

And I suggested that he run DFT on the drive when
PowerMax didnt say anything about shock, because
I expected that it would have had something to say about
those SMART values which clearly arent normal for that drive.

Less clear why they arent flagged as
indicating a drive with a severe problem.

 

[Folkert Rienstra]

I meant that power brownouts dont produce a very slow drive.

OK, my bad.

 

[Folkert Rienstra]

Like I said, those with the increasing high numbers
mostly dont get a mention there, most obviously the
two Shock* attributes and the TA_Increase_Count.

But their attribute numbers do.

The others in the block I specified are obvious enough.



Not exactly rocket science given the two Shock* attributes.

Which obviously made you remember when I mentioned 'Excessive Shock'.

They clearly arent just shock events with numbers like that tho.

No, looks like they are events logged after the shock event, because of
the shock event.
May explain why the drive is still getting slower by more write events
happening after the shock.
That's what happened with my drive, it was reading normally when I first
got it, but it became immensely slow after I wiped it (Low Level Formatted).

Not at all clear what they are supposed to indicate,
particularly why they always have the same value either.

There are more of those, eg raw read error rate that is the
accumulation counter for all read errors related attributes.

And I suggested that he run DFT on the drive when
PowerMax didnt say anything about shock, because
I expected that it would have had something to say about
those SMART values which clearly arent normal for that drive.

IBMs don't use those attribute numbers.
DFT's SMART section probably isn't even active with non-IBM drives.

 

[J. Clarke]

We have the footage of what you do with
it when things go a tad pear shaped...

Oh sure. Prove it. Put it on putfile.com or somewhere. [grin]

I've reported you to the RSPCPPSTBTI, you'll be soorree...

What does that stand for?

It isnt a time thing, it basically depends on how its
been handled, particularly when unplugging drives etc.

I think the cables were touched 3-4 times within the last few years.
It's pretty rare! Maybe it's the heat? My room can get up to 85
degrees(F) in the heat waves.

One good yank can kill a cable.
Wow.


Its more likely the drive is just dying tho given the SMART data.

OK.

Nobody has mentioned this, so I figure someone should. Before there was
SMART there were ears. Listen to the thing. If it's making repeated
noises that sound like something vibrating (on some drives they are high
pitched these days--some Seagate models sound like a cat crying for
example) those are recalibration attempts and they're generally an
indicator that the drive is trying to deal with a marginal sector. If you
get a lot of those, no matter what SMART is telling you, there is something
wrong either with the drive or with the power or cooling--it should be
backed up and replaced at the earliest opportunity and the cooling and
power checked and repaired if needed before installing the replacement.

 

[Rod Speed]

But their attribute numbers do.

I bet all that means is that the T13 list is pretty
inadequate on those two Shock* attributes.

Cant see why those two should have the same
numbers when the T13 list lists one as TAR
and the other as the software CRC rate.

The T13 list must be just plain wrong with that maxtor drive.

202 is most likely vendor specific like the T13 list says is one possibility.

Which obviously made you remember when I mentioned 'Excessive Shock'.

Nope, I got that when Andy first quoted the
SMART values, before you even commented.

No, looks like they are events logged after
the shock event, because of the shock event.

Maybe. Odd that they have the same numbers
when one is a rate and the other is a count tho.

More likely the names given by smartctl are meaningless and we dont
have anything from maxtor saying what those attributes actually are.

May explain why the drive is still getting slower
by more write events happening after the shock.

That's what happened with my drive, it was reading
normally when I first got it, but it became immensely
slow after I wiped it (Low Level Formatted).

There are more of those, eg raw read error rate that is the
accumulation counter for all read errors related attributes.

IBMs don't use those attribute numbers.
DFT's SMART section probably isn't even active with non-IBM drives.

I thought you said that DFT did report excessive shock with your maxtor drive ?

Hard to believe that it would have got that from other than SMART data.

 

[ANTant]

Nobody has mentioned this, so I figure someone should. Before there was

SMART there were ears. Listen to the thing. If it's making repeated
noises that sound like something vibrating (on some drives they are high
pitched these days--some Seagate models sound like a cat crying for
example) those are recalibration attempts and they're generally an
indicator that the drive is trying to deal with a marginal sector. If you
get a lot of those, no matter what SMART is telling you, there is something
wrong either with the drive or with the power or cooling--it should be
backed up and replaced at the earliest opportunity and the cooling and
power checked and repaired if needed before installing the replacement.

I listened to my HDD during disk tests. I only heard soft clicks, but I
don't know if those were normal clicks or not. They're not annoying loud
clicks or anything. No cat cries for sure.
--
"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.
( )

 

[Peter]

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?

Test it in a different PC. If it still gives you bad results, throw it out.
It is just an old 40GB disk. Not worth thorough troubleshooting. Cheap new
drives are all over the place.

 

[Folkert Rienstra]

I bet all that means is that the T13 list is pretty
inadequate on those two Shock* attributes.

Cant see why

I can.

those two should have the same numbers when the T13 list
lists one as TAR and the other as the

software CRC rate.

ECC rate.

Thermal asperity error means that a head graced the platter
(temperature jump). When the head graces the platter it will
probably not read properly resulting in possible ECC errors.

The T13 list must be just plain wrong with that maxtor drive.

202 is most likely vendor specific like the T13 list says is one possibility.



Nope, I got that when Andy first quoted the
SMART values, before you even commented.

Yeah right.

Maybe. Odd that they have the same numbers
when one is a rate and the other is a count tho.

More likely the names given by smartctl are meaningless and we dont
have anything from maxtor saying what those attributes actually are.





I thought you said that DFT did report excessive shock with your maxtor drive ?

Never said anything about Maxtor.

Hard to believe that it would have got that from other than SMART data.

Mine is an IBM.

 

[Folkert Rienstra]

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.

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.

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?

Yeah, pretty weird that you get no complaints at all and get
the same lousy speed even with a booted CD, so it cant be
the OS config. Most likely something is stopping it using DMA,
tho PowerMax should have complained about that.

Try Hitachi's DFT.

Ehh, I am not going to bother. I think the HDD
is just super old. It is from 1999 so do the math.

That is just plain wrong. That dinosaur I ran it on got
much better results than your maxtor. Those numbers
are much too low to just be the age of the drive.

And its unlikely to be due to the drive having been
dropped either, PowerMax should have picked that up.

Dropped? How so? I haven't opened the
case for ages. Unless you mean earthquakes.

We have the footage of what you do with
it when things go a tad pear shaped...

Oh sure. Prove it. Put it on putfile.com or somewhere. [grin]

I've reported you to the RSPCPPSTBTI, you'll be soorree...

What does that stand for?

Make sure you have the cable on the right way around, you
often dont get DMA if its on backwards, basically because the
system decides that there is something wrong with the cable.

Doubt that.

It has happened, regardless of what you doubt.

If its on the right way around, try a new cable.

Yeah, I can try that but somehow I doubt it is a cable problem.

You have no basis for that doubt. They do go flakey.

Hmm, OK. They are like 3-4 years old. I will try another cable.

However, I haven't opened the case since summer so it is
not like I touched it. Linux's uptime was like 100+ days!

Sure, but due to the nature of ribbon cables, they can
go flakey over time and its cheap to try that possibility.

How long do they usually last?

It isnt a time thing, it basically depends on how its
been handled, particularly when unplugging drives etc.

I think the cables were touched 3-4 times within the last few years.
It's pretty rare! Maybe it's the heat? My room can get up to 85
degrees(F) in the heat waves.

Assuming I don't open the case that often. Say once a year.

One good yank can kill a cable.
Wow.


Its more likely the drive is just dying tho given the SMART data.

OK.

Nobody has mentioned this,

Maybe because it is nonsense?

so I figure someone should. Before there was SMART there were ears.
Listen to the thing. If it's making repeated noises that sound like something
vibrating (on some drives they are high pitched these days --

some Seagate models sound like a cat crying for example)

those are recalibration attempts

Not the crying cat one.

and they're generally an indicator that the drive is trying to deal with a marginal
sector.

That one is the repeated click or thump.

If you get a lot of those, no matter what SMART is telling you, there is
something wrong either with the drive or with the power or cooling -- it
should be backed up and replaced at the earliest opportunity and the cooling
and power checked and repaired if needed before installing the replacement.

If you repaired anything then obviously the drive wasn't the problem
and can be reused after a wipe with the mfgr's diagnostic.

 

[Rod Speed]

I can.

No you cant.

ECC rate.

Yeah, should proof read complicated posts like this
even when I cant be bothered with normal posts.

Thermal asperity error means that a head graced the platter
(temperature jump). When the head graces the platter it will
probably not read properly resulting in possible ECC errors.

Duh. No reason why that and the software ECC rate
should have identical numbers tho, so its unlikely that
that is what Maxtor actually uses those two attributes for.

And its unlikely to be a thermal effect in his case anyway.

And whoever wrote smartctl clearly doesnt agree with
the T13 on those two attributes anyway. And the T13
list is clearly saying that its not chiselled in stone.

Yeah right.

Fraid so, yours was two days later.

 

[ANTant]

As a follow-up, I am currently copying with dd_rescue off KNOPPIX v4.0.2:

$ dd_rescue -V

dd_rescue Version 1.11, (e-mail address removed), GNU GPL
($Id: dd_rescue.c,v 1.50 2005/02/14 00:39:44 garloff Exp $)

root@0[knoppix]# dd_rescue /dev/hdd /dev/hda
dd_rescue: (info): ipos:dd_rescue: (info): ipos: 1588224.0k, opos: 1588224.0k,
xferd:dd_rescue: (info): ipos: 2579456.0k, opos: 2579456.0k, xferd: 2579456.0k
errs: 0, errxfer: 0.0k, succxfer: 2579456.0k
+curr.rate: 171kB/s, avg.rate: 152kB/s, avg.load: 0.3%

Geez, that is so slow. Much slower than 1-2 MB/sec! It seems like this will take a few
days to finish assuming no problems. I hope HDD will make it to the end and no power
outages (UPS connected to hold for like 15 minutes). As you can see no errors yet. Just
freaky slow!

hdd is the old Maxtor HDD that is super slow. hda is my new Seagate 80 GB 7200 RPM HDD.

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.

--
"None preaches better than the ant, and she says nothing." --Ben Franklin
/\___/\
/ /\ /\ \ 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.
( )