Re: [Smartmontools-support]Help needed

[Bruce A. <ba...@gr...>]

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