public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Samuelsson <sam@home.se>
To: dougg@torque.net
Cc: Mark Salyzyn <Mark_Salyzyn@adaptec.com>,
	Linux-Scsi <linux-scsi@vger.kernel.org>,
	AACRAID <AACRAID@adaptec.com>
Subject: Re: aacraid and S.M.A.R.T
Date: Thu, 31 Jul 2008 20:32:06 +0200	[thread overview]
Message-ID: <20080731203206.f19fdcfd.sam@home.se> (raw)
In-Reply-To: <4891FBA3.50703@torque.net>

On Thu, 31 Jul 2008 13:51:31 -0400
Douglas Gilbert <dougg@torque.net> wrote:

> Martin Samuelsson wrote:
> > On Thu, 31 Jul 2008 10:47:33 -0400
> > Mark Salyzyn <Mark_Salyzyn@adaptec.com> wrote:
> > 
> >> On Jul 31, 2008, at 10:05 AM, Douglas Gilbert wrote:
> >>
> >>> Mark Salyzyn wrote:
> >>>> aacraid driver is not the emulation. The Firmware itself has a SAT  
> >>>> 0.9
> >>>> translation layer to the raw SATA drives at the physical transport,  
> >>>> the
> >>>> Firmware then deals with all the targets as SCSI representations.
> >>> Mark,
> >>> Is that SAT interface at the physical transport accessible
> >>> to something like smartmontools?
> >> YES, that is the whole reason we added the physical access via /dev/ 
> >> sg* in the driver!!!
> >>
> >> You may have to do a '-d ata', the patch to smartmontools to automate  
> >> this for SATA devices was not approved by Adaptec. SAS drives work.
> > 
> > Does that mean that
> > 
> > [root@disk ~]# smartctl -a -d ata /dev/sg1
> > 
> > should return something nicer than
> > 
> > ====
> > smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> > Home page is http://smartmontools.sourceforge.net/
> 
> Martin,
> I wouldn't use smartmontools version 5.36 . Could you try
> version 5.38?

Sure can do, after fetching the tar ball and a fitting C++ compiler.

> Also please don't use "-d ata" on the command line; either don't
> give a "-d <interface>" argument, or (if there are still problems)
> try "-d sat".

That did some kind of trick. Without -d sat, the result was the same as before; "bad response to IEC mode page", but with it, there's _something_ happening:

====
[root@disk ~]# smartctl -a -d sat -T permissive /dev/sg1
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     x_05_9anemf_er
Serial Number:    [No Information Found]
Firmware Version: #<binary junk>
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   14
ATA Standard is:  Not recognized. Minor revision code: 0xb7f8
Local Time is:    Thu Jul 31 20:18:20 2008 CEST
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
                  Checking for SMART support by trying SMART ENABLE command.
                  SMART ENABLE appeared to work!  Continuing.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
                  Checking to be sure by trying SMART RETURN STATUS command.
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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Total time to complete Offline 
data collection:                 (   0) seconds.
Offline data collection
capabilities:                    (0x00)         Offline data collection not supported.
SMART capabilities:            (0x0000) Automatic saving of SMART data                                  is not implemented.
Error logging capability:        (0x00) Error logging NOT supported.
                                        No General Purpose Logging support.

Warning: device does not support Error Logging
SMART Error Log Version: 0
No Errors Logged

Warning: device does not support Self Test Logging
SMART Self-test log structure revision number 0
Warning: ATA Specification requires self-test log structure revision number = 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


Device does not support Selective Self Tests/Logging
====

(I'd say the overall outcome was a failure, if somewhat less than before.)

Doing the same to /dev/sdb gives almost the same; the difference is in:

====
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   15
ATA Standard is:  Not recognized. Minor revision code: 0x83
====

Without permissive, it stops after the second "Ambiguous".

Regards,
/Sam

> 
> Doug Gilbert
> 
> 
> > Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)
> > 
> > A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
> > ====
> > ?
> > 
> > Without it, I at least get the drive name:
> > 
> > ====
> > [root@disk ~]# smartctl -a /dev/sg1
> > smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> > Home page is http://smartmontools.sourceforge.net/
> > 
> > Device: WDC      WD3200KS-00PFB0  Version: 21.0
> >>> Terminate command early due to bad response to IEC mode page
> > A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
> > ====
> > 
> > The responses are identical for /dev/sdb, by the way. And two permissives state that SMART ENABLE failed in the former case, and that the response to IEC mode page was bad.
> > 
> > I got what seems to be Dell's latest firmware for the card
> > 
> > http://support.us.dell.com/support/downloads/format.aspx?releaseid=R155588&c=us&l=en&cs=&s=gen
> > 
> > (for the CERC SATA 1.5/6ch card, which should be the same), but it didn't like the card.
> > 
> > AFA0> controller details
> > Executing: controller details
> > Controller Information
> > ----------------------
> >          Remote Computer: .
> >              Device Name: AFA0
> >          Controller Type: Adaptec 2610SA
> >              Access Mode: READ-WRITE
> > Controller Serial Number: Last Six Digits = C31E83
> >       Number of Channels: 1
> >      Devices per Channel: 15
> > Controller Physical Slot: 2
> >           Controller CPU: i960 series
> >     Controller CPU Speed: 100 Mhz
> >        Controller Memory: 64 Mbytes
> >            Battery State: Not Present
> > 
> > Component Revisions
> > -------------------
> >                 CLI: 4.1-0 (Build #7420)
> >                 API: 4.1-0 (Build #7420)
> >     Miniport Driver: 1.1-5 (Build #2453)
> > Controller Software: 4.2-1 (Build #9304)
> >     Controller BIOS: 4.2-1 (Build #9304)
> > Controller Firmware: (Build #9304)
> > 
> > Regards,
> > /Sam
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> > 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-07-31 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 21:54 aacraid and S.M.A.R.T Martin Samuelsson
2008-07-31  2:06 ` Mark Salyzyn
2008-07-31  7:41   ` Martin Samuelsson
2008-07-31 14:05   ` Douglas Gilbert
2008-07-31 14:47     ` Mark Salyzyn
2008-07-31 15:27       ` Martin Samuelsson
2008-07-31 15:49         ` Mark Salyzyn
2008-07-31 16:01           ` Martin Samuelsson
2008-07-31 17:51         ` Douglas Gilbert
2008-07-31 18:32           ` Martin Samuelsson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080731203206.f19fdcfd.sam@home.se \
    --to=sam@home.se \
    --cc=AACRAID@adaptec.com \
    --cc=Mark_Salyzyn@adaptec.com \
    --cc=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox