headers
Bruce Allen | 27 Oct 2002 16:08
Picon
Favicon

Brian Lin's questions

Brian,

I apologize for not replying sooner.  There has been some problem with the
mailing list and I have not been getting the mail sent to it.  Hopefully I
willn now have access.

Let me reply to all three postings at once:

> hi   can you tell me why send 1 for enable smart?

use smartctl -e /dev/hda
(or give appropriate device name).  The man page has this as an
example. If you have installed smartmontools on your system, do 
man 8 smartctl
else in the directory where you have installed smartmontools, do
man ./smartctl.8

> hi I am great to find your team.I read the ATA-4 , 5, 6 I want to know
> about SMART difinium.If you are free can you tell me more.

Please see the "REFERENCES" section on the web page
http://smartmontools.sourceforge.net
and read the man pages above.

> I am use 2.4.14 for redhat linux. I stardy ATA-5 and I want use ioctl
> send a value to Sector Number  but I find I can not send to there can
> you help me?

I am not much of an expert -- the best I can do is suggest that you read
the code in atacmds.c.  There are twoo different IOCTLs used.  The
(Continue reading)

Permalink | Reply | 2 comments |
headers
Bruce Allen | 27 Oct 2002 16:39
Picon
Favicon

reports on changing attributes (0 <at> pervalidus.{net, {dyndns.}org})

Hi,

I apologize for not replying sooner.  For unknown reasons I have not been
getting email destined for the mailing list.  Let me reply to everything
at once:

> Hi. With smartd from smartsuite 2.1 I got the following each 30
> minutes:
> 
> Device: /dev/hda, S.M.A.R.T. Attribute: 1 Changed -66
> 
> With smartd from smartmontools 5.0-10 I get:
> 
> Device: /dev/hda, S.M.A.R.T. Attribute: 255 Changed from 100 to 166

I've changed the message so instead of showing the amount of the change,
it shows initial and final values.

> Device Model:     MAXTOR 6L060J3
> Serial Number:    663200252994
> Firmware Version: A93.0500
> ATA Version is:   5
> ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
> SMART support is: Enabled
> 
> What I find strange is that I don't see Attribute 1 or 255 with
> smartctl -a /dev/hda.

There is probably a bug in smartd, where it incorrectly identifies these
as atributes.  I'll have a look.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bruce Allen | 27 Oct 2002 17:20
Picon
Favicon

Guy Coates Bug is smartctl?

Hi Guy,

Sorry for the delay in replying.  For some reason I have not been getting
mail from the list.  Let me reply to all inquiries at once:

>  This patch makes smartctl exit with 1 if it detects a smart failure.

I would have put this in sooner if I had known.  As it was a few days ago
I added exit status to smartctl.  This started in release 5.0-11 and has
continued.  To quote from the changelog:

smartctl now returns sensible values (bitmask).  See smartctl.h for the
values, and the man page for documentation.

Here is the relevant part of the man page:

RETURN VALUES
       The  return  values of smartctl are defined by a bitmask.  For the
moment this only
       works on ATA disks.  The different bits in the return value are as
follows:

       Bit 0: Command line did not parse.

       Bit 1: Device open failed, or device did not return an IDENTIFY
DEVICE structure.

       Bit 2: Some SMART command to the disk failed.

       Bit 3: SMART status check returned "DISK FAILING".
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bruce Allen | 29 Oct 2002 01:17
Picon
Favicon

Re: smartd

Hi Russell,

I just wanted to let you know that I've put a new version of smartmontools
into CVS.  This now implements your request about ignoring changes in
certain attributes.  It's documented in the man page smartd.8.

This is all controlled by entries in /etc/smartd.conf.  A line that reads

/dev/hda -a -I 194

for example would monitor smart status, the number of errors in the ATA
error log, the number of errors in the self test log, and would track
changes in both prefailure and usage attributes.  However it will ignore
attribute 194 (temperature). 

I haven't generated a release yet; I was hoping that you and some others
would download the code from CVS and try it first.  It's at
http://smartmontools.sourceforge.net/

Cheers,
	Bruce

On Fri, 25 Oct 2002, Bruce Allen wrote:

> Hi Russell,
> 
> I've been working on modernizing the smartd and smartctl -- see
> http://smartmontools.sourceforge.net/
> I've put your idea about being able to ignore certain attributes into the
> "to-do" list.  It should be quite easy.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frédéric L. W. Meunier | 29 Oct 2002 02:18

Re: Brian Lin's questions

Bruce Allen wrote:

>> Hi. With smartd from smartsuite 2.1 I got the following each
>> 30 minutes:
>>
>> Device: /dev/hda, S.M.A.R.T. Attribute: 1 Changed -66
>>
>> With smartd from smartmontools 5.0-10 I get:
>>
>> Device: /dev/hda, S.M.A.R.T. Attribute: 255 Changed from 100 to 166

> I've changed the message so instead of showing the amount of
> the change, it shows initial and final values.

BTW, with 5.0-16 I always get:

Device: /dev/hda, SMART Attribute: 255 Unknown_Attribute changed from 100 to 165

With 5.0-11 I always got:

Device: /dev/hda, SMART Attribute: 255 Unknown_Attribute changed from 100 to 11

>> Device Model:     MAXTOR 6L060J3
>> Serial Number:    663200252994
>> Firmware Version: A93.0500
>> ATA Version is:   5
>> ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
>> SMART support is: Enabled
>>
>> What I find strange is that I don't see Attribute 1 or 255
(Continue reading)

Permalink | Reply | 502 comments |
headers
Bruce Allen | 29 Oct 2002 10:56
Picon
Favicon

Re: Re: Brian Lin's questions

> BTW, with 5.0-16 I always get:
> 
> Device: /dev/hda, SMART Attribute: 255 Unknown_Attribute changed from 100 to 165

> With 5.0-11 I always got:
> 
> Device: /dev/hda, SMART Attribute: 255 Unknown_Attribute changed from 100 to 11

This is a bit odd; I don't understand it yet.

Please send me the output of smartd -VXB for the version 11 and version 16
code that you are using (depending whether you built it using CVS or from
a release, it may contain slightly different module versions).  This way I
can compare the exact routines that are producing this.

> >> Device Model:     MAXTOR 6L060J3
> >> Serial Number:    663200252994
> >> Firmware Version: A93.0500
> >> ATA Version is:   5
> >> ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
> >> SMART support is: Enabled
> >>
> >> What I find strange is that I don't see Attribute 1 or 255
> >> with smartctl -a /dev/hda.
> 
> > There is probably a bug in smartd, where it incorrectly
> > identifies these as atributes.  I'll have a look.
> 
> I thought Attribute 1 was "Raw_Read_Error_Rate".
> ~
(Continue reading)

Permalink | Reply | 502 comments |
headers
Bruce Allen | 29 Oct 2002 11:03
Picon
Favicon

Re: Attribute 255 inconsistent smartd/smartctl

> Please send me the output of smartd -VXB for the version 11 and version 16

I meant smartd -VX

Bruce

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Permalink | Reply | 6 comments |
headers
Frédéric L. W. Meunier | 29 Oct 2002 17:38

Re: Attribute 255 inconsistent smartd/smartctl

On Tue, 29 Oct 2002, Bruce Allen wrote:

> > Please send me the output of smartd -VXB for the version 11 and version 16
>
> I meant smartd -VX

5.0-16:

smartd version 5.0-16 - S.M.A.R.T. Daemon.
Home page is http://smartmontools.sourceforge.net/

smartd comes with ABSOLUTELY NO WARRANTY. This
is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License Version 2.
See http://www.gnu.org for further details.

CVS version IDs of files used to build this code are:
Module: smartd.c      revision: 1.31   date: 2002/10/25
  uses: atacmds.h     revision: 1.18   date: 2002/10/24
  uses: scsicmds.h    revision: 1.7    date: 2002/10/22
  uses: smartd.h      revision: 1.8    date: 2002/10/25
Module: atacmds.c     revision: 1.23   date: 2002/10/24
  uses: atacmds.h     revision: 1.18   date: 2002/10/24
Module: scsicmds.c    revision: 1.11   date: 2002/10/23
  uses: scsicmds.h    revision: 1.7    date: 2002/10/22

5.0-11:

smartd version 5.0-11 - S.M.A.R.T. Daemon
Home page is http://smartmontools.sourceforge.net/
(Continue reading)

Permalink | Reply | 5 comments |
headers
Frédéric L. W. Meunier | 29 Oct 2002 17:53

Re: Re: Brian Lin's questions

On Tue, 29 Oct 2002, Bruce Allen wrote:

> > (  1)Raw Read Error Rate...
> >
> > which I never had with smartsuite or smartmontools.
>
> Interesting.  This attribute ought to exist in your drive.
> Could you post the complete output of smartctl -a please?

=== START OF INFORMATION SECTION ===
Device Model:     MAXTOR 6L060J3
Serial Number:    663200252994
Firmware Version: A93.0500
ATA Version is:   5
ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Off-line data collection status: (0x02) Offline data collection activity
                                        completed without error.
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:                 (  35) seconds.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Bruce Allen | 29 Oct 2002 20:35
Picon
Favicon

Why is attribute 255 reported differently in -5.0-11 and -16

Hi Frédéric,

I went through the code pretty closely, comparing the file differences
between smartd 5.0-11 and 5.0-16.  I can't find any cause for the
difference in the reporting on your attribute #255.

The only files that differ are:
> Module: smartd.c      revision: 1.31   date: 2002/10/25
>   uses: smartd.h      revision: 1.8    date: 2002/10/25
> Module: atacmds.c     revision: 1.23   date: 2002/10/24
> 
> Module: smartd.c      revision: 1.24   date: 2002/10/24
>   uses: smartd.h      revision: 1.7    date: 2002/10/24
> Module: atacmds.c     revision: 1.22   date: 2002/10/24

In comparing these I did find one bug (now fixed).  I'd left a "break;"
out of a switch statement so that Attribute 231 would be mistakenly
identified as "unrecognized" rather than as temperature.  But it didn't
have any other effect.  It's not responsible for what you are seeing.

> BTW, I'm using CVS, but with tagged releases:
> 
> RELEASE_5_0_11 and RELEASE_5_0_16

Do you have an older 2.2 kernel?  Strange compiler?  Anything
non-standard?  You just did "make"?

I'd be interested to know if the problems persist if you use one of the
binary distribution formats, eg the .rpm
(Continue reading)

Permalink | Reply | 4 comments |

Gmane