From: Larry McVoy <lm@bitmover.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: IDE wierdness
Date: Wed, 20 Aug 2003 08:09:03 -0700 [thread overview]
Message-ID: <20030820150903.GA7246@work.bitmover.com> (raw)
The primary drive in our file server started to flake out on us (caught by
the integrity checker we use as part of our backups, files that hadn't been
modified in a couple of years started having different CRC's). I pulled
the data off and stuck in a new drive.
I wanted to see if the old drive could be salvaged and used as a test box
drive. The drive seems to be degenerating fast. When I put that drive
in a 3ware card the 3ware card only sees 1/3 of the drives. Strange.
When I put all 3 drives in a promise card, it sees them but if I try and
copy data from the bad drive to any other drive the system locks up hard,
no console, no pings, no response to the reset switch, it takes a power
cycle to get things back.
I verified that behaviour on two different systems so it isn't the box.
I also cycled through 3 different 3ware cards to make sure that wasn't
the problem (isn't sys admin fun?).
It's clear to me that I don't want to use this drive but I'm wondering if
there is any interest in debugging the lock up. I've only done it on
2.4.18 as shipped by redhat but I could try 2.6 or whatever you like.
If the concensus is that it is OK that bad hardware locks you up then I'll
toss the drive and move on.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next reply other threads:[~2003-08-20 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 15:09 Larry McVoy [this message]
2003-08-20 15:40 ` IDE wierdness Jeff Garzik
2003-08-20 15:40 ` Alan Cox
2003-08-29 16:15 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2003-08-20 17:03 John Bradford
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=20030820150903.GA7246@work.bitmover.com \
--to=lm@bitmover.com \
--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