From: James Bottomley <James.Bottomley@steeleye.com>
To: Ross Macintyre <raz@macs.hw.ac.uk>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
ian@eclipsecomputing.co.uk, cos@vger.kernel.org
Subject: Re: interpreting scsi errors (RAID)
Date: 09 Feb 2004 10:35:05 -0500 [thread overview]
Message-ID: <1076340906.2090.3.camel@mulgrave> (raw)
In-Reply-To: <2198.137.195.14.4.1076324273.squirrel@www.macs.hw.ac.uk>
On Mon, 2004-02-09 at 05:57, Ross Macintyre wrote:
> I have seen this error twice now:
>
> Adapter 1 Channel 1 Target 2: Sense Data: errCode=0x71 valBit=1
> segMent=0x00 SenseKey=4 ILI=0 EOM=0 FMRK=0 Address=0x00005A8E
> ASL=0xA cmdSpec=0x0000 ASC=0x0C ASCQ=0x00 FRUC Code + Sense Key
> Specific=0x8001
That's a non recoverable write error.
> I have an LSILogic Megaraid SCSI 320-1, running RAID level5, 4 disks, and
> the OS is RedHat8.0.
>
> What I would like, is to be able to understand these messages.
> In particular I need to know if there is a hardware error which means that
> I can contact the retailer, in confidence, and ask for a replacement, as
> the disk is still under warranty.
> Any pointers at FAQs or READMEs greatly appreciated,
All the sense codes are documented in the current SCSI Primary Commands
document at the t10 webiste
http://www.t10.org/ftp/t10/drafts/spc3/spc3r17.pdf
Although the pointer will change as the standard is revised.
James
next prev parent reply other threads:[~2004-02-09 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 10:57 interpreting scsi errors (RAID) Ross Macintyre
2004-02-09 15:35 ` James Bottomley [this message]
2004-02-09 16:19 ` Ross Macintyre
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=1076340906.2090.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=cos@vger.kernel.org \
--cc=ian@eclipsecomputing.co.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=raz@macs.hw.ac.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.