linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Pim Zandbergen <P.Zandbergen@macroscoop.nl>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SMART support for SATA drives in SAS enclosures
Date: Wed, 23 May 2007 15:49:23 -0400	[thread overview]
Message-ID: <46549AC3.4090105@torque.net> (raw)
In-Reply-To: <46488711.9020903@macroscoop.nl>

Pim Zandbergen wrote:
> Is SMART support available for SATA drives in SAS enclosures?
> 
> I'm testing this setup
> 
> LSI Logic SAS3800X PCI-X SAS controller (mptsas driver)
> Promise V-Trak J300S SAS/SATA enclosure/expander
> 12x Seagate ST3500630NS
> Linux kernel 2.6.21.1 x86_64
> smartmontools-5.37-1.1.fc6 from Fedora Core 6
> 
> "smartctl -i -d sat /dev/sdc" gives me
> 
> Smartctl: Device Read Identity Failed

I presume /dev/sdc is an actual disk rather than a
RAID device made up of several disks. The SAT standard
(and smartmontools) don't have a general way of
addressing individual disks behind RAID infrastructure.

For recent versions of smartmontools version 5.37 and
MPT Fusion SAS HBAs this should work if /dev/sdc is
a SATA disk. Your HBA may need a firmware upgrade.


You might fetch sg3_utils version 1.24 and try:
  sg_sat_identify /dev/sdc
That needs to work before smartctl has a hope.

> Same with "-d ata".
> 
> If I treat the disk as SCSI ("-d scsi"), the command
> will not fail, but wil only retrieve the serial number.

With MPT Fusion SAS hardware (that I have seen) the SAT
layer is in the HBA firmware. Only later versions of the
firmware support the SCSI ATA PASS-THROUGH command.

Doug Gilbert


  reply	other threads:[~2007-05-23 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 15:58 SMART support for SATA drives in SAS enclosures Pim Zandbergen
2007-05-23 19:49 ` Douglas Gilbert [this message]
2007-05-24 11:17   ` Pim Zandbergen
2007-05-30 11:49   ` Pim Zandbergen

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=46549AC3.4090105@torque.net \
    --to=dougg@torque.net \
    --cc=P.Zandbergen@macroscoop.nl \
    --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;
as well as URLs for NNTP newsgroup(s).