public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Ransom <ransom@cfa.harvard.edu>
To: linux-kernel@vger.kernel.org, Scott Ransom <ransom@cfa.harvard.edu>
Subject: 3ware Escalade problems
Date: Wed, 01 Aug 2001 14:14:44 -0400	[thread overview]
Message-ID: <3B684714.32F6A02F@cfa.harvard.edu> (raw)

Hello,

After months of running a fileserver with an 8 port 3ware escalade card
(kernels 2.4.[3457] using reiserfs and software RAID5) I started getting
problems this weekend.

Over the last three days, when I try to access the drives, after a
couple minutes I get a drive failure (I even heard a "yelp" from the
drive during one of them...).  But the "failure" has happened to 3 of
the 8 drives over 3 days -- so unless there is a hardware problem that
is killing my drives I find it hard to believe that 3 drives really and
truly failed....

Here is a sample from my syslog of a failure:

3w-xxxx: tw_interrupt(): Bad response, status = 0xc7, flags = 0x51, unit
= 0x1.
3w-xxxx: tw_scsi_eh_reset(): Reset succeeded for card 1.
3w-xxxx: tw_interrupt(): Bad response, status = 0xc7, flags = 0x51, unit
= 0x1.
scsi: device set offline - not ready or command retry failed after host
reset: host 1 channel 0 id 1 lun 0
SCSI disk error : host 1 channel 0 id 1 lun 0 return code = 80000
I/O error: dev 08:11, sector 158441712

I've noticed several "issues" with the 3ware cards in the archives.  Has
anyone seen something like this?

Scott

PS:  I'm currently running 2.4.7 with the lm-sensors/i2c patches.

-- 
Scott M. Ransom                   Address:  Harvard-Smithsonian CfA
Phone:  (617) 496-7908                      60 Garden St.  MS 10 
email:  ransom@cfa.harvard.edu              Cambridge, MA  02138
GPG Fingerprint: 06A9 9553 78BE 16DB 407B  FFCA 9BFA B6FF FFD3 2989

             reply	other threads:[~2001-08-01 18:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 18:14 Scott Ransom [this message]
2001-08-01 21:39 ` 3ware Escalade problems Jeff V. Merkey
2001-08-02  0:26   ` Alan Cox
2001-08-02  1:40     ` Jeff V. Merkey
2001-08-02  0:40       ` Alan Cox
2001-08-02  1:58         ` Jeff V. Merkey
2001-08-02 12:22           ` Alan Cox
2001-08-02 21:26             ` Jeff V. Merkey
2001-08-02 22:02               ` Jeff V. Merkey
2001-08-02 14:19   ` 3ware Escalade problems? Adaptec? Michael Rothwell
     [not found] <53B208BD9A7FD311881A009027B6BBFB9EADC7@siamese>
2001-08-01 18:51 ` 3ware Escalade problems Scott Ransom
     [not found] <53B208BD9A7FD311881A009027B6BBFB9EADCC@siamese>
2001-08-02  1:38 ` Jeff V. Merkey

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=3B684714.32F6A02F@cfa.harvard.edu \
    --to=ransom@cfa.harvard.edu \
    --cc=linux-kernel@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