My computer has 1 main (primary) IDE drive of 250GB. Recently I have added anothe 250GB drive onto the same cable as secondary. At a set time during the night changed files from the primary drive are backed up onto the secondary drive using Find/CPIO. When this backup happens I get many of the following errors in my logs:
Mar 3 07:35:16 dataman1 kernel: hda: dma_intr: error=0x40 { UncorrectableError}, LBAsect=440937085, high=26, low=4729469, sector=232525840 Mar 3 07:35:16 dataman1 kernel: end_request: I/O error, dev 03:02 (hda), sector 232525840 Mar 3 07:35:16 dataman1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
The values vary but the messages are basically the same. After the backup at 1:00 AM there are no more messages until Cron Daily is run at 7:30 AM when they repeat.
However after that, whatever I do on the computer, there are no more DMA error messages until the next backup. This did not happen at all until the new drive was installed and the backup sessions started.
Both drives are set for UDMA5 (it says in the BIOS).
I don't see why these errors should occur for hda as it is only being read during the backup whereas hdb is being written to but then I don't know anything about DMA.
I tried changing UDMA5 to UDMA3 on hda to no effect. It is now back to UDMA5.
I would dearly like some suggestions from the experts.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
The two things I would do here are-
Install the smartmontools package to get smartctl. Read the man file and use this tool to run a extended offline test of hda....Offline tests don't actually take the drive offline (they can just make it really slow) so you can do them when it is mounted...I strongly advise you read the man file first...but essentially the syntax is as follows.
smartctl -t long /dev/hda
Which will start the test and give an approximation of when it will finish...once that point has passed.
smartctl -a /dev/hda
to get a full drive status and test results...if you can't make sense of them then post the results here.
replace the IDE cable, be sure to get one of the ultra DMA capable 80 conductor types as the old style 40 conductor type would cause similar errors to what you are seeing here....this won't effect the results of the test above because the smart test is performed by the drive firmware not the PC.
IDE cables can be amazingly fickle....I have had physically perfect looking cables cause me no end of random disk problems.
The only other things I can think of you checking is that your PSU is up to the job of running both drives when they are busy.
On 2006.03.03 18:39, Wayne Stallwood wrote:
The two things I would do here are-
Install the smartmontools package to get smartctl. Read the man file and use this tool to run a extended offline test of hda....Offline tests don't actually take the drive offline (they can just make it really slow) so you can do them when it is mounted...I strongly advise you read the man file first...but essentially the syntax is as follows.
smartctl -t long /dev/hda
Which will start the test and give an approximation of when it will finish...once that point has passed.
smartctl -a /dev/hda
to get a full drive status and test results...if you can't make sense of them then post the results here.
Results below.
replace the IDE cable, be sure to get one of the ultra DMA capable 80 conductor types as the old style 40 conductor type would cause similar errors to what you are seeing here....this won't effect the results of the test above because the smart test is performed by the drive firmware not the PC.
IDE cables can be amazingly fickle....I have had physically perfect looking cables cause me no end of random disk problems.
I'll have to try that when I can get a new cable.
The only other things I can think of you checking is that your PSU is up to the job of running both drives when they are busy.
PSU has had more than two drives before without problems. ======================================================================= 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 MaXLine Plus II Device Model: Maxtor 7Y250P0 Serial Number: Y62BLZAE Firmware Version: YAR41BW0 User Capacity: 251,000,193,024 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 Local Time is: Fri Mar 3 22:04:31 2006 GMT 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: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 116) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 363) seconds. Offline data collection capabilities: (0x5b) 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. 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: ( 106) 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 3 Spin_Up_Time 0x0027 179 179 063 Pre-fail Always - 22479 4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 124 5 Reallocated_Sector_Ct 0x0033 233 232 063 Pre-fail Always - 208 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0 7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0 8 Seek_Time_Performance 0x0027 251 249 187 Pre-fail Always - 43428 9 Power_On_Minutes 0x0032 215 215 000 Old_age Always - 173h+54m 10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail Always - 0 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 253 253 000 Old_age Always - 117 192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always - 0 194 Temperature_Celsius 0x0032 253 253 000 Old_age Always - 51 195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 7003 196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0 197 Current_Pending_Sector 0x0008 233 233 000 Old_age Offline - 203 198 Offline_Uncorrectable 0x0008 252 252 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x0008 190 173 000 Old_age Offline - 61 200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 1 202 TA_Increase_Count 0x000a 253 252 000 Old_age Always - 0 203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 0 204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 0 205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0 207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 0 208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 0 209 Offline_Seek_Performnce 0x0024 188 188 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 1643 inconsistent with error log pointer 5
ATA Error Count: 1643 (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 1643 occurred at disk power-on lifetime: 12437 hours (518 days + 5 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 -- -- -- -- -- -- -- 40 51 08 ed 19 5c e0 Error: UNC 8 sectors at LBA = 0x005c19ed = 6035949
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 ed 19 5c e0 08 6d+02:24:52.736 READ DMA EXT 25 00 08 c5 1d 58 e0 08 6d+02:24:52.736 READ DMA EXT 25 00 08 bd 1d 58 e0 08 6d+02:24:52.720 READ DMA EXT 25 00 08 b5 1d 58 e0 08 6d+02:24:52.720 READ DMA EXT 25 00 08 ad 1d 58 e0 08 6d+02:24:52.720 READ DMA EXT
Error 1642 occurred at disk power-on lifetime: 12437 hours (518 days + 5 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 -- -- -- -- -- -- -- 40 51 08 ed 19 5c e0 Error: UNC 8 sectors at LBA = 0x005c19ed = 6035949
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 ed 19 5c e0 08 6d+02:24:51.712 READ DMA EXT 25 00 08 95 1d 58 e0 08 6d+02:24:51.696 READ DMA EXT 25 00 08 8d 1d 58 e0 08 6d+02:24:51.696 READ DMA EXT 25 00 08 85 1d 58 e0 08 6d+02:24:51.696 READ DMA EXT 25 00 08 7d 1d 58 e0 08 6d+02:24:51.696 READ DMA EXT
Error 1641 occurred at disk power-on lifetime: 12437 hours (518 days + 5 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 -- -- -- -- -- -- -- 40 51 08 ed 19 5c e0 Error: UNC 8 sectors at LBA = 0x005c19ed = 6035949
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 ed 19 5c e0 08 6d+02:24:50.688 READ DMA EXT 25 00 08 75 1d 58 e0 08 6d+02:24:50.688 READ DMA EXT 35 00 08 17 1a 26 e0 08 6d+02:24:50.688 WRITE DMA EXT 35 00 10 07 1a 26 e0 08 6d+02:24:50.688 WRITE DMA EXT 35 00 08 b7 3b 2e e0 08 6d+02:24:50.688 WRITE DMA EXT
Error 1640 occurred at disk power-on lifetime: 12437 hours (518 days + 5 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 -- -- -- -- -- -- -- 40 51 08 ed 19 5c e0 Error: UNC 8 sectors at LBA = 0x005c19ed = 6035949
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 ed 19 5c e0 08 6d+02:24:49.648 READ DMA EXT 25 00 08 55 1d 58 e0 08 6d+02:24:49.648 READ DMA EXT 25 00 08 4d 1d 58 e0 08 6d+02:24:49.648 READ DMA EXT 25 00 08 45 1d 58 e0 08 6d+02:24:49.648 READ DMA EXT 35 00 08 a7 19 26 e0 08 6d+02:24:49.648 WRITE DMA EXT
Error 1639 occurred at disk power-on lifetime: 12437 hours (518 days + 5 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 -- -- -- -- -- -- -- 40 51 08 ed 19 5c e0 Error: UNC 8 sectors at LBA = 0x005c19ed = 6035949
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 ed 19 5c e0 08 6d+02:24:48.608 READ DMA EXT 25 00 08 2d 1d 58 e0 08 6d+02:24:48.608 READ DMA EXT 25 00 08 25 1d 58 e0 08 6d+02:24:48.592 READ DMA EXT 25 00 08 1d 1d 58 e0 08 6d+02:24:48.592 READ DMA EXT 25 00 08 15 1d 58 e0 08 6d+02:24:48.592 READ DMA EXT
SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 40% 12449 49372246
SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
On Fri, 2006-03-03 at 22:11 +0000, Barry Samuels wrote:
to get a full drive status and test results...if you can't make sense of them then post the results here.
Results below.
Looks to be shot I am afraid, however your drive has warranty until this time next year so I'd copy your system over to another drive and get that one sent away on a RMA request.
You can do that online here https://www4.maxtor.com/en/support/service/rma/create/
You may have to go through the braindead Maxtor diagnostic tools thing, but I think that can be done from a boot disk....they used to have a way of posting the SMART errors which bypassed having to run the test....It may also be that the Maxtor utility can do a hard format and fix the problems...but in this case I doubt it.
The logged errors are showing as external interface errors, but the internal self test failed at block 49372246. Usually this means that the drive has so many bad sectors that it cannot remap any more..currently your drive thinks it has remapped 208 sectors.
You'd probably find that if you ran badblocks on it (be very very careful with badblocks some of the options will overwrite all the data in a particularly unrecoverable way) you would find some bad sectors scattered all over it....Check your backups and replace it ASAP is my advice.
I am also pretty sure the "current pending sector offline" being anything other than 0 is a bad thing.
One more thing..for a 7200 RPM drive I would say that 51 degrees is a little on the warm side...Even my music server which is in a really poorly vented NAS box case with no fans other than a sub miniature case fan has a 7200 RPM drive that has never been over about 42C
Whether this has caused the failure (through bad case ventilation) or is a symptom of the failure I am not sure...I would check the temp of the other drive though. If that is equally high then I'd consider a case fan. On a standard ATX case there is sometimes a place for a fan in front of the drive bays..put a fan to suck air in on this position...if there isn't a space there then put in a rear fan (which should be set to blow air out).
Wayne
Many thanks for your help it is much appreciated.
On 2006.03.03 23:06, Wayne Stallwood wrote:
On Fri, 2006-03-03 at 22:11 +0000, Barry Samuels wrote:
to get a full drive status and test results...if you can't make sense of them then post the results here.
Results below.
Looks to be shot I am afraid, however your drive has warranty until this time next year so I'd copy your system over to another drive and get that one sent away on a RMA request.
The logged errors are showing as external interface errors, but the internal self test failed at block 49372246. Usually this means that the drive has so many bad sectors that it cannot remap any more..currently your drive thinks it has remapped 208 sectors.
You'd probably find that if you ran badblocks on it (be very very careful with badblocks some of the options will overwrite all the data in a particularly unrecoverable way) you would find some bad sectors scattered all over it....Check your backups and replace it ASAP is my advice.
Badblocks had got up to 1700+ bad blocks when I finally stopped it. This, incidentally, appears to affect only one partition.
One more thing..for a 7200 RPM drive I would say that 51 degrees is a little on the warm side...Even my music server which is in a really poorly vented NAS box case with no fans other than a sub miniature case fan has a 7200 RPM drive that has never been over about 42C
Whether this has caused the failure (through bad case ventilation) or is a symptom of the failure I am not sure...I would check the temp of the other drive though. If that is equally high then I'd consider a case fan. On a standard ATX case there is sometimes a place for a fan in front of the drive bays..put a fan to suck air in on this position...if there isn't a space there then put in a rear fan (which should be set to blow air out).
One thing that I'm really good at is forgetting - in fact I would say I'm a 'Master' on that subject.
I have only just realised that this problem coincides with the fitting of a hard drive silencing kit. Removing that from the drive reduces the temperature to 21 degrees. The case cooling is fine. It has one fan at the front and one at the back and both are 120mm. CPU temperatures are also fine.
The silencing kit and the drive came from the same retailer so I shall tackle them about it. It certainly appears that the silencing kit has caused the overheating and damage.
I already have a duplicate drive in the case which is mirroring the working drive and I booted from the mirror drive yesterday to test it and it all works. I shall be swapping that as the working drive and the faulty one can go back with the silencing kit.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On Fri, 2006-03-03 at 18:39 +0000, Wayne Stallwood wrote:
Install the smartmontools package to get smartctl. Read the man file and use this tool to run a extended offline test of hda....Offline tests don't actually take the drive offline (they can just make it really slow) so you can do them when it is mounted...I strongly advise you read the man file first...but essentially the syntax is as follows.
Actually drifting off topic slightly..But something I'd recommend to anybody.
Set up the smartmontools in daemon mode...there are a couple of good howto's on the web but it's pretty simple to get them to run scheduled tests and mail root if any tests failed..I can't do it on my main machine because my SATA disks (or controller I'm not sure) aren't supported by the Smartmontools package.
Disks often fail over a period of time...if these tools can catch an error before total failure then it could save you a bit of a headache.
A lot of BIOS's support SMART but only in a very simplistic way and only during boot (also it is often disabled by default) they don't run the tests, but just report if any of the values go over threshold....What the tools do is far more thorough.
-
Barry Samuels -
Barry Samuels -
Wayne Stallwood