From: Tim C. <cyg...@ho...> - 2002-12-11 16:17:20
|
Hmm, first off I made a small mistake: this is not a 7200 RPM 100gb maxtor drive; it's a 13 or 20gb drive, not 7200RPM. But playing around with smartmontools makes it look like there isn't really support for this drive: smartmon doesn't seem to understand the info the drive returns. Is this a known issue with maxtor drives? tim >From: Bruce Allen <ba...@gr...> >To: Tim Carr <cyg...@ho...> >CC: sma...@li... >Subject: Re: [Smartmontools-support]Maxtor 100gb 7200rpm 2mb cache, odd >output >Date: Mon, 11 Nov 2002 07:19:48 -0600 (CST) > >Hi Tim, > >I just noticed a couple of other things about your disk: > > > SMART Error Log Version: 1 > > ATA Error Count: 1947 (device log contains only the most recent five >errors) > >This is a VERY high number of ATA errors. The most recent >of these errors occured at time: > > > Error 1 occurred at disk power-on lifetime: 2156 hours > >Is this disk only about 3 or 4 months old? If so, you should use the "-m" >option to smartctl; the power on lifetime is stored in minutes not hours. > > > SMART Self-test log, version number 1 > > No self-tests have been logged > >I would definitely run some disk self-tests. Use the -X and -S options to >smartctl. After the test is over, you can view the results with -L (or >with -a). > >Cheers, > Bruce _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail |
From: Tim C. <cyg...@ho...> - 2002-12-12 16:16:07
|
Many thanks for all the help! I set an extended self-test going on the maxtor drive, only to find that it doesn't support self-test logging :( So i'm not sure how to get the results of any tests to send to you; here is the output of "smartctl -a /dev/hda" right after the extended self-test finished: smartctl version 5.0-32 Copyright (C) 2002 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: Maxtor 91361U3 Serial Number: G3HVGG7C Firmware Version: FA520860 ATA Version is: 4 ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17 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: Off-line data collection status: (0x00) Offline data collection activity was never started. 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 off-line data collection: ( 0) seconds. Offline data collection capabilities: (0x1b) SMART execute Offline immediate. Automatic timer ON/OFF support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x00) Error logging NOT supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 13) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000a 253 252 000 Old_age - 341673 3 Spin_Up_Time 0x0027 234 233 063 Pre-fail - 4407 4 Start_Stop_Count 0x0032 253 253 000 Old_age - 705 5 Reallocated_Sector_Ct 0x0033 248 248 063 Pre-fail - 13 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail - 0 7 Seek_Error_Rate 0x000a 253 246 000 Old_age - 93843 8 Seek_Time_Performance 0x0027 248 240 187 Pre-fail - 1505273 9 Power_On_Hours 0x0032 247 247 000 Old_age - 138017 10 Spin_Retry_Count 0x002b 253 252 223 Pre-fail - 93 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail - 73 12 Power_Cycle_Count 0x0032 252 252 000 Old_age - 753 196 Reallocated_Event_Count 0x0008 253 253 000 Old_age - 0 197 Current_Pending_Sector 0x0008 253 252 000 Old_age - 0 198 Offline_Uncorrectable 0x0008 253 253 000 Old_age - 0 199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age - 5920 200 Unknown_Attribute 0x000a 253 252 000 Old_age - 254394 201 Unknown_Attribute 0x000a 253 113 000 Old_age - 341671 202 Unknown_Attribute 0x000a 253 252 000 Old_age - 341665 203 Unknown_Attribute 0x000b 253 252 180 Pre-fail - 341665 204 Unknown_Attribute 0x000a 253 252 000 Old_age - 341665 205 Unknown_Attribute 0x000a 253 241 000 Old_age - 341665 207 Unknown_Attribute 0x002a 253 252 000 Old_age - 93 208 Unknown_Attribute 0x002a 253 252 000 Old_age - 93 209 Unknown_Attribute 0x0024 253 253 000 Old_age - 0 96 Unknown_Attribute 0x0004 253 253 000 Old_age - 0 97 Unknown_Attribute 0x0004 253 253 000 Old_age - 0 98 Unknown_Attribute 0x0004 253 253 000 Old_age - 0 99 Unknown_Attribute 0x0004 253 253 000 Old_age - 0 100 Unknown_Attribute 0x0004 253 253 000 Old_age - 0 101 Unknown_Attribute 0x0004 253 253 000 Old_age - 0 Warning: device does not support Error Logging SMART Error Log Version: 1 ATA Error Count: 1971 (device log contains only the most recent five errors) DCR = Device Control Register FR = Features Register SC = Sector Count Register SN = Sector Number Register CL = Cylinder Low Register CH = Cylinder High Register D/H = Device/Head Register CR = Content written to Command Register ER = Error register STA = Status register Timestamp is seconds since the previous disk power-on. Note: timestamp "wraps" after 2^32 msec = 49.710 days. Error 1 occurred at disk power-on lifetime: 2156 hours When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER:04 SC:00 SN:01 CL:00 CH:00 D/H:a0 ST:51 Sequence of commands leading to the command that caused the error were: DCR FR SC SN CL CH D/H CR Timestamp 08 ff 00 01 00 00 a0 a1 37.744 08 ff 01 01 00 00 a0 20 37.744 08 d2 00 01 4f c2 a0 b0 37.696 08 d8 3f 00 4f c2 a0 b0 37.648 08 ff 3f 00 00 00 af 91 37.648 Error 2 occurred at disk power-on lifetime: 2156 hours When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER:04 SC:00 SN:01 CL:00 CH:00 D/H:a0 ST:51 Sequence of commands leading to the command that caused the error were: DCR FR SC SN CL CH D/H CR Timestamp 08 ff 00 01 00 00 a0 a1 37.744 08 ff 01 01 00 00 a0 20 37.744 08 d2 00 01 4f c2 a0 b0 37.696 08 d8 3f 00 4f c2 a0 b0 37.648 08 ff 3f 00 00 00 af 91 37.648 Error 3 occurred at disk power-on lifetime: 2156 hours When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER:04 SC:00 SN:01 CL:00 CH:00 D/H:a0 ST:51 Sequence of commands leading to the command that caused the error were: DCR FR SC SN CL CH D/H CR Timestamp 08 ff 00 01 00 00 a0 a1 1916.912 08 ff 01 01 00 00 a0 20 1916.896 08 d2 00 01 4f c2 a0 b0 1916.864 08 d8 3f 00 4f c2 a0 b0 1916.816 08 ff 3f 00 00 00 af 91 1916.816 Error 4 occurred at disk power-on lifetime: 2156 hours When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER:04 SC:00 SN:01 CL:00 CH:00 D/H:a0 ST:51 Sequence of commands leading to the command that caused the error were: DCR FR SC SN CL CH D/H CR Timestamp 08 ff 00 01 00 00 a0 a1 1392.464 08 ff 01 01 00 00 a0 20 1392.464 08 d2 00 01 4f c2 a0 b0 1392.416 08 d8 3f 00 4f c2 a0 b0 1392.352 08 ff 3f 00 00 00 af 91 1392.352 Error 5 occurred at disk power-on lifetime: 2156 hours When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER:04 SC:00 SN:01 CL:00 CH:00 D/H:a0 ST:51 Sequence of commands leading to the command that caused the error were: DCR FR SC SN CL CH D/H CR Timestamp 08 ff 00 01 00 00 a0 a1 1109.104 08 ff 01 01 00 00 a0 20 1109.088 08 d2 00 01 4f c2 a0 b0 1109.056 08 d8 3f 00 4f c2 a0 b0 1109.008 08 ff 3f 00 00 00 af 91 1109.008 Warning: device does not support Self Test Logging Again, thanks for all your continued help :) tim >From: Bruce Allen <ba...@gr...> >To: Tim Carr <cyg...@ho...> >CC: sma...@li... >Subject: Re: [Smartmontools-support]Maxtor 100gb 7200rpm 2mb cache, odd >output >Date: Wed, 11 Dec 2002 12:31:52 -0600 (CST) > >Hi Tim, > > > Hmm, first off I made a small mistake: this is not a 7200 RPM 100gb > > maxtor drive; it's a 13 or 20gb drive, not 7200RPM. > >I just looked at the maxtor data sheet for the drive family. It's a 5400 >RPM 20 GB drive, I think. > > > But playing around with smartmontools makes it look like there isn't > > really support for this drive: smartmon doesn't seem to understand the > > info the drive returns. Is this a known issue with maxtor drives? > >Not at all. Maxtor was pretty involved in writing the ATA SMART specs and >these drives definitely implement it. And when I look at the output that >you sent from smartctl a month ago, it seemed pretty sensible. > >On the other hand, if the disk is damaged then some of the values returned >could be garbage. But on the whole it does appear to support smart and I >think smartmontools is reporting correctly what's on the disk. > >Did you try running some self-tests as I had suggested in November? >If so, send the output of smartctl -a along, please. > >Cheers, > Bruce > > > > >From: Bruce Allen <ba...@gr...> > > >To: Tim Carr <cyg...@ho...> > > >CC: sma...@li... > > >Subject: Re: [Smartmontools-support]Maxtor 100gb 7200rpm 2mb cache, odd > > >output > > >Date: Mon, 11 Nov 2002 07:19:48 -0600 (CST) > > > > > >Hi Tim, > > > > > >I just noticed a couple of other things about your disk: > > > > > > > SMART Error Log Version: 1 > > > > ATA Error Count: 1947 (device log contains only the most recent five > > >errors) > > > > > >This is a VERY high number of ATA errors. The most recent > > >of these errors occured at time: > > > > > > > Error 1 occurred at disk power-on lifetime: 2156 hours > > > > > >Is this disk only about 3 or 4 months old? If so, you should use the >"-m" > > >option to smartctl; the power on lifetime is stored in minutes not >hours. > > > > > > > SMART Self-test log, version number 1 > > > > No self-tests have been logged > > > > > >I would definitely run some disk self-tests. Use the -X and -S options >to > > >smartctl. After the test is over, you can view the results with -L (or > > >with -a). > > > > > >Cheers, > > > Bruce > > > > > > _________________________________________________________________ > > Tired of spam? Get advanced junk mail protection with MSN 8. > > http://join.msn.com/?page=features/junkmail > > > > _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail |
From: Bruce A. <ba...@gr...> - 2002-12-12 16:49:41
|
Hi Tim, > Many thanks for all the help! You're welcome. > I set an extended self-test going on the maxtor drive, only to find > that it doesn't support self-test logging :( So i'm not sure how to > get the results of any tests to send to you; here is the output of > "smartctl -a /dev/hda" right after the extended self-test finished: You can see the result of the self-test here: > Self-test execution status: ( 0) The previous self-test routine > completed > without error or no self-test has > ever > been run. So no sign of trouble. [I hadn't noticed that you don't have self-test logging -- sorry!] You might also try an Offline Immediate test (-O option). You should be able to watch its progress by using the -v option to track the fraction of time remaining. Cheers,, Bruce |
From: Bruce A. <ba...@gr...> - 2002-12-11 18:32:07
|
Hi Tim, > Hmm, first off I made a small mistake: this is not a 7200 RPM 100gb > maxtor drive; it's a 13 or 20gb drive, not 7200RPM. I just looked at the maxtor data sheet for the drive family. It's a 5400 RPM 20 GB drive, I think. > But playing around with smartmontools makes it look like there isn't > really support for this drive: smartmon doesn't seem to understand the > info the drive returns. Is this a known issue with maxtor drives? Not at all. Maxtor was pretty involved in writing the ATA SMART specs and these drives definitely implement it. And when I look at the output that you sent from smartctl a month ago, it seemed pretty sensible. On the other hand, if the disk is damaged then some of the values returned could be garbage. But on the whole it does appear to support smart and I think smartmontools is reporting correctly what's on the disk. Did you try running some self-tests as I had suggested in November? If so, send the output of smartctl -a along, please. Cheers, Bruce > >From: Bruce Allen <ba...@gr...> > >To: Tim Carr <cyg...@ho...> > >CC: sma...@li... > >Subject: Re: [Smartmontools-support]Maxtor 100gb 7200rpm 2mb cache, odd > >output > >Date: Mon, 11 Nov 2002 07:19:48 -0600 (CST) > > > >Hi Tim, > > > >I just noticed a couple of other things about your disk: > > > > > SMART Error Log Version: 1 > > > ATA Error Count: 1947 (device log contains only the most recent five > >errors) > > > >This is a VERY high number of ATA errors. The most recent > >of these errors occured at time: > > > > > Error 1 occurred at disk power-on lifetime: 2156 hours > > > >Is this disk only about 3 or 4 months old? If so, you should use the "-m" > >option to smartctl; the power on lifetime is stored in minutes not hours. > > > > > SMART Self-test log, version number 1 > > > No self-tests have been logged > > > >I would definitely run some disk self-tests. Use the -X and -S options to > >smartctl. After the test is over, you can view the results with -L (or > >with -a). > > > >Cheers, > > Bruce > > > _________________________________________________________________ > Tired of spam? Get advanced junk mail protection with MSN 8. > http://join.msn.com/?page=features/junkmail > > |