From: David S. <pe...@le...> - 2003-02-24 07:08:31
|
Hi there, I have two hard drives in this machine, hda is a ST34321A, hdc is a Maxtor 90648D3 I've enabled SMART support in the bios of this machine, and tried using the latest release of the smartmontools software (5.1-7) Both drives are coming up with checksum errors for the data and the thresholds structures, and some of the results look off. Is this meant to happen, am I unlucky and have two damaged drives, and is there any way of fixing the checksums? I'll attach the results of smartctl -a at the end of this mail. This is a 2.4.18 kernel, using devfs. Regards, David hda: smartctl -a /dev/hda smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST34321A Serial Number: VTD72748 Firmware Version: 2.09 ATA Version is: 4 ATA Standard is: Unrecognized. Minor revision code: 0x00 Local Time is: Mon Feb 24 01:03:27 2003 CST SMART support is: Available - device has SMART capability. SMART support is: Enabled Warning! SMART Attribute Data Structure error: invalid SMART checksum. Warning! SMART Attribute Thresholds Structure error: invalid SMART checksum. === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Off-line data collection status: (0x00) Offline data collection activity was never started. Total time to complete off-line data collection: ( 0) seconds. Offline data collection capabilities: (0x00) Off-line data collection not supported. SMART capabilities: (0x0000) Automatic saving of SMART data is not implemented. Error logging capability: (0x00) Error logging NOT supported. SMART Attributes Data Structure revision number: 0 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0100 010 000 000 Old_age In_the_past 8077534060660 Warning: device does not support Error Logging Error SMART Error Log Read failed: Input/output error Smartctl: SMART Errorlog Read Failed Warning: device does not support Self Test Logging hdc: smartctl -a /dev/hdc -T permissive smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: Serial Number: Firmware Version: ATA Version is: 13 ATA Standard is: Unrecognized. Minor revision code: 0x00 Local Time is: Mon Feb 24 01:07:44 2003 CST SMART support is: Unavailable - device lacks SMART capability. Checking to be sure by trying SMART ENABLE command. SMART appears to work. Continuing. SMART support is: Available - device has SMART capability. SMART support is: Enabled Warning! SMART Attribute Data Structure error: invalid SMART checksum. Warning! SMART Attribute Thresholds Structure error: invalid SMART checksum. === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Off-line data collection status: (0x00) Offline data collection activity was never started. Total time to complete off-line data collection: ( 0) seconds. Offline data collection capabilities: (0x00) Off-line data collection not supported. SMART capabilities: (0x0000) Automatic saving of SMART data is not implemented. Error logging capability: (0x00) Error logging NOT supported. SMART Attributes Data Structure revision number: 0 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE WHEN_FAILED RAW_VALUE 6 Read_Channel_Margin 0x0100 011 000 000 Old_age In_the_past 20221983997 Warning: device does not support Error Logging Error SMART Error Log Read failed: Input/output error Smartctl: SMART Errorlog Read Failed Warning: device does not support Self Test Logging -- David Sutton Email: pe...@le... Jabber: per...@le... |
From: Bruce A. <ba...@gr...> - 2003-02-24 13:14:01
|
Hi David, > I have two hard drives in this machine, hda is a ST34321A, hdc is a > Maxtor 90648D3 > > I've enabled SMART support in the bios of this machine, and tried > using the latest release of the smartmontools software (5.1-7) > > Both drives are coming up with checksum errors for the data and the > thresholds structures, and some of the results look off. Is this meant > to happen, am I unlucky and have two damaged drives, and is there any > way of fixing the checksums? > > I'll attach the results of smartctl -a at the end of this mail. This > is a 2.4.18 kernel, using devfs. This is about the weirdest smartmontools output that I've seen. It gives me the shivers -- a bit like watching a three-legged dog walking. It would be very reassuring if there was at least one disk attached to the system giving normal output! I've never had any reports of checksum warnings before, and these warnings have been part of the smartmontools package for quite some time now. SMART stores data in 512-byte sectors, and the last byte is a checksum which should indicate consistency of the data. In the case of your drives, it indicated inconsistency. > hda: > > smartctl -a /dev/hda > smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF INFORMATION SECTION === > Device Model: ST34321A > Serial Number: VTD72748 > Firmware Version: 2.09 > ATA Version is: 4 > ATA Standard is: Unrecognized. Minor revision code: 0x00 > Local Time is: Mon Feb 24 01:03:27 2003 CST > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > Warning! SMART Attribute Data Structure error: invalid SMART checksum. > Warning! SMART Attribute Thresholds Structure error: invalid SMART > checksum. > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED The "Bottom Line": the disk says that it's OK! > See vendor-specific Attribute list for marginal Attributes. > > General SMART Values: > Off-line data collection status: (0x00) Offline data collection activity > was > never started. > Total time to complete off-line > data collection: ( 0) seconds. > Offline data collection > capabilities: (0x00) Off-line data collection > not supported. > SMART capabilities: (0x0000) Automatic saving of SMART data > is not implemented. > Error logging capability: (0x00) Error logging NOT supported. OK, this seems to indicate that the drive has rather minimal support for different SMART features. > SMART Attributes Data Structure revision number: 0 > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE > WHEN_FAILED RAW_VALUE > 5 Reallocated_Sector_Ct 0x0100 010 000 000 Old_age > In_the_past 8077534060660 This makes *some* sense, although the number of Reallocated sectors is higher than would be reasonable (more sectors than the disk has!) > Warning: device does not support Error Logging > Error SMART Error Log Read failed: Input/output error > Smartctl: SMART Errorlog Read Failed > Warning: device does not support Self Test Logging This is consistent with the lack of capabilities indicated before. Now, onto your Maxtor disk. I was able to find some documentation here: http://www.maxtor.co.jp/hdd_pdf/dm4320_pm.pdf Section 7-14 shows some SMART support. The output below is a bit like that from the previous disk, only even less data is available (like Device info). It's strange. How likely is it that something is weird with your kernel/build? I've used smartmontools on lots of 2.4.18 systems, so the kernel version should not be a problem. Is this x86 architecture? Cheers, Bruce > smartctl -a /dev/hdc -T permissive > smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF INFORMATION SECTION === > Device Model: > Serial Number: > Firmware Version: > ATA Version is: 13 > ATA Standard is: Unrecognized. Minor revision code: 0x00 > Local Time is: Mon Feb 24 01:07:44 2003 CST > SMART support is: Unavailable - device lacks SMART capability. > Checking to be sure by trying SMART ENABLE command. > SMART appears to work. Continuing. > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > Warning! SMART Attribute Data Structure error: invalid SMART checksum. > Warning! SMART Attribute Thresholds Structure error: invalid SMART > checksum. > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > See vendor-specific Attribute list for marginal Attributes. > > General SMART Values: > Off-line data collection status: (0x00) Offline data collection activity > was > never started. > Total time to complete off-line > data collection: ( 0) seconds. > Offline data collection > capabilities: (0x00) Off-line data collection > not supported. > SMART capabilities: (0x0000) Automatic saving of SMART data > is not implemented. > Error logging capability: (0x00) Error logging NOT supported. > > SMART Attributes Data Structure revision number: 0 > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE > WHEN_FAILED RAW_VALUE > 6 Read_Channel_Margin 0x0100 011 000 000 Old_age > In_the_past 20221983997 > > Warning: device does not support Error Logging > Error SMART Error Log Read failed: Input/output error > Smartctl: SMART Errorlog Read Failed > Warning: device does not support Self Test Logging > > > -- > David Sutton > Email: pe...@le... > Jabber: per...@le... > > > ------------------------------------------------------- > This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. > The most comprehensive and flexible code editor you can use. > Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. > www.slickedit.com/sourceforge > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: David S. <pe...@le...> - 2003-02-24 17:31:30
|
Hi Bruce. On Mon, Feb 24, 2003 at 07:13:46AM -0600, Bruce Allen wrote: > Hi David, > > This is about the weirdest smartmontools output that I've seen. It gives > me the shivers -- a bit like watching a three-legged dog walking. It > would be very reassuring if there was at least one disk attached to the > system giving normal output! > This is what I thought. > > I've never had any reports of checksum warnings before, and these warnings > have been part of the smartmontools package for quite some time now. > SMART stores data in 512-byte sectors, and the last byte is a checksum > which should indicate consistency of the data. In the case of your drives, > it indicated inconsistency. > > > > hda: > > > > smartctl -a /dev/hda > > smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen > > Home page is http://smartmontools.sourceforge.net/ > > > > === START OF INFORMATION SECTION === > > Device Model: ST34321A > > Serial Number: VTD72748 > > Firmware Version: 2.09 > > ATA Version is: 4 > > ATA Standard is: Unrecognized. Minor revision code: 0x00 > > Local Time is: Mon Feb 24 01:03:27 2003 CST > > SMART support is: Available - device has SMART capability. > > SMART support is: Enabled > > > > Warning! SMART Attribute Data Structure error: invalid SMART checksum. > > Warning! SMART Attribute Thresholds Structure error: invalid SMART > > checksum. > > === START OF READ SMART DATA SECTION === > > SMART overall-health self-assessment test result: PASSED > > The "Bottom Line": the disk says that it's OK! > > > See vendor-specific Attribute list for marginal Attributes. > > > > General SMART Values: > > Off-line data collection status: (0x00) Offline data collection activity > > was > > never started. > > Total time to complete off-line > > data collection: ( 0) seconds. > > Offline data collection > > capabilities: (0x00) Off-line data collection > > not supported. > > SMART capabilities: (0x0000) Automatic saving of SMART data > > is not implemented. > > Error logging capability: (0x00) Error logging NOT supported. > > OK, this seems to indicate that the drive has rather minimal support for > different SMART features. > > > SMART Attributes Data Structure revision number: 0 > > Vendor Specific SMART Attributes with Thresholds: > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE > > WHEN_FAILED RAW_VALUE > > 5 Reallocated_Sector_Ct 0x0100 010 000 000 Old_age > > In_the_past 8077534060660 > > This makes *some* sense, although the number of Reallocated sectors is > higher than would be reasonable (more sectors than the disk has!) > > > Warning: device does not support Error Logging > > Error SMART Error Log Read failed: Input/output error > > Smartctl: SMART Errorlog Read Failed > > Warning: device does not support Self Test Logging > > This is consistent with the lack of capabilities indicated before. > > Now, onto your Maxtor disk. I was able to find some documentation here: > http://www.maxtor.co.jp/hdd_pdf/dm4320_pm.pdf > Section 7-14 shows some SMART support. > > The output below is a bit like that from the previous disk, only even less > data is available (like Device info). It's strange. > > How likely is it that something is weird with your kernel/build? I've > used smartmontools on lots of 2.4.18 systems, so the kernel version should > not be a problem. Is this x86 architecture? > This machine is an AMD k6-333, 128Mb Ram, using the 2.4.18 kernel released by Nvidia to support the MX200 PCI graphics card. Its using Mandrake 8.2 for the linux distribution. Results from lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5591/5592 Host (rev 02) 00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 01) 00:01.1 Class ff00: Silicon Integrated Systems [SiS] ACPI 00:01.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 11) 00:02.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP 00:09.0 VGA compatible controller: nVidia Corporation NV11 (GeForce2 MX DDR) (rev b2) 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326 (rev 0b) Regarding the Maxtor, "ATA Version is: 13" seems worrying to me too. I'm including the results of hdparm, to see if there maybe any other clues there. Regards, David # hdparm -iI /dev/hda /dev/hda: Model=ST34321A, FwRev=2.09, SerialNo=VTD72748 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } RawCHS=8894/15/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=128kB, MaxMultSect=32, MultSect=32 CurCHS=8894/15/63, CurSects=8404830, LBA=yes, LBAsects=8404830 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 AdvancedPM=no WriteCache=enabled Drive Supports : Reserved : ATA-1 ATA-2 ATA-3 ATA-4 non-removable ATA device, with non-removable media Model Number: ST34321A Serial Number: VTD72748 Firmware Revision: 2.09 Standards: Supported: 1 2 3 4 Likely used: 4 Configuration: Logical max current cylinders 8894 8894 heads 15 15 sectors/track 63 63 bytes/track: 0 (obsolete) bytes/sector: 0 (obsolete) current sector capacity: 8404830 LBA user addressable sectors = 8404830 Capabilities: LBA, IORDY(can be disabled) Buffer size: 128.0kB Queue depth: 1 Standby timer values: spec'd by standard r/w multiple sector transfer: Max = 32 Current = 32 DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=240ns IORDY flow control=120ns Commands/features: Enabled Supported: * READ BUFFER cmd * WRITE BUFFER cmd * look-ahead * write cache * Power Management feature set * SMART feature set * DOWNLOAD MICROCODE cmd # hdparm -iI /dev/hdc /dev/hdc: Model=Maxtor 90648D3, FwRev=GAS6C712, SerialNo=A3DAB07C Config={ Fixed } RawCHS=12556/16/63, TrkSize=0, SectSize=0, ECCbytes=29 BuffType=DualPortCache, BuffSize=512kB, MaxMultSect=16, MultSect=16 CurCHS=12556/16/63, CurSects=12656448, LBA=yes, LBAsects=12656448 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 AdvancedPM=no WriteCache=enabled Drive Supports : ATA/ATAPI-4 T13 1153D revision 17 : ATA-1 ATA-2 ATA-3 ATA-4 removable ATA device, with non-removable media Standards: Supported: 8 9 10 11 13 Likely used: 13 Configuration: Logical max current cylinders 0 18241 heads 0 21302 sectors/track 0 17207 bytes/track: 0 (obsolete) bytes/sector: 0 (obsolete) current sector capacity: 1298215218 LBA user addressable sectors = 540634994 Capabilities: IORDY(may be)(cannot be disabled) Queue depth: 1 Standby timer values: spec'd by standard r/w multiple sector transfer: Max = 32 Current = ? Advanced power management level: 8000 DMA: not supported PIO: pio0 Security: Master password revision code = 193 386min for SECURITY ERASE UNIT. 32min for ENHANCED SECURITY ERASE UNIT. > > Cheers, > Bruce > > -- David Sutton Email: pe...@le... Jabber: per...@le... |
From: Bruce A. <ba...@gr...> - 2003-02-24 22:35:11
|
Hi David, On Mon, 24 Feb 2003, David Sutton wrote: > Hi Bruce. > > On Mon, Feb 24, 2003 at 07:13:46AM -0600, Bruce Allen wrote: > > Hi David, > > > > This is about the weirdest smartmontools output that I've seen. It gives > > me the shivers -- a bit like watching a three-legged dog walking. It > > would be very reassuring if there was at least one disk attached to the > > system giving normal output! > > > This is what I thought. After looking at some more of the output, I think that something is wrong but am not sure quite what. > > > smartctl -a /dev/hda > > > smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen > > > Home page is http://smartmontools.sourceforge.net/ > > > > > > === START OF INFORMATION SECTION === > > > Device Model: ST34321A > > > Serial Number: VTD72748 > > > Firmware Version: 2.09 > > > ATA Version is: 4 > > > ATA Standard is: Unrecognized. Minor revision code: 0x00 > > > Local Time is: Mon Feb 24 01:03:27 2003 CST > > > SMART support is: Available - device has SMART capability. > > > SMART support is: Enabled > > > > > > Warning! SMART Attribute Data Structure error: invalid SMART checksum. > > > Warning! SMART Attribute Thresholds Structure error: invalid SMART > > > checksum. > > > === START OF READ SMART DATA SECTION === > > > SMART overall-health self-assessment test result: PASSED > > > > The "Bottom Line": the disk says that it's OK! > > > > > See vendor-specific Attribute list for marginal Attributes. > > > > > > General SMART Values: > > > Off-line data collection status: (0x00) Offline data collection activity > > > was > > > never started. > > > Total time to complete off-line > > > data collection: ( 0) seconds. > > > Offline data collection > > > capabilities: (0x00) Off-line data collection > > > not supported. > > > SMART capabilities: (0x0000) Automatic saving of SMART data > > > is not implemented. > > > Error logging capability: (0x00) Error logging NOT supported. > > > > OK, this seems to indicate that the drive has rather minimal support for > > different SMART features. > > > > > SMART Attributes Data Structure revision number: 0 > > > Vendor Specific SMART Attributes with Thresholds: > > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE > > > WHEN_FAILED RAW_VALUE > > > 5 Reallocated_Sector_Ct 0x0100 010 000 000 Old_age > > > In_the_past 8077534060660 > > > > This makes *some* sense, although the number of Reallocated sectors is > > higher than would be reasonable (more sectors than the disk has!) > > > > > Warning: device does not support Error Logging > > > Error SMART Error Log Read failed: Input/output error > > > Smartctl: SMART Errorlog Read Failed > > > Warning: device does not support Self Test Logging > > > > This is consistent with the lack of capabilities indicated before. > > > > Now, onto your Maxtor disk. I was able to find some documentation here: > > http://www.maxtor.co.jp/hdd_pdf/dm4320_pm.pdf > > Section 7-14 shows some SMART support. > > > > The output below is a bit like that from the previous disk, only even less > > data is available (like Device info). It's strange. > > > > How likely is it that something is weird with your kernel/build? I've > > used smartmontools on lots of 2.4.18 systems, so the kernel version should > > not be a problem. Is this x86 architecture? > > > This machine is an AMD k6-333, 128Mb Ram, using the 2.4.18 kernel > released by Nvidia to support the MX200 PCI graphics card. Its using Mandrake > 8.2 for the linux distribution. OK. How did you install smartmontools? From the binary RPM? Or did you build it from the tarball or a source RPM? If you installed from the binary RPM, I am wondering if the k6 instruction set is not compatible with the binary. [This may be impossible -- I am just grasping at straws.] > I'm including the results of hdparm, to see if there maybe any other > clues there. In fact there is a very big clue. If you compare the output of hdparm -i /dev/hda and hdparm -I /dev/hda for the Maxtor disk you'll see that in the -I case, the disk model number, serial number and firmware version are missing. And it also gets confused about what the ATA standard is. The -i argument uses: if (ioctl(device, HDIO_GET_IDENTITY, buf)){ whereas -I uses: unsigned char parms[HDIO_DRIVE_CMD_HDR_SIZE+sizeof(*buf)]= {WIN_IDENTIFY, 0, 0, 1,}; ioctl(device ,HDIO_DRIVE_CMD,parms) So I suspect that something is going wrong with the HDIO_DRIVE_CMD ioctl(). But I don't know why this is happening. Please tell me about how you installed smartmontools. Cheers, Bruce |
From: David S. <pe...@le...> - 2003-02-25 05:22:29
|
Hi Bruce, On Mon, Feb 24, 2003 at 04:34:55PM -0600, Bruce Allen wrote: > Hi David, > <snip> > > OK. > > How did you install smartmontools? From the binary RPM? Or did you build > it from the tarball or a source RPM? If you installed from the binary > RPM, I am wondering if the k6 instruction set is not compatible with the > binary. [This may be impossible -- I am just grasping at straws.] > I followed the instructions on the page and downloaded the binary RPM. To test the theory, I just rebuilt the binary RPM from the SRPM and ran smartctl. Its a lot happier now. There is definately something about the binary RPM it doesn't like. Kernel version changes? > > > I'm including the results of hdparm, to see if there maybe any other > > clues there. > > In fact there is a very big clue. If you compare the output of > hdparm -i /dev/hda > and > hdparm -I /dev/hda > > for the Maxtor disk you'll see that in the -I case, the disk model > number, serial number and firmware version are missing. And it also gets > confused about what the ATA standard is. > > The -i argument uses: > if (ioctl(device, HDIO_GET_IDENTITY, buf)){ > whereas -I uses: > unsigned char parms[HDIO_DRIVE_CMD_HDR_SIZE+sizeof(*buf)]= > {WIN_IDENTIFY, 0, 0, 1,}; > ioctl(device ,HDIO_DRIVE_CMD,parms) > So I suspect that something is going wrong with the HDIO_DRIVE_CMD > ioctl(). > /dev/hda is now reporting ok, however the maxtor (/dev/hdc) is still unhappy. I've included both outputs again at the end of the post. > > But I don't know why this is happening. > > Please tell me about how you installed smartmontools. > > Cheers, > Bruce > Regards, David # smartctl -a /dev/hda smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST34321A Serial Number: VTD72748 Firmware Version: 2.09 ATA Version is: 4 ATA Standard is: Unrecognized. Minor revision code: 0x00 Local Time is: Mon Feb 24 23:13:12 2003 CST 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. Total time to complete off-line data collection: ( 0) seconds. Offline data collection capabilities: (0x03) SMART execute Offline immediate. Automatic timer ON/OFF support. Suspend Offline collection upon new command. No Offline surface scan supported. No Self-test supported. SMART capabilities: (0x0002) Does not save SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x00) Error logging NOT supported. SMART Attributes Data Structure revision number: 5 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE WHEN_FAILED RAW _VALUE 1 Raw_Read_Error_Rate 0x000a 116 096 000 Old_age - 127 835917 3 Spin_Up_Time 0x0006 079 077 000 Old_age - 0 4 Start_Stop_Count 0x0013 100 100 020 Pre-fail - 987 5 Reallocated_Sector_Ct 0x0013 100 100 036 Pre-fail - 5 7 Seek_Error_Rate 0x000b 070 060 030 Pre-fail - 743 09597 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail - 0 12 Power_Cycle_Count 0x0013 099 099 020 Pre-fail - 131 8 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age - 0 Warning: device does not support Error Logging Error SMART Error Log Read failed: Input/output error Smartctl: SMART Errorlog Read Failed Warning: device does not support Self Test Logging # smartctl -a /dev/hdc smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: Maxtor 90648D3 Serial Number: A3DAB07C Firmware Version: GAS6C712 ATA Version is: 4 ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17 Local Time is: Mon Feb 24 23:13:23 2003 CST SMART support is: Available - device has SMART capability. SMART support is: Enabled Warning! SMART Attribute Data Structure error: invalid SMART checksum. Warning! SMART Attribute Thresholds Structure error: invalid SMART checksum. === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Off-line data collection status: (0x00) Offline data collection activity was never started. Total time to complete off-line data collection: ( 0) seconds. Offline data collection capabilities: (0x00) Off-line data collection not sup ported. SMART capabilities: (0x0000) Automatic saving of SMART data is not i mplemented. Error logging capability: (0x00) Error logging NOT supported. SMART Attributes Data Structure revision number: 0 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE WHEN_FAILED RAW _VALUE 6 Read_Channel_Margin 0x0100 011 000 000 Old_age In_the_past 204 84455677 Warning: device does not support Error Logging Error SMART Error Log Read failed: Input/output error Smartctl: SMART Errorlog Read Failed Warning: device does not support Self Test Logging -- David Sutton Email: pe...@le... Jabber: per...@le... |
From: David S. <pe...@le...> - 2003-02-25 06:30:28
|
Hi again, I spoke too soon. I don't know what has changed, but the reporting is broken again. I'm getting the checksum errors again for both drives, and i'm having to use the "-T permissive" on /dev/hdc again. This is very strange indeed. The output is the same as the first time I ran smartctl. Regards, David On Mon, Feb 24, 2003 at 11:22:25PM -0600, David Sutton wrote: > Hi Bruce, > > On Mon, Feb 24, 2003 at 04:34:55PM -0600, Bruce Allen wrote: > > Hi David, > > > <snip> > > > > OK. > > > > How did you install smartmontools? From the binary RPM? Or did you build > > it from the tarball or a source RPM? If you installed from the binary > > RPM, I am wondering if the k6 instruction set is not compatible with the > > binary. [This may be impossible -- I am just grasping at straws.] > > > I followed the instructions on the page and downloaded the binary RPM. > To test the theory, I just rebuilt the binary RPM from the SRPM and ran > smartctl. Its a lot happier now. There is definately something about the > binary RPM it doesn't like. Kernel version changes? > > > > > I'm including the results of hdparm, to see if there maybe any other > > > clues there. > > > > In fact there is a very big clue. If you compare the output of > > hdparm -i /dev/hda > > and > > hdparm -I /dev/hda > > > > for the Maxtor disk you'll see that in the -I case, the disk model > > number, serial number and firmware version are missing. And it also gets > > confused about what the ATA standard is. > > > > The -i argument uses: > > if (ioctl(device, HDIO_GET_IDENTITY, buf)){ > > whereas -I uses: > > unsigned char parms[HDIO_DRIVE_CMD_HDR_SIZE+sizeof(*buf)]= > > {WIN_IDENTIFY, 0, 0, 1,}; > > ioctl(device ,HDIO_DRIVE_CMD,parms) > > So I suspect that something is going wrong with the HDIO_DRIVE_CMD > > ioctl(). > > > /dev/hda is now reporting ok, however the maxtor (/dev/hdc) is still > unhappy. I've included both outputs again at the end of the post. > > > > But I don't know why this is happening. > > > > Please tell me about how you installed smartmontools. > > > > Cheers, > > Bruce > > > > Regards, > > David > > # smartctl -a /dev/hda > smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF INFORMATION SECTION === > Device Model: ST34321A > Serial Number: VTD72748 > Firmware Version: 2.09 > ATA Version is: 4 > ATA Standard is: Unrecognized. Minor revision code: 0x00 > Local Time is: Mon Feb 24 23:13:12 2003 CST > 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. > Total time to complete off-line > data collection: ( 0) seconds. > Offline data collection > capabilities: (0x03) SMART execute Offline immediate. > Automatic timer ON/OFF support. > Suspend Offline collection upon > new > command. > No Offline surface scan > supported. > No Self-test supported. > SMART capabilities: (0x0002) Does not save SMART data before > entering power-saving mode. > Supports SMART auto save timer. > Error logging capability: (0x00) Error logging NOT supported. > > SMART Attributes Data Structure revision number: 5 > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE > WHEN_FAILED RAW > _VALUE > 1 Raw_Read_Error_Rate 0x000a 116 096 000 Old_age - > 127 > 835917 > 3 Spin_Up_Time 0x0006 079 077 000 Old_age - > 0 > 4 Start_Stop_Count 0x0013 100 100 020 Pre-fail - > 987 > 5 Reallocated_Sector_Ct 0x0013 100 100 036 Pre-fail - > 5 > 7 Seek_Error_Rate 0x000b 070 060 030 Pre-fail - > 743 > 09597 > 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail - > 0 > 12 Power_Cycle_Count 0x0013 099 099 020 Pre-fail - > 131 > 8 > 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age - > 0 > > Warning: device does not support Error Logging > Error SMART Error Log Read failed: Input/output error > Smartctl: SMART Errorlog Read Failed > Warning: device does not support Self Test Logging > > > # smartctl -a /dev/hdc > smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF INFORMATION SECTION === > Device Model: Maxtor 90648D3 > Serial Number: A3DAB07C > Firmware Version: GAS6C712 > ATA Version is: 4 > ATA Standard is: ATA/ATAPI-4 T13 1153D revision 17 > Local Time is: Mon Feb 24 23:13:23 2003 CST > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > Warning! SMART Attribute Data Structure error: invalid SMART checksum. > Warning! SMART Attribute Thresholds Structure error: invalid SMART > checksum. > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > See vendor-specific Attribute list for marginal Attributes. > > General SMART Values: > Off-line data collection status: (0x00) Offline data collection activity > was > never started. > Total time to complete off-line > data collection: ( 0) seconds. > Offline data collection > capabilities: (0x00) Off-line data collection > not sup > ported. > SMART capabilities: (0x0000) Automatic saving of SMART data > is not i > mplemented. > Error logging capability: (0x00) Error logging NOT supported. > > SMART Attributes Data Structure revision number: 0 > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE > WHEN_FAILED RAW > _VALUE > 6 Read_Channel_Margin 0x0100 011 000 000 Old_age > In_the_past 204 > 84455677 > > Warning: device does not support Error Logging > Error SMART Error Log Read failed: Input/output error > Smartctl: SMART Errorlog Read Failed > Warning: device does not support Self Test Logging > > > -- > David Sutton > Email: pe...@le... > Jabber: per...@le... > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support -- David Sutton Email: pe...@le... Jabber: per...@le... |
From: Bruce A. <ba...@gr...> - 2003-02-25 14:24:58
|
Hi David, > I spoke too soon. I don't know what has changed, but the reporting is > broken again. I'm getting the checksum errors again for both drives, > and i'm having to use the "-T permissive" on /dev/hdc again. This is > very strange indeed. The output is the same as the first time I ran > smartctl. At this point, the smart money is betting "there is something messsed up with your system". I am guessing that either the compiler that is installed or the libraries are not entirely compatible, or are not compatible with the K6 architecture of your machine. Please try what I suggested in the previous email, and post the gcc and libc output that I asked for. Cheers, Bruce [PS: are you sure that you are running the newly complied version of smartctl. Eg, do ./smartctl -a /dev/hd* in the sm5/ directory, not just smartctl -a /dev/hd* since the latter may run the /usr/sbin/ executable.] |
From: Bruce A. <ba...@gr...> - 2003-02-25 14:21:31
|
Hi David, > > How did you install smartmontools? From the binary RPM? Or did you build > > it from the tarball or a source RPM? If you installed from the binary > > RPM, I am wondering if the k6 instruction set is not compatible with the > > binary. [This may be impossible -- I am just grasping at straws.] > I followed the instructions on the page and downloaded the binary RPM. > To test the theory, I just rebuilt the binary RPM from the SRPM and ran > smartctl. Its a lot happier now. There is definately something about the > binary RPM it doesn't like. Kernel version changes? I am not sure what it might be. There are really four different things that need to be compatible: -- Kernel -- C libraries -- Compiler -- Harware If there is a way for you to check that these things are consistent with your installation, it would be good. The fact that hdparm -I does not return the drive model/serial #/firmware is a sign that something is messed up. > /dev/hda is now reporting ok, however the maxtor (/dev/hdc) is still > unhappy. I've included both outputs again at the end of the post. In factor the Maxtor report is much better than before, in that the Drive Identity command is now correctly returning the drive model/serial #/firmware version info. > > But I don't know why this is happening. Here are some suggestions: In Makefile, change CFLAGS = -fsigned-char -Wall -O2 to CFLAGS = -fsigned-char -Wall -g and also change -o smartctl to --static -o smartctl and -o smartd to --static -o smartd See if that makes a difference. Also, post the output of gcc -dumpspecs and the output of /lib/libc.so.6 [You mauy need to replace the '6' above by whatever the right version number is of your libc.so.* file] Cheers, Bruce |
From: David S. <pe...@le...> - 2003-02-25 14:54:16
Attachments:
gcc-dumpspecs
|
Hi Bruce, The attached file is the output from gcc -dumpstats. This machine is using glibc v2.2.4, confirmed by the libc.so.6 symlink I'll continue looking around. I'm considering recompiling gcc and glibc on this system anyway, so can test if it is that. Regards, David On Tue, Feb 25, 2003 at 08:21:17AM -0600, Bruce Allen wrote: > Hi David, > > > > How did you install smartmontools? From the binary RPM? Or did you build > > > it from the tarball or a source RPM? If you installed from the binary > > > RPM, I am wondering if the k6 instruction set is not compatible with the > > > binary. [This may be impossible -- I am just grasping at straws.] > > > I followed the instructions on the page and downloaded the binary RPM. > > To test the theory, I just rebuilt the binary RPM from the SRPM and ran > > smartctl. Its a lot happier now. There is definately something about the > > binary RPM it doesn't like. Kernel version changes? > > I am not sure what it might be. There are really four different things > that need to be compatible: > -- Kernel > -- C libraries > -- Compiler > -- Harware > If there is a way for you to check that these things are consistent with > your installation, it would be good. The fact that hdparm -I does not > return the drive model/serial #/firmware is a sign that something is > messed up. > > > /dev/hda is now reporting ok, however the maxtor (/dev/hdc) is still > > unhappy. I've included both outputs again at the end of the post. > > In factor the Maxtor report is much better than before, in that the Drive > Identity command is now correctly returning the drive model/serial > #/firmware version info. > > > > But I don't know why this is happening. > > Here are some suggestions: > > In Makefile, change > CFLAGS = -fsigned-char -Wall -O2 > > to > CFLAGS = -fsigned-char -Wall -g > > and also change > -o smartctl > to > --static -o smartctl > and > -o smartd > to > --static -o smartd > > See if that makes a difference. > > Also, post the output of > gcc -dumpspecs > > and the output of > /lib/libc.so.6 > > [You mauy need to replace the '6' above by whatever the right > version number is of your libc.so.* file] > > Cheers, > Bruce > -- David Sutton Email: pe...@le... Jabber: per...@le... |
From: Bruce A. <ba...@gr...> - 2003-02-25 15:01:27
|
Hi David, Believe it or not, glibc is executable -- please run it so we can see how it was built, and post the output. Eg, on my system: [ballen@lap 2003-02]$ /lib/libc.so.6 GNU C Library stable release version 2.2.5, by Roland McGrath et al. Copyright (C) 1992-2001, 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 2.96 20000731 (Red Hat Linux 7.3 2.96-112). Compiled on a Linux 2.4.9-9 system on 2002-10-10. Available extensions: GNU libio by Per Bothner crypt add-on version 2.1 by Michael Glad and others The C stubs add-on version 2.1.2. linuxthreads-0.9 by Xavier Leroy BIND-8.2.3-T5B NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk Glibc-2.0 compatibility add-on by Cristian Gafton libthread_db work sponsored by Alpha Processor Inc Report bugs using the `glibcbug' script to <bu...@gn...>. Cheers, Bruce On Tue, 25 Feb 2003, David Sutton wrote: > Hi Bruce, > > The attached file is the output from gcc -dumpstats. This machine is > using glibc v2.2.4, confirmed by the libc.so.6 symlink > > I'll continue looking around. I'm considering recompiling gcc and > glibc on this system anyway, so can test if it is that. > > Regards, > > David > > On Tue, Feb 25, 2003 at 08:21:17AM -0600, Bruce Allen wrote: > > Hi David, > > > > > > How did you install smartmontools? From the binary RPM? Or did you build > > > > it from the tarball or a source RPM? If you installed from the binary > > > > RPM, I am wondering if the k6 instruction set is not compatible with the > > > > binary. [This may be impossible -- I am just grasping at straws.] > > > > > I followed the instructions on the page and downloaded the binary RPM. > > > To test the theory, I just rebuilt the binary RPM from the SRPM and ran > > > smartctl. Its a lot happier now. There is definately something about the > > > binary RPM it doesn't like. Kernel version changes? > > > > I am not sure what it might be. There are really four different things > > that need to be compatible: > > -- Kernel > > -- C libraries > > -- Compiler > > -- Harware > > If there is a way for you to check that these things are consistent with > > your installation, it would be good. The fact that hdparm -I does not > > return the drive model/serial #/firmware is a sign that something is > > messed up. > > > > > /dev/hda is now reporting ok, however the maxtor (/dev/hdc) is still > > > unhappy. I've included both outputs again at the end of the post. > > > > In factor the Maxtor report is much better than before, in that the Drive > > Identity command is now correctly returning the drive model/serial > > #/firmware version info. > > > > > > But I don't know why this is happening. > > > > Here are some suggestions: > > > > In Makefile, change > > CFLAGS = -fsigned-char -Wall -O2 > > > > to > > CFLAGS = -fsigned-char -Wall -g > > > > and also change > > -o smartctl > > to > > --static -o smartctl > > and > > -o smartd > > to > > --static -o smartd > > > > See if that makes a difference. > > > > Also, post the output of > > gcc -dumpspecs > > > > and the output of > > /lib/libc.so.6 > > > > [You mauy need to replace the '6' above by whatever the right > > version number is of your libc.so.* file] > > > > Cheers, > > Bruce > > > > -- > David Sutton > Email: pe...@le... > Jabber: per...@le... > |
From: David S. <pe...@le...> - 2003-02-25 15:15:12
|
Hi Bruce. Well they say you learn something new every day :) I've never come across this before. Heres the results. # /lib/libc.so.6 GNU C Library stable release version 2.2.4, by Roland McGrath et al. Copyright (C) 1992-1999, 2000, 2001 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 2.96 20000731 (Mandrake Linux 8.2 2.96-0.74mdk). Compiled on a Linux 2.4.17 system on 2002-02-06. Available extensions: GNU libio by Per Bothner crypt add-on version 2.1 by Michael Glad and others The C stubs add-on version 2.1.2. linuxthreads-0.9 by Xavier Leroy BIND-8.2.3-T5B NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk Glibc-2.0 compatibility add-on by Cristian Gafton libthread_db work sponsored by Alpha Processor Inc Report bugs using the `glibcbug' script to <bu...@gn...>. Regards, David On Tue, Feb 25, 2003 at 09:01:13AM -0600, Bruce Allen wrote: > Hi David, > > Believe it or not, glibc is executable -- please run it so we can see how > it was built, and post the output. > > Eg, on my system: > > [ballen@lap 2003-02]$ /lib/libc.so.6 > GNU C Library stable release version 2.2.5, by Roland McGrath et al. > Copyright (C) 1992-2001, 2002 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. > There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A > PARTICULAR PURPOSE. > Compiled by GNU CC version 2.96 20000731 (Red Hat Linux 7.3 2.96-112). > Compiled on a Linux 2.4.9-9 system on 2002-10-10. > Available extensions: > GNU libio by Per Bothner > crypt add-on version 2.1 by Michael Glad and others > The C stubs add-on version 2.1.2. > linuxthreads-0.9 by Xavier Leroy > BIND-8.2.3-T5B > NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk > Glibc-2.0 compatibility add-on by Cristian Gafton > libthread_db work sponsored by Alpha Processor Inc > Report bugs using the `glibcbug' script to <bu...@gn...>. > > Cheers, > Bruce > > > On Tue, 25 Feb 2003, David Sutton wrote: > > > Hi Bruce, > > > > The attached file is the output from gcc -dumpstats. This machine is > > using glibc v2.2.4, confirmed by the libc.so.6 symlink > > > > I'll continue looking around. I'm considering recompiling gcc and > > glibc on this system anyway, so can test if it is that. > > > > Regards, > > > > David > > > > On Tue, Feb 25, 2003 at 08:21:17AM -0600, Bruce Allen wrote: > > > Hi David, > > > > > > > > How did you install smartmontools? From the binary RPM? Or did you build > > > > > it from the tarball or a source RPM? If you installed from the binary > > > > > RPM, I am wondering if the k6 instruction set is not compatible with the > > > > > binary. [This may be impossible -- I am just grasping at straws.] > > > > > > > I followed the instructions on the page and downloaded the binary RPM. > > > > To test the theory, I just rebuilt the binary RPM from the SRPM and ran > > > > smartctl. Its a lot happier now. There is definately something about the > > > > binary RPM it doesn't like. Kernel version changes? > > > > > > I am not sure what it might be. There are really four different things > > > that need to be compatible: > > > -- Kernel > > > -- C libraries > > > -- Compiler > > > -- Harware > > > If there is a way for you to check that these things are consistent with > > > your installation, it would be good. The fact that hdparm -I does not > > > return the drive model/serial #/firmware is a sign that something is > > > messed up. > > > > > > > /dev/hda is now reporting ok, however the maxtor (/dev/hdc) is still > > > > unhappy. I've included both outputs again at the end of the post. > > > > > > In factor the Maxtor report is much better than before, in that the Drive > > > Identity command is now correctly returning the drive model/serial > > > #/firmware version info. > > > > > > > > But I don't know why this is happening. > > > > > > Here are some suggestions: > > > > > > In Makefile, change > > > CFLAGS = -fsigned-char -Wall -O2 > > > > > > to > > > CFLAGS = -fsigned-char -Wall -g > > > > > > and also change > > > -o smartctl > > > to > > > --static -o smartctl > > > and > > > -o smartd > > > to > > > --static -o smartd > > > > > > See if that makes a difference. > > > > > > Also, post the output of > > > gcc -dumpspecs > > > > > > and the output of > > > /lib/libc.so.6 > > > > > > [You mauy need to replace the '6' above by whatever the right > > > version number is of your libc.so.* file] > > > > > > Cheers, > > > Bruce > > > > > > > -- > > David Sutton > > Email: pe...@le... > > Jabber: per...@le... > > > -- David Sutton Email: pe...@le... Jabber: per...@le... |
From: Bruce A. <ba...@gr...> - 2003-02-25 15:40:06
|
Hi David, On Tue, 25 Feb 2003, David Sutton wrote: > Hi Bruce. > > Well they say you learn something new every day :) I've never come > across this before. Heres the results. > > # /lib/libc.so.6 <snip> > Compiled by GNU CC version 2.96 20000731 (Mandrake Linux 8.2 > 2.96-0.74mdk). The point now is to make sure that you have a compiler setup that is compatible with these libraries, and perhaps to try and check that when this library was compiled, the code that was emitted was K6-compatible. The most likely source of trouble is that the ATA standard uses some packed data structures, and if the compiler and libs are not correctly built for the platform, these data structures may get misaligned. [Reminder -- I am grasping at straws -- I am not sure what is going wrong but this is the only thing I can think of. Also, this is not an area where I am very competent -- an expert might be able to diagnose what is wrong much more quickly.] Cheers, Bruce > Compiled on a Linux 2.4.17 system on 2002-02-06. > Available extensions: > GNU libio by Per Bothner > crypt add-on version 2.1 by Michael Glad and others > The C stubs add-on version 2.1.2. > linuxthreads-0.9 by Xavier Leroy > BIND-8.2.3-T5B > NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk > Glibc-2.0 compatibility add-on by Cristian Gafton > libthread_db work sponsored by Alpha Processor Inc > Report bugs using the `glibcbug' script to <bu...@gn...>. > > Regards, > > David > On Tue, Feb 25, 2003 at 09:01:13AM -0600, Bruce Allen wrote: > > Hi David, > > > > Believe it or not, glibc is executable -- please run it so we can see how > > it was built, and post the output. > > > > Eg, on my system: > > > > [ballen@lap 2003-02]$ /lib/libc.so.6 > > GNU C Library stable release version 2.2.5, by Roland McGrath et al. > > Copyright (C) 1992-2001, 2002 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. > > There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A > > PARTICULAR PURPOSE. > > Compiled by GNU CC version 2.96 20000731 (Red Hat Linux 7.3 2.96-112). > > Compiled on a Linux 2.4.9-9 system on 2002-10-10. > > Available extensions: > > GNU libio by Per Bothner > > crypt add-on version 2.1 by Michael Glad and others > > The C stubs add-on version 2.1.2. > > linuxthreads-0.9 by Xavier Leroy > > BIND-8.2.3-T5B > > NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk > > Glibc-2.0 compatibility add-on by Cristian Gafton > > libthread_db work sponsored by Alpha Processor Inc > > Report bugs using the `glibcbug' script to <bu...@gn...>. > > > > Cheers, > > Bruce > > > > > > On Tue, 25 Feb 2003, David Sutton wrote: > > > > > Hi Bruce, > > > > > > The attached file is the output from gcc -dumpstats. This machine is > > > using glibc v2.2.4, confirmed by the libc.so.6 symlink > > > > > > I'll continue looking around. I'm considering recompiling gcc and > > > glibc on this system anyway, so can test if it is that. > > > > > > Regards, > > > > > > David > > > > > > On Tue, Feb 25, 2003 at 08:21:17AM -0600, Bruce Allen wrote: > > > > Hi David, > > > > > > > > > > How did you install smartmontools? From the binary RPM? Or did you build > > > > > > it from the tarball or a source RPM? If you installed from the binary > > > > > > RPM, I am wondering if the k6 instruction set is not compatible with the > > > > > > binary. [This may be impossible -- I am just grasping at straws.] > > > > > > > > > I followed the instructions on the page and downloaded the binary RPM. > > > > > To test the theory, I just rebuilt the binary RPM from the SRPM and ran > > > > > smartctl. Its a lot happier now. There is definately something about the > > > > > binary RPM it doesn't like. Kernel version changes? > > > > > > > > I am not sure what it might be. There are really four different things > > > > that need to be compatible: > > > > -- Kernel > > > > -- C libraries > > > > -- Compiler > > > > -- Harware > > > > If there is a way for you to check that these things are consistent with > > > > your installation, it would be good. The fact that hdparm -I does not > > > > return the drive model/serial #/firmware is a sign that something is > > > > messed up. > > > > > > > > > /dev/hda is now reporting ok, however the maxtor (/dev/hdc) is still > > > > > unhappy. I've included both outputs again at the end of the post. > > > > > > > > In factor the Maxtor report is much better than before, in that the Drive > > > > Identity command is now correctly returning the drive model/serial > > > > #/firmware version info. > > > > > > > > > > But I don't know why this is happening. > > > > > > > > Here are some suggestions: > > > > > > > > In Makefile, change > > > > CFLAGS = -fsigned-char -Wall -O2 > > > > > > > > to > > > > CFLAGS = -fsigned-char -Wall -g > > > > > > > > and also change > > > > -o smartctl > > > > to > > > > --static -o smartctl > > > > and > > > > -o smartd > > > > to > > > > --static -o smartd > > > > > > > > See if that makes a difference. > > > > > > > > Also, post the output of > > > > gcc -dumpspecs > > > > > > > > and the output of > > > > /lib/libc.so.6 > > > > > > > > [You mauy need to replace the '6' above by whatever the right > > > > version number is of your libc.so.* file] > > > > > > > > Cheers, > > > > Bruce > > > > > > > > > > -- > > > David Sutton > > > Email: pe...@le... > > > Jabber: per...@le... > > > > > > > -- > David Sutton > Email: pe...@le... > Jabber: per...@le... > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |