aacraid and S.M.A.R.T

aacraid and S.M.A.R.T

[Martin Samuelsson]

Hello list,

I have an old Adaptec 2610SA SATA RAID controller with six disks. As I'm a bit curious, I'd like to know, for example, the temperature they report. (afacli can't report those, and I suspect aaccli can't either) It seemed utterly impossible until I saw the expose_physicals module option, but after switching that on, I can at least see traces of the individual disks.

If I understand it correctly, aacraid provides an emulation layer between what I see and the physical disks, passing known commands and responses back and forth. However, S.M.A.R.T commands doesn't seem to be among those known ones, is that correct?

I'm running CentOS 5 with kernel 2.6.18, which is kind of old. Would running a spanking new kernel make me happier and support reading the temperature from the individual disks?

Regards,
/Sam

Re: aacraid and S.M.A.R.T

[Mark Salyzyn]

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.

SMART was supposed to be emulated, but on that old card it was never  
tested ... make sure you have the latest Firmware on the card just in  
case something got fixed ...

Sincerely -- Mark Salyzyn

On Jul 30, 2008, at 5:54 PM, Martin Samuelsson wrote:

> Hello list,
>
> I have an old Adaptec 2610SA SATA RAID controller with six disks. As  
> I'm a bit curious, I'd like to know, for example, the temperature  
> they report. (afacli can't report those, and I suspect aaccli can't  
> either) It seemed utterly impossible until I saw the  
> expose_physicals module option, but after switching that on, I can  
> at least see traces of the individual disks.
>
> If I understand it correctly, aacraid provides an emulation layer  
> between what I see and the physical disks, passing known commands  
> and responses back and forth. However, S.M.A.R.T commands doesn't  
> seem to be among those known ones, is that correct?
>
> I'm running CentOS 5 with kernel 2.6.18, which is kind of old. Would  
> running a spanking new kernel make me happier and support reading  
> the temperature from the individual disks?
>
> 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

Re: aacraid and S.M.A.R.T

[Martin Samuelsson]

On Wed, 30 Jul 2008 22:06:38 -0400
Mark Salyzyn <Mark_Salyzyn@adaptec.com> 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.

Ow, OK, that explains things.

> SMART was supposed to be emulated, but on that old card it was never  
> tested ... make sure you have the latest Firmware on the card just in  
> case something got fixed ...

I will. A slight problem is that the 2610SA is a card that seem to be a Dell exclusive thing, and impossible to find any information about on the Adaptec site. I'll try, and then I'll try at the Dell site, just in case.

Thanks for your help!

Regards,
/Sam

Re: aacraid and S.M.A.R.T

[Douglas Gilbert]

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?

"SAT 0.9 transport layer" does not correspond to any t10 numbering.
Is the "0.9" meant to imply that the implementation is just
shy of compliance to the SAT-1 standard? [Perhaps a version
descriptor in the INQUIRY response answers my question.]

Doug Gilbert


> SMART was supposed to be emulated, but on that old card it was never 
> tested ... make sure you have the latest Firmware on the card just in 
> case something got fixed ...
> 
> Sincerely -- Mark Salyzyn
> 
> On Jul 30, 2008, at 5:54 PM, Martin Samuelsson wrote:
> 
>> Hello list,
>>
>> I have an old Adaptec 2610SA SATA RAID controller with six disks. As 
>> I'm a bit curious, I'd like to know, for example, the temperature they 
>> report. (afacli can't report those, and I suspect aaccli can't either) 
>> It seemed utterly impossible until I saw the expose_physicals module 
>> option, but after switching that on, I can at least see traces of the 
>> individual disks.
>>
>> If I understand it correctly, aacraid provides an emulation layer 
>> between what I see and the physical disks, passing known commands and 
>> responses back and forth. However, S.M.A.R.T commands doesn't seem to 
>> be among those known ones, is that correct?
>>
>> I'm running CentOS 5 with kernel 2.6.18, which is kind of old. Would 
>> running a spanking new kernel make me happier and support reading the 
>> temperature from the individual disks?
>>
>> 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
> 
> 

Re: aacraid and S.M.A.R.T

[Mark Salyzyn]

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.

> "SAT 0.9 transport layer" does not correspond to any t10 numbering.
> Is the "0.9" meant to imply that the implementation is just
> shy of compliance to the SAT-1 standard? [Perhaps a version
> descriptor in the INQUIRY response answers my question.]

Yes, officially shy of compliance ... but unofficially enhanced when  
needed when compliance issues have come up (translation: 0.9+) in  
Adaptec or OEM Q/A. The team responsible for the SAT layer was VERY  
risk averse when it came to making any changes even when introducing a  
new released card, so this level is true of old and new cards today.

> Doug Gilbert

Sincerely -- Mark Salyzyn

FYI, my last day of in-office employment with Adaptec is August 8, aacraid@adaptec.com 
  for driver support will continue to be answered by the team (I may  
continue at my discretion or at the hands of my new employer <shrug>)

>> SMART was supposed to be emulated, but on that old card it was never
>> tested ... make sure you have the latest Firmware on the card just in
>> case something got fixed ...
>>
>> Sincerely -- Mark Salyzyn
>>
>> On Jul 30, 2008, at 5:54 PM, Martin Samuelsson wrote:
>>
>>> Hello list,
>>>
>>> I have an old Adaptec 2610SA SATA RAID controller with six disks. As
>>> I'm a bit curious, I'd like to know, for example, the temperature  
>>> they
>>> report. (afacli can't report those, and I suspect aaccli can't  
>>> either)
>>> It seemed utterly impossible until I saw the expose_physicals module
>>> option, but after switching that on, I can at least see traces of  
>>> the
>>> individual disks.
>>>
>>> If I understand it correctly, aacraid provides an emulation layer
>>> between what I see and the physical disks, passing known commands  
>>> and
>>> responses back and forth. However, S.M.A.R.T commands doesn't seem  
>>> to
>>> be among those known ones, is that correct?
>>>
>>> I'm running CentOS 5 with kernel 2.6.18, which is kind of old. Would
>>> running a spanking new kernel make me happier and support reading  
>>> the
>>> temperature from the individual disks?
>>>
>>> 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
>>
>>
>

Re: aacraid and S.M.A.R.T

[Martin Samuelsson]

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

Re: aacraid and S.M.A.R.T

[Mark Salyzyn]

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

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.

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

Re: aacraid and S.M.A.R.T

[Martin Samuelsson]

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

Re: aacraid and S.M.A.R.T

[Douglas Gilbert]

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?

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".

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
> 
> 

Re: aacraid and S.M.A.R.T

[Martin Samuelsson]

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