public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Wakko Warner <wakko@animx.eu.org>
Cc: Richard Scobie <richard@sauce.co.nz>, linux-scsi@vger.kernel.org
Subject: Re: mptsas problem
Date: Sun, 13 Apr 2008 12:37:43 -0500	[thread overview]
Message-ID: <1208108263.4707.37.camel@localhost.localdomain> (raw)
In-Reply-To: <20080413170644.GA1234@animx.eu.org>

On Sun, 2008-04-13 at 13:06 -0400, Wakko Warner wrote:
> > There's an easy way to verify:  smartctl -i will print the firmware
> > version string.
> 
> The aic sas one shows 3.AAE
> The lsi mptsas can't be queried:
> # smartctl -d scsi -i /dev/sdc
> smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
> 
> Serial number:             3QD076X8
> Device type: disk
> Local Time is: Sun Apr 13 13:02:36 2008 EDT
> Device supports SMART and is Enabled
> Temperature Warning Disabled or Not Supported
> #
> 
> I tried -d ata, -d sat and not using -d, provided no information.  -T
> permissive didn't work either.

That's a bit unfortunate ... it means the LSI firmware SAT layer doesn't
support ATA_16.  you can try ATA_12 just to make sure (little chance it
will work, but just in case):

smartctl -i -d sat,12 /dev/sd<x>

If that doesn't work, I'm afraid you'll need to transfer the drive to a
card that does support the command (like the aic).

However, it doesn't have to be a drive firmware fault, it could be some
type of corner case NCQ failure triggered by the NCQ handler inside the
LSI firmware ... in which case, your only hope for fixing it lies with
LSI.

There is one final thought:  the reason the aic94xx has a queue depth of
31 is because that's the maximum NCQ can support (well, it's 32 max, but
we need one command for error handling).  So, if the LSI shows a queue
depth of 64 it may be queueing internally as well.  You could try
lowering the lsi queue to 31 and seeing if it makes a difference.

James



  reply	other threads:[~2008-04-13 17:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06 23:40 mptsas problem Richard Scobie
2008-04-07  1:04 ` Wakko Warner
2008-04-13 13:00   ` Douglas Gilbert
2008-04-13 14:39     ` James Bottomley
2008-04-13 14:31   ` James Bottomley
2008-04-13 16:48     ` Wakko Warner
2008-04-13 16:58       ` James Bottomley
2008-04-13 17:06         ` Wakko Warner
2008-04-13 17:37           ` James Bottomley [this message]
2008-04-13 20:49             ` Wakko Warner
2008-04-14 18:16               ` Moore, Eric
2008-04-14 21:34                 ` Wakko Warner
2008-04-15 17:26                   ` Moore, Eric
2008-04-15 22:49                     ` Wakko Warner
2008-04-13 22:22             ` Douglas Gilbert
2008-04-13 23:51               ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2008-04-06 19:56 Wakko Warner
     [not found] ` <0631C836DBF79F42B5A60C8C8D4E8229F64FC1@NAMAIL2.ad.lsil.com>
2008-04-07  1:07   ` Wakko Warner
2008-04-07 11:36     ` Bernd Schubert
2008-04-07 15:16     ` Moore, Eric
2008-04-07 16:54       ` Wakko Warner

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=1208108263.4707.37.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=richard@sauce.co.nz \
    --cc=wakko@animx.eu.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