Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Sean Bruno <sean.bruno@dsl-only.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-scsi@vger.kernel.org
Subject: Re: SMART Status Query
Date: Tue, 03 Feb 2009 06:22:56 -0800	[thread overview]
Message-ID: <1233670976.2065.1.camel@localhost.localdomain> (raw)
In-Reply-To: <4987FB23.7040600@s5r6.in-berlin.de>

On Tue, 2009-02-03 at 09:06 +0100, Stefan Richter wrote:
> (Cc'd LSML in case I write nonsense)
> 
> Sean Bruno wrote:
> > Out of curiosity, I tried to query the smart status from disks in a
> > FW400 enclosure.  I was prompted that the drives do not support SMART.
> > 
> > The Seagates in the enclosure do indeed support SMART and I suppose that
> > there is a missing bit in the firewire stack or in my enclosure that
> > would allow these commands to be passed down to the disks.
> > 
> > Does this situation have a resolution?  Is there a way around it?
> > 
> > I do find it interesting, that the the actual disk information is
> > returned and not the "spoofed" enclosure disk names.
> > 
> > I tried "smartctl -a /dev/sdd" and was presented with:
> > [sean@home-desk ~]$ sudo smartctl -a /dev/sdc
> > smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8
> > Bruce Allen
> > Home page is http://smartmontools.sourceforge.net/
> > 
> > Device: ST380811 AS               Version: 3.AA
> > Serial number:             5PS13NWB
> > Device type: disk
> > Local Time is: Mon Feb  2 22:36:07 2009 PST
> > Device does not support SMART
> > 
> > Error Counter logging not supported
> > Device does not support Self Test logging
> 
> AFAIK SMART requires "ATA pass-through", i.e. the tunneling of ATA
> commands through SCSI.
> 
> The FireWire drivers happily send any command to the target which the
> Linux kernel or an application emits.  The missing piece here is ATA
> pass-through support in the firmware of the FireWire-to-SATA bridge chip
> of the drive enclosure.
> 
> I have not yet heard of FireWire-to-SATA bridges which do support ATA
> pass-through.

That makes sense, unfortunate, but not unexpected.

Can you tell me how my system is getting the Seagate drive information
then?  I've looked over the data available to me on the Firewire bus,
and don't see where it's being pulled from.

Sean


  reply	other threads:[~2009-02-03 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1233643011.8067.21.camel@localhost.localdomain>
2009-02-03  8:06 ` SMART Status Query Stefan Richter
2009-02-03 14:22   ` Sean Bruno [this message]
2009-02-03 16:04     ` Stefan Richter

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=1233670976.2065.1.camel@localhost.localdomain \
    --to=sean.bruno@dsl-only.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /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