From: Jarrod Johnson <jarrod.b.johnson@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Problems w/ RAID-5/sata_promise/PDC20579
Date: Tue, 19 Jul 2005 00:58:41 -0400 [thread overview]
Message-ID: <fab4e42a050718215857958bc4@mail.gmail.com> (raw)
I have a Soltek planar with this controller providing two ports.
As I try to use those ports together with two non-pdc attached sata
drives for software raid, the devices hanging off of the PDC
controller frequently become unresponive, throwing I/O errors on every
attempt to read a sector after a timeout.
Don't have the exact error in front of me, but essentially, it gets
command timeout,
then every command to the controller seems to give the same, status of
0xff busy, but not much more informative output.
The situation seems very similar to Jim Ramsays:
http://www.opensubscriber.com/message/linux-ide@vger.kernel.org/1671725.html
Output seems to line up pretty much exactly, except specific sector
numbers, of course.
next reply other threads:[~2005-07-19 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 4:58 Jarrod Johnson [this message]
2005-07-22 1:23 ` Problems w/ RAID-5/sata_promise/PDC20579 Jarrod Johnson
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=fab4e42a050718215857958bc4@mail.gmail.com \
--to=jarrod.b.johnson@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).