HDD reads slower and slower...

A

ANTant

As a follow-up, I did some HDD benchmarks outside of my installed
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.
Click to expand...
See what PowerMax has to say about the drive.
Click to expand...

Ouch. I posted the result in my other reply.
--
"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

Arno Wagner

If it was PSU, wouldn't my other HDD be affected too?
Click to expand...

It might not be as sensitive to this problem. It might be the
HDD itself that has the problem, but then it would need to
be somethign related to the servos and they are usually
pretty reliable.

This type of problem is hard to debug. The best choice usually is
changin components until the problem goes away.

Arno
 
R

Rod Speed

(e-mail address removed) wrote
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?
Click to expand...

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.

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.

If its on the right way around, try a new cable.
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. :)
Click to expand...
Click to expand...
Yeah, its a very cryptic report compared with the everest report.
Click to expand...

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. :)\ _ / Please remove ANT if replying by
e-mail. ( )
Click to expand...
 
A

ANTant

Rod Speed said:
(e-mail address removed) wrote
Click to expand...
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.
Yeah.


Try Hitachi's DFT.
Click to expand...

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

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.
Click to expand...

Doubt that.

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

Yeah, I can try that but somehow I doubt it is a cable problem.
However, I haven't opened the case since summer so it is not like I
touched it. :) Linux's uptime was like 100+ days!

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.
Click to expand...
USE FIXED WIDTH FONT (E.G., COURIER FONT) TO VIEW THIS SECTION
PROPERLY:
Click to expand...
# 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. :)
Click to expand...
Yeah, its a very cryptic report compared with the everest report.
Click to expand...

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. :)
Click to expand...
Click to expand...
--
"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.
( )
 
F

Folkert Rienstra

Arno Wagner said:
It might not be as sensitive to this problem.
Click to expand...

Yeah, it must be.
It obviously can't be the cable between the drive and the supply.
It might be the HDD itself that has the problem, but then it would
need to be somethign related to the servos and they are usually pretty
reliable.
Click to expand...

Yeah, obviously can't be the supply regulators on the board itself either.
This type of problem is hard to debug.
Click to expand...

You mean troubleshoot don't you.
The best choice usually is changin components until the problem goes away.
Click to expand...

Which is called trouble shooting if you put some common sense into that.
 
F

Folkert Rienstra

Rod Speed said:
(e-mail address removed) wrote
Click to expand...
Weird, huh?
Click to expand...

That can happen with drives that suffered from severe shock.
I have one.
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.

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.
Click to expand...

You still get UDMA 33.
If its on the right way around, try a new cable.
Click to expand...

[snip]
 
R

Rod Speed

(e-mail address removed) wrote
Ehh, I am not going to bother. I think the HDD
is just super old. It is from 1999 so do the math. :)
Click to expand...

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.
Doubt that.
Click to expand...

It has happened, regardless of what you doubt.
Yeah, I can try that but somehow I doubt it is a cable problem.
Click to expand...

You have no basis for that doubt. They do go flakey.
However, I haven't opened the case since summer so it is
not like I touched it. :) Linux's uptime was like 100+ days!
Click to expand...

Sure, but due to the nature of ribbon cables, they can
go flakey over time and its cheap to try that possibility.
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. :)
o o| | Ant's Quality Foraged Links (AQFL):
http://aqfl.net
Click to expand...
Click to expand...
\ _ / Please remove ANT if replying by
e-mail. ( )
Click to expand...
 
R

Rod Speed

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

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
ys - 1030792418682
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail
s - 73
4 Start_Stop_Count 0x0032 253 253 000 Old_age
ys - 473
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 132 111 000 Old_age
ys - 575525689929
8 Seek_Time_Performance 0x0027 245 245 187 Pre-fail
s - 177648438657628
9 Power_On_Minutes 0x0032 248 248 000 Old_age
ys - 1836h+35m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail
s - 65
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
s - 61
12 Power_Cycle_Count 0x0032 252 252 000 Old_age
ys - 469
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 - 5588
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age
ys - 450483
Click to expand...
201 Soft_Read_Error_Rate 0x000a 247 247 000 Old_age
ys - 14280766526842
202 TA_Increase_Count 0x000a 001 001 000 Old_age
ys - 1692217382266
203 Run_Out_Cancel 0x000b 250 250 180 Pre-fail
s - 6820408333690
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age
ys - 267642
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age
ys - 267642
Click to expand...

On further thought, this block looks bad. Not completely clear what
they actually mean, but you dont normally see those very high numbers
with maxtor drives, do it looks like the drive is pretty sick.

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.
207 Spin_High_Current 0x002a 253 252 000 Old_age
ys - 65
208 Spin_Buzz 0x002a 253 252 000 Old_age
ys - 65
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

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.
( )
Click to expand...
 
F

Folkert Rienstra

Rod Speed said:
Rod Speed said:
(e-mail address removed) wrote:
Click to expand...
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.
Click to expand...
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?
Click to expand...
Show the SMART data using Everest off the Super WinPE bootable CD.
Click to expand...

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
Click to expand...
201 Soft_Read_Error_Rate 0x000a 247 247 000 Old_age
ys - 14280766526842
202 TA_Increase_Count 0x000a 001 001 000 Old_age
ys - 1692217382266
203 Run_Out_Cancel 0x000b 250 250 180 Pre-fail
s - 6820408333690
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age
ys - 267642
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age
ys - 267642
Click to expand...

On further thought,
Click to expand...

Nah, you just picked that up from my post.
this block looks bad.
Click to expand...

Yup, you managed to mangle that quoting very comprehensively indeed.
There's even partial words missing.
Not completely clear what they actually mean,
Click to expand...

No kidding.
but you dont normally see those very high numbers
with maxtor drives, do it looks like the drive is pretty sick.

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.
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. :)
o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
Click to expand...
\ _ / Please remove ANT if replying by e-mail.
( )
Click to expand...
Click to expand...
 
A

ANTant

Rod Speed said:
(e-mail address removed) wrote
Click to expand...
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.
Click to expand...
And its unlikely to be due to the drive having been
dropped either, PowerMax should have picked that up.
Click to expand...

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

It has happened, regardless of what you doubt.
Click to expand...
You have no basis for that doubt. They do go flakey.
Click to expand...

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

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

How long do they usually last? Assuming I don't open the case that often.
Say once a year.
 
A

ANTant

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0)
That can happen with drives that suffered from severe shock.
I have one.
Click to expand...

Shock from electrcity? Isn't that what APC UPS supposed to stop? I
know there was recent power hiccups (brown outs) a few months ago.
--
"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
(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.
Click to expand...
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?
Click to expand...
Show the SMART data using Everest off the Super WinPE bootable CD.
Click to expand...

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
ys - 1030792418682
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail
s - 73
4 Start_Stop_Count 0x0032 253 253 000 Old_age
ys - 473
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 132 111 000 Old_age
ys - 575525689929
8 Seek_Time_Performance 0x0027 245 245 187 Pre-fail
s - 177648438657628
9 Power_On_Minutes 0x0032 248 248 000 Old_age
ys - 1836h+35m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail
s - 65
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
s - 61
12 Power_Cycle_Count 0x0032 252 252 000 Old_age
ys - 469
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 - 5588
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age
ys - 450483
201 Soft_Read_Error_Rate 0x000a 247 247 000 Old_age
ys - 14280766526842
202 TA_Increase_Count 0x000a 001 001 000 Old_age
ys - 1692217382266
203 Run_Out_Cancel 0x000b 250 250 180 Pre-fail
s - 6820408333690
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age
ys - 267642
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age
ys - 267642
Click to expand...
Click to expand...
On further thought, this block looks bad. Not completely clear what
they actually mean, but you dont normally see those very high numbers
with maxtor drives, do it looks like the drive is pretty sick.
Click to expand...
Main question is why PowerMax doesnt say anything
about it, but the PoweMax has always been rather flakey.
Click to expand...
I'd personally just bin the drive.
Click to expand...

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.

207 Spin_High_Current 0x002a 253 252 000 Old_age
ys - 65
208 Spin_Buzz 0x002a 253 252 000 Old_age
ys - 65
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

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. :)
Click to expand...
Click to expand...
--
"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

(e-mail address removed) wrote
Dropped? How so? I haven't opened the
case for ages. Unless you mean earthquakes. ;)
Click to expand...

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

I've reported you to the RSPCPPSTBTI, you'll be soorree...
Hmm, OK. They are like 3-4 years old. I will try another cable.
Click to expand...
How long do they usually last?
Click to expand...

It isnt a time thing, it basically depends on how its
been handled, particularly when unplugging drives etc.
Assuming I don't open the case that often. Say once a year.
Click to expand...

One good yank can kill a cable.

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

ANTant

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
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 Always - 1211181091848
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail Always - 74
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 474
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 164 111 000 Old_age Always - 343597442371
8 Seek_Time_Performance 0x0027 247 245 187 Pre-fail Always - 161645390127284
9 Power_On_Minutes 0x0032 248 248 000 Old_age Always - 1839h+20m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail Always - 66
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 63
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 470
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 - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 346825
201 Soft_Read_Error_Rate 0x000a 251 246 000 Old_age Always - 6695854328840
202 TA_Increase_Count 0x000a 001 001 000 Old_age Always - 2233383308296
203 Run_Out_Cancel 0x000b 250 247 180 Pre-fail Always - 8632884579336
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 314376
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 314376
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 66
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 66
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

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

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.
Click to expand...
--
"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.
( )
 
F

Frazer Jolly Goodfellow

One good yank can kill a cable.
Click to expand...

'mercans never do things by halves. When you can't get the connector
off, try shootin' it with a Colt 45 - just like a white hat cowboy
opening a locked door.
 
A

ANTant

Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0)
We have the footage of what you do with
it when things go a tad pear shaped...
Click to expand...

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

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

What does that stand for? :p

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

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.
Click to expand...

OK.
--
"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)
Nope, physical shock.
Click to expand...

Hmm, maybe a vacuum cleaner or something. I know the second floor is
on wooden floor. Easy to vibrate if you were to jump hard. heh.

Its unlikely to be that, those dont produce a very slow drive.
Click to expand...

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

Folkert Rienstra

Rod Speed said:
Nope, physical shock.


Its unlikely to be that, those dont produce a very slow drive.
Click to expand...

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

Rod Speed

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
Click to expand...

That one has actually dropped to zero. Presumably it must have been reset by
something.
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age
ys - 346825
201 Soft_Read_Error_Rate 0x000a 251 246 000 Old_age
ys - 6695854328840
202 TA_Increase_Count 0x000a 001 001 000 Old_age
ys - 2233383308296
203 Run_Out_Cancel 0x000b 250 247 180 Pre-fail
s - 8632884579336
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age
ys - 314376
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age
ys - 314376
Click to expand...

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

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

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

Similar Threads

A bootable CD/disk with HDD benchmarks? 3
How long does an ASUS RMA usually take? 4
XP Pro. SP2's explorer.exe crashing a lot and randomly. 19

Top