public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Samuelsson <sam@home.se>
To: Mark Salyzyn <Mark_Salyzyn@adaptec.com>
Cc: "dougg@torque.net" <dougg@torque.net>,
	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 18:01:57 +0200	[thread overview]
Message-ID: <20080731180157.826c2dcb.sam@home.se> (raw)
In-Reply-To: <6922644A-352E-42C1-8F6A-88FC4F01E04E@adaptec.com>

On Thu, 31 Jul 2008 11:49:09 -0400
Mark Salyzyn <Mark_Salyzyn@adaptec.com> wrote:

> Sounds like a compliance issue, this is solely at the Firmware's  
> discretion :-(

I suspected as much. It's a bit frustrating.

> It is somewhat clear you are communicating to the physical component,  
> but be aware that the logical (array) does NOT respond to SMART, only  
> the physical components. Looks like you need to take this up with Dell.

Do you mean that it looks like I get through to the firmware's interface, but that it does not forward my request to the physical device?

Yes, either I get through to Dell (though they seem reluctant to talk to people without service tags) or I will have to live with not knowing whether the disks risk running too hot or not, I suppose. We'll see what happens.

Thanks for your help! (All of you.)

/Sam

> 
> Sincerely -- Mark Salyzyn
> 
> On Jul 31, 2008, at 11:27 AM, 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/
> >
> > 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

  reply	other threads:[~2008-07-31 16:02 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 [this message]
2008-07-31 17:51         ` Douglas Gilbert
2008-07-31 18:32           ` Martin Samuelsson

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=20080731180157.826c2dcb.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