HDD reads slower and slower...
ANT...@zimage.com
slow like less than 3 MB/sec. Today I noticed it went under 1 MB/sec in some benchmark tests (hdparm
/dev/hda command in Debian/Linux). It is not consistent. It never goes above 5 MB/sec. recently. My other
HDD (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
Does this mean my Maxtor HDD is dying? I didn't see any disk errors. SMART didn't say anything. What do you
guys think?
Thank you in advance. :)
--
Allah's Apostle said, "Once while a prophet amongst the prophets was taking a rest underneath a tree, an ant bit him. He, therefore, ordered that his luggage be taken away from underneath that tree and then ordered that the dwelling place of the ants should be set on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari, Book 54, Number 536
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
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.
Bob Willard
>Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No (K60BMHKC). I noticed the HDD was reading
>slow like less than 3 MB/sec. Today I noticed it went under 1 MB/sec in some benchmark tests (hdparm
>/dev/hda command in Debian/Linux). It is not consistent. It never goes above 5 MB/sec. recently. My other
>HDD (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
>
>Does this mean my Maxtor HDD is dying? I didn't see any disk errors. SMART didn't say anything. What do you
>guys think?
>
>Thank you in advance. :)
>
>
Run HDtach, and look at the graph. If you have large areas of bad sectors,
they should show up as performance dips.
--
Cheers, Bob
Arno Wagner
Arno Wagner
> Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
> (K60BMHKC). I noticed the HDD was reading slow like less than 3
> MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
> tests (hdparm /dev/hda command in Debian/Linux). It is not
> consistent. It never goes above 5 MB/sec. recently. My other HDD
> (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
> Does this mean my Maxtor HDD is dying? I didn't see any disk
> errors. SMART didn't say anything. What do you guys think?
> Thank you in advance. :)
Can you post the output from smartctl -a /dev/hd<whatever> here?
Arno
ANT...@zimage.com
How about the one from Linux's smartctl?
# smartctl -a /dev/hda
smartctl version 5.34 [i686-pc-linux-gnu] Copyright (C) 2002-5 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 40 series (Ultra ATA 66 and Ultra ATA 100)
Device Model: Maxtor 53073U6
Serial Number: K60BMHKC
Firmware Version: DA620CQ0
User Capacity: 30,735,581,184 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 4
ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17
Local Time is: Fri Dec 9 12:09:04 2005 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 22) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 1030792418682
3 Spin_Up_Time 0x0027 199 195 063 Pre-fail Always - 73
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 473
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 0
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 132 111 000 Old_age Always - 575525689929
8 Seek_Time_Performance 0x0027 245 245 187 Pre-fail Always - 177648438657628
9 Power_On_Minutes 0x0032 248 248 000 Old_age Always - 1836h+35m
10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail Always - 65
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 61
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 469
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 5588
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 450483
201 Soft_Read_Error_Rate 0x000a 247 247 000 Old_age Always - 14280766526842
202 TA_Increase_Count 0x000a 001 001 000 Old_age Always - 1692217382266
203 Run_Out_Cancel 0x000b 250 250 180 Pre-fail Always - 6820408333690
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 267642
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 267642
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 65
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 65
209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age Offline - 0
96 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
97 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
98 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
SMART Error Log Version: 1
Warning: ATA error count 2163 inconsistent with error log pointer 5
ATA Error Count: 2163 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 2163 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 20d+11:41:17.536 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
Error 2162 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 20d+11:41:17.488 DEVICE RESET
ca 00 04 41 80 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 6f 00 08 e0 08 20d+11:41:07.968 WRITE DMA
ca 00 02 61 00 08 e0 08 20d+11:41:07.952 WRITE DMA
ca 00 02 4b 00 08 e0 08 20d+11:41:07.952 WRITE DMA
Error 2161 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 2d+14:32:27.616 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
Error 2160 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 2d+14:32:27.568 DEVICE RESET
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
ca 00 02 51 04 00 e0 08 2d+14:32:19.184 WRITE DMA
Error 2159 occurred at disk power-on lifetime: 1721 hours (71 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 1d+12:26:58.176 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 1d+12:26:58.128 DEVICE RESET
ca 00 02 8b 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 6f 00 08 e0 08 1d+12:26:49.696 WRITE DMA
ca 00 02 5d c0 07 e0 08 1d+12:26:49.696 WRITE DMA
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Device does not support Selective Self Tests/Logging
All this was over my head. :)
ANT...@zimage.com
It requires Windows though. I don't have Windows nor want to install it. Thanks though.
ANT...@zimage.com
Arno, here you go. I didn't know this one.
All this information went over my head. :(
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?
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.
Yeah, its a very cryptic report compared with the everest report.
ANT...@zimage.com
> ANT...@zimage.com wrote
> > Rod Speed <rod_...@yahoo.com> wrote
> >> ANT...@zimage.com wrote
> >>> 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.
You can read
http://groups.google.com/group/comp.sys.ibm.pc.hardware.storage/tree/browse_frm/thread/63da7694fdf44462/cd34de9b5ffe3678?rnum=1&hl=en&q=antant%40zimage.com&_done=%2Fgroup%2Fcomp.sys.ibm.pc.hardware.storage%2Fbrowse_frm%2Fthread%2F63da7694fdf44462%2Fcd34de9b5ffe3678%3Ftvc%3D1%26q%3Dantant%40zimage.com%26hl%3Den%26#doc_f04eab657113476b
or http://tinyurl.com/ayja5 (if the above URL is too long). Be sure to use fixed width font.
> The problem clearly isnt due to bad sectors.
> Not at all clear what some of the other values are actually about.
> Try running Maxtor's PowerMax and see what it thinks of the drive.
OK. I am going to use the one from Ultimate Boot CD: http://www.ultimatebootcd.com/ ... I hope it is 4.21.
Folkert Rienstra
> > Rod Speed <rod_...@yahoo.com> wrote
> > > ANT...@zimage.com wrote
>
> > > > 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.
Rod Speed
> "Rod Speed" <rod_...@yahoo.com> wrote in message
> news:3vucthF...@individual.net
>> ANT...@zimage.com wrote
>>> Rod Speed <rod_...@yahoo.com> wrote
>>>> ANT...@zimage.com wrote
>>
>>>>> 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.
>
> What a rotten excuse.
> No problem at all, just use a proper and properly setup newsclient.
Arno Wagner
>> > Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
>> > (K60BMHKC). I noticed the HDD was reading slow like less than 3
>> > MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
>> > tests (hdparm /dev/hda command in Debian/Linux). It is not
>> > consistent. It never goes above 5 MB/sec. recently. My other HDD
>> > (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
>> > Does this mean my Maxtor HDD is dying? I didn't see any disk
>> > errors. SMART didn't say anything. What do you guys think?
>> > Thank you in advance. :)
>> Can you post the output from smartctl -a /dev/hd<whatever> here?
> Arno, here you go. I didn't know this one.
I think the clue is in attribute 7 and 8. It seems seeking correctly
has really become a challenge for this drive. That would explain the
slowdown. It seems when it finds a sector it can read and write
correctly, since it has no reallocated secors at all. The high
read-error rates are likely not accurate head positioning.
It could be the PSU. It could be (unlikely) a servo driver
in the drive going bad. It could be (also unlikely) strong
vibration from something else (other drive?).
My first guess would be a PSU with weak or overloaded 12V line. The
head-servo is droven from that. Have you added any power-hungry
hardware before this problem became obvous, like a modern graphics
card or a fater CPU?
Can you describe you PSU a bit? Modeal, manufacturer, power rating,
current ratings on the individual outputs (5V and 12V are what matters)?
Can you also state the CPU and graphics card you have?
Arno
ANT...@zimage.com
> Previously ANT...@zimage.com wrote:
> >> > Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
> >> > (K60BMHKC). I noticed the HDD was reading slow like less than 3
> >> > MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
> >> > tests (hdparm /dev/hda command in Debian/Linux). It is not
> >> > consistent. It never goes above 5 MB/sec. recently. My other HDD
> >> > (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
> >> > Does this mean my Maxtor HDD is dying? I didn't see any disk
> >> > errors. SMART didn't say anything. What do you guys think?
> >> > Thank you in advance. :)
> >> Can you post the output from smartctl -a /dev/hd<whatever> here?
> > Arno, here you go. I didn't know this one.
> I think the clue is in attribute 7 and 8. It seems seeking correctly
> has really become a challenge for this drive. That would explain the
> slowdown. It seems when it finds a sector it can read and write
> correctly, since it has no reallocated secors at all. The high
> read-error rates are likely not accurate head positioning.
> It could be the PSU. It could be (unlikely) a servo driver
> in the drive going bad. It could be (also unlikely) strong
> vibration from something else (other drive?).
I doubt it. I haven't changed anything recently since summer.
> My first guess would be a PSU with weak or overloaded 12V line. The
> head-servo is droven from that. Have you added any power-hungry
> hardware before this problem became obvous, like a modern graphics
> card or a fater CPU?
Not changed recently. See my secondary machine on
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ... :)
> Can you describe you PSU a bit? Modeal, manufacturer, power rating,
> current ratings on the individual outputs (5V and 12V are what matters)?
> Can you also state the CPU and graphics card you have?
Enlight Power Supply (EN-8341934; Model: HPC-340-101; 340 watts).
ANT...@zimage.com
I can confirm that with KNOPPIX v4.0.2's bootable CD, hdparm -tT showed the same results for
slow disk access speeds.
I also used Ultimate Boot CD v3.3 (Full) from http://www.ultimatebootcd.com/... I ran its System
Speed Test 32 v4.78 (http://user.rol.ru/~dxover/speedsys/) and got:
PIO 4 UDMA 4(4) Cache: 2048 KB
--
Fast Test:
Average/Max Seek Time: 12.41/152.8 ms
Random Seek Time: 14.32 ms
Track-to-track seek: 2.31 ms
Random Access Time: 18.82 ms
Buffered Read Speed: 786227 KB/sec
Linear Verify Speed: 5094 KB/sec
Linear Read Speed: 1294 KB/sc
23.83 HD Speed (don't know how fast this is: MB? KB?). It did say slower than SHD3062(110 MB)
according to the graph.
--
Full Test:
Average/Max Seek Time: 12.67/233.64 ms
Random Seek Time: 10.44 ms
Track-to-track seek: 2.52 ms
Random Access Time: 18.33 ms
Buffered Read Speed: 795757 KB/sec
Linear Verify Speed: <unknown and it was going super slow so I aborted here> ... Going from
track 0 to 57 took like 10 minutes!
Linear Read Speed: 2130 KB/sec (only up to 0 to 800 tracks before I aborted it)
These results look bad, right?
ANT...@zimage.com wrote:
> Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No (K60BMHKC). I noticed the HDD was reading
> slow like less than 3 MB/sec. Today I noticed it went under 1 MB/sec in some benchmark tests (hdparm
> /dev/hda command in Debian/Linux). It is not consistent. It never goes above 5 MB/sec. recently. My other
> HDD (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
> Does this mean my Maxtor HDD is dying? I didn't see any disk errors. SMART didn't say anything. What do you
> guys think?
> Thank you in advance. :)
--
"The general, unable to control his irritation, will launch his men to the assault like swarming ants, with the result that one-third of his men are slain, while the town still remains untaken. Such are the disastrous effects of a siege." --Chapter 3 in Sun Tzu's The Ancient Art of War (Translated by Lionel Giles)
Arno Wagner
> Arno Wagner <m...@privacy.net> wrote:
>> Previously ANT...@zimage.com wrote:
>> >> > Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
>> >> > (K60BMHKC). I noticed the HDD was reading slow like less than 3
>> >> > MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
>> >> > tests (hdparm /dev/hda command in Debian/Linux). It is not
>> >> > consistent. It never goes above 5 MB/sec. recently. My other HDD
>> >> > (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
>> >> > Does this mean my Maxtor HDD is dying? I didn't see any disk
>> >> > errors. SMART didn't say anything. What do you guys think?
>> >> > Thank you in advance. :)
>> >> Can you post the output from smartctl -a /dev/hd<whatever> here?
>> > Arno, here you go. I didn't know this one.
>> I think the clue is in attribute 7 and 8. It seems seeking correctly
>> has really become a challenge for this drive. That would explain the
>> slowdown. It seems when it finds a sector it can read and write
>> correctly, since it has no reallocated secors at all. The high
>> read-error rates are likely not accurate head positioning.
>> It could be the PSU. It could be (unlikely) a servo driver
>> in the drive going bad. It could be (also unlikely) strong
>> vibration from something else (other drive?).
> I doubt it. I haven't changed anything recently since summer.
Can still be the PSU. They degrade over time.
>> My first guess would be a PSU with weak or overloaded 12V line. The
>> head-servo is droven from that. Have you added any power-hungry
>> hardware before this problem became obvous, like a modern graphics
>> card or a fater CPU?
> Not changed recently. See my secondary machine on
> http://alpha.zimage.com/~ant/antfarm/about/computers.txt ... :)
You have a second machine? Then put the HDD in there and run
the hdparm benchmarks there!
Arno
Rod Speed
Slow, certainly. Much worse than the 250G Samsung in the PVR
with System Speed Test 32 v4.78 from the Ultimate Boot CD.
> ANT...@zimage.com wrote:
>> 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. :)
>
Rod Speed
Just ran it on a rather dinsoaury old Compaq with an 8G seagate
and its much faster than yours. You've clearly got a real problem.
See what PowerMax has to say about the drive.
ANT...@zimage.com
> >>> 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?
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:
Yeah, but it shows more datas than Everest. I just don't have
Windows installed on this box. :( So far, two people said HDD
seems to be having problems reading even though I have NO idea
what all that information meant. :)
--
"The general, unable to control his irritation, will launch his men to the assault like swarming ants, with the result that one-third of his men are slain, while the town still remains untaken. Such are the disastrous effects of a siege." --Chapter 3 in Sun Tzu's The Ancient Art of War (Translated by Lionel Giles)
ANT...@zimage.com
> >> >> > (K60BMHKC). I noticed the HDD was reading slow like less than 3
> >> >> > MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
> >> >> > tests (hdparm /dev/hda command in Debian/Linux). It is not
> >> >> > consistent. It never goes above 5 MB/sec. recently. My other HDD
> >> >> > (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
> >> >> > Does this mean my Maxtor HDD is dying? I didn't see any disk
> >> >> > errors. SMART didn't say anything. What do you guys think?
> >> >> > Thank you in advance. :)
> >> >> Can you post the output from smartctl -a /dev/hd<whatever> here?
> >> > Arno, here you go. I didn't know this one.
> >> I think the clue is in attribute 7 and 8. It seems seeking correctly
> >> has really become a challenge for this drive. That would explain the
> >> slowdown. It seems when it finds a sector it can read and write
> >> correctly, since it has no reallocated secors at all. The high
> >> read-error rates are likely not accurate head positioning.
> >> It could be the PSU. It could be (unlikely) a servo driver
> >> in the drive going bad. It could be (also unlikely) strong
> >> vibration from something else (other drive?).
> > I doubt it. I haven't changed anything recently since summer.
> Can still be the PSU. They degrade over time.
If it was PSU, wouldn't my other HDD be affected too?
> >> My first guess would be a PSU with weak or overloaded 12V line. The
> >> head-servo is droven from that. Have you added any power-hungry
> >> hardware before this problem became obvous, like a modern graphics
> >> card or a fater CPU?
> > Not changed recently. See my secondary machine on
> > http://alpha.zimage.com/~ant/antfarm/about/computers.txt ... :)
> You have a second machine? Then put the HDD in there and run
> the hdparm benchmarks there!
Nope.
> >> Can you describe you PSU a bit? Modeal, manufacturer, power rating,
> >> current ratings on the individual outputs (5V and 12V are what matters)?
> >> Can you also state the CPU and graphics card you have?
> > Enlight Power Supply (EN-8341934; Model: HPC-340-101; 340 watts).
--
"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)
ANT...@zimage.com
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)
Arno Wagner
>> >> >> > Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
>> >> >> > (K60BMHKC). I noticed the HDD was reading slow like less than 3
>> >> >> > MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
>> >> >> > tests (hdparm /dev/hda command in Debian/Linux). It is not
>> >> >> > consistent. It never goes above 5 MB/sec. recently. My other HDD
>> >> >> > (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
>> >> >> > Does this mean my Maxtor HDD is dying? I didn't see any disk
>> >> >> > errors. SMART didn't say anything. What do you guys think?
>> >> >> > Thank you in advance. :)
>> >> >> Can you post the output from smartctl -a /dev/hd<whatever> here?
>> >> > Arno, here you go. I didn't know this one.
>> >> I think the clue is in attribute 7 and 8. It seems seeking correctly
>> >> has really become a challenge for this drive. That would explain the
>> >> slowdown. It seems when it finds a sector it can read and write
>> >> correctly, since it has no reallocated secors at all. The high
>> >> read-error rates are likely not accurate head positioning.
>> >> It could be the PSU. It could be (unlikely) a servo driver
>> >> in the drive going bad. It could be (also unlikely) strong
>> >> vibration from something else (other drive?).
>> > I doubt it. I haven't changed anything recently since summer.
>> Can still be the PSU. They degrade over time.
> If it was PSU, wouldn't my other HDD be affected too?
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
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?
>> 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.
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.
ANT...@zimage.com
Yeah.
> 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. :)
> 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.
> 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.
However, I haven't opened the case since summer so it is not like I
touched it. :) Linux's uptime was like 100+ days!
--
"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)
Folkert Rienstra
> Previously ANT...@zimage.com wrote:
>>>>>>>> Hello! I have an old Maxtor 53073U6 (Firmware DA620CQ0) Serial No
>>>>>>>> (K60BMHKC). I noticed the HDD was reading slow like less than 3
>>>>>>>> MB/sec. Today I noticed it went under 1 MB/sec in some benchmark
>>>>>>>> tests (hdparm /dev/hda command in Debian/Linux). It is not
>>>>>>>> consistent. It never goes above 5 MB/sec. recently. My other HDD
>>>>>>>> (even older; Quantum Fireball 6.4 GB) got about 12 MB/sec.
>>>>>>>> Does this mean my Maxtor HDD is dying? I didn't see any disk
>>>>>>>> errors. SMART didn't say anything. What do you guys think?
>>>>>>>> Thank you in advance. :)
>
>>>>>>> Can you post the output from smartctl -a /dev/hd<whatever> here?
>
>>>>>> Arno, here you go. I didn't know this one.
>
>>>>> I think the clue is in attribute 7 and 8. It seems seeking correctly
>>>>> has really become a challenge for this drive. That would explain the
>>>>> slowdown. It seems when it finds a sector it can read and write
>>>>> correctly, since it has no reallocated secors at all. The high
>>>>> read-error rates are likely not accurate head positioning.
>
>>>>> It could be the PSU. It could be (unlikely) a servo driver
>>>>> in the drive going bad. It could be (also unlikely) strong
>>>>> vibration from something else (other drive?).
>
>>>> I doubt it. I haven't changed anything recently since summer.
>
>>> Can still be the PSU. They degrade over time.
>
>> If it was PSU, wouldn't my other HDD be affected too?
>
> It might not be as sensitive to this problem.
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.
Yeah, obviously can't be the supply regulators on the board itself either.
>
> This type of problem is hard to debug.
You mean troubleshoot don't you.
> The best choice usually is changin components until the problem goes away.
Which is called trouble shooting if you put some common sense into that.
>
> Arno
Folkert Rienstra
> ANT...@zimage.com wrote
>
>>>>>> 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?
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.
You still get UDMA 33.
>
> 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.
>
>
[snip]
Rod Speed
> Yeah.
>> Try Hitachi's DFT.
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.
>> 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.
> 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.
Rod Speed
<ANT...@zimage.com> wrote in message
news:mPqdnaX-oq-...@mminternet.net...
> 3 Spin_Up_Time 0x0027 199 195 063 Pre-fail
> 4 Start_Stop_Count 0x0032 253 253 000 Old_age
> 5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail
> 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail
> 7 Seek_Error_Rate 0x000a 132 111 000 Old_age
> 8 Seek_Time_Performance 0x0027 245 245 187 Pre-fail
> 9 Power_On_Minutes 0x0032 248 248 000 Old_age
> 10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail
> 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
> 12 Power_Cycle_Count 0x0032 252 252 000 Old_age
> 196 Reallocated_Event_Count 0x0008 253 253 000 Old_age
> 197 Current_Pending_Sector 0x0008 253 253 000 Old_age
> 198 Offline_Uncorrectable 0x0008 253 253 000 Old_age
> 199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
> 200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age
> 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
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
ANT...@zimage.com
> > Yeah.
> >> Try Hitachi's DFT.
Dropped? How so? I haven't opened the case for ages. Unless you mean earthquakes. ;)
> >> 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? Assuming I don't open the case that often.
Say once a year.
ANT...@zimage.com
> >>>>>> 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?
> That can happen with drives that suffered from severe shock.
> I have one.
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)
ANT...@zimage.com
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)
Rod Speed
> Shock from electrcity?
Nope, physical shock.
> Isn't that what APC UPS supposed to stop? I know there
> was recent power hiccups (brown outs) a few months ago.
Its unlikely to be that, those dont produce a very slow drive.
Rod Speed
>>> Yeah.
>>>> Try Hitachi's DFT.
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...
>>>> 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.
> Assuming I don't open the case that often. Say once a year.
One good yank can kill a cable.
Its more likely the drive is just dying tho given the SMART data.
ANT...@zimage.com
> > >> > (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
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
> > 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.
Frazer Jolly Goodfellow
@individual.net:
> One good yank can kill a cable.
'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.
ANT...@zimage.com
> >>> Yeah.
> >>>> Try Hitachi's DFT.
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? :P
> >>>> 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.
--
"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)
Folkert Rienstra
>> 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
> > 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
>
> On further thought,
Nah, you just picked that up from my post.
> this block looks bad.
Yup, you managed to mangle that quoting very comprehensively indeed.
There's even partial words missing.
> Not completely clear what they actually mean,
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
ANT...@zimage.com
> > Shock from electrcity?
> Nope, physical shock.
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.
> > Isn't that what APC UPS supposed to stop? I know there
> > was recent power hiccups (brown outs) a few months ago.
> Its unlikely to be that, those dont produce a very slow drive.
OK.
Rod Speed
<ANT...@zimage.com> wrote in message
news:qomdnbBEqqKrlwPe...@mminternet.net...
> 3 Spin_Up_Time 0x0027 199 195 063 Pre-fail
> 4 Start_Stop_Count 0x0032 253 253 000 Old_age
> 5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail
> 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail
> 7 Seek_Error_Rate 0x000a 164 111 000 Old_age
> 8 Seek_Time_Performance 0x0027 247 245 187 Pre-fail
> 9 Power_On_Minutes 0x0032 248 248 000 Old_age
> 10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail
> 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
> 12 Power_Cycle_Count 0x0032 252 252 000 Old_age
> 196 Reallocated_Event_Count 0x0008 253 253 000 Old_age
> 197 Current_Pending_Sector 0x0008 253 253 000 Old_age
> 198 Offline_Uncorrectable 0x0008 253 253 000 Old_age
> 199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
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
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
ANT...@zimage.com
Probably because I turned the computer off completely for a few minutes?
> > 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
> 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.os.linux.hardware/browse_frm/thread/f7fd902226db519d/04a546a64031afe1?lnk=st&q=Shock_Count_Write_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.
Rod Speed
<ANT...@zimage.com> wrote in message
news:buSdnXj88cJ...@mminternet.net...
I wouldnt have expected that one to reset on power off.
>> > 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
>
>> 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.os.linux.hardware/browse_frm/thread/f7fd902226db519d/04a546a64031afe1?lnk=st&q=Shock_Count_Write_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.
Folkert Rienstra
It does to mine. Nothing wrong with it except very very slow.
Nothing wrong that is, until you run DFT: Excessive Shock.
Folkert Rienstra
> <ANT...@zimage.com> wrote in message news:buSdnXj88cJ...@mminternet.net...
> > > > > > > > > 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
[snip]
> > > > 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.
UDMA_CRC errors aren't necessarily the drive's fault.
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
> Rod Speed <rod_...@yahoo.com> wrote
>> ANT...@zimage.com wrote
>>>>> Weird, huh?
>>> Shock from electrcity?
>> Nope, physical shock.
I meant that power brownouts dont produce a very slow drive.
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
>>>>> 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.
> 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.
>> 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.
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
Folkert Rienstra
But their attribute numbers do.
>
> The others in the block I specified are obvious enough.
>
> > > 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.
>
> 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
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.
--
--John
to email, dial "usenet" and validate
(was jclarke at eye bee em dot net)
Rod Speed
>>> http://www.t13.org/docs2005/e05173r0-ACS-SMARTAttributes_List.pdf
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.
>> The others in the block I specified are obvious enough.
>>>> 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.
>> Not exactly rocket science given the two Shock* attributes.
> 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.
>> 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.
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).
>> 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.
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.
ANT...@zimage.com
> 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.
Peter
(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
> > > > > > > > 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
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.
>
> > > The others in the block I specified are obvious enough.
>
> > > > > 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.
>
> > > Not exactly rocket science given the two Shock* attributes.
>
> > 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.
Yeah right.
>
> > > 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.
>
> 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).
>
> > > 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.
>
> 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
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
"Folkert Rienstra" <see_re...@myweb.nl> wrote in message
news:43a0741d$1$80320$892e...@authen.yellow.readfreenews.net...
>> Cant see why
> I can.
No you cant.
>> 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.
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.
>> 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.
>>>> The others in the block I specified are obvious enough.
>>>>>> 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.
>>>> Not exactly rocket science given the two Shock* attributes.
>>> 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.
> Yeah right.
Fraid so, yours was two days later.
ANT...@zimage.com
$ dd_rescue -V
dd_rescue Version 1.11, garl...@suse.de, 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.
ANT...@zimage.com wrote:
> 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