From: Nick Clark <Nick.Clark@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: IDE drive status error 0x058 under load
Date: Sat, 24 Mar 2001 11:00:38 +0000 [thread overview]
Message-ID: <3ABC7E56.2040003@bigfoot.com> (raw)
Hey. Using Kernel 2.2.18 + E-IDE patches Rev 6.30 + Raid patches
Putting together a fileserver setup with two mirrored FSs over four
disks & two IDE controllers (ie each disk on controller 1 is mirrored to
a second on Controller 2, using raid 1).
No problems accessing disks separately, can create FS on each Ok with
out errors. Can build each raid pair separately with no errors.
But when attempting to build raid devices on all four disks at the same
time get many of these
Mar 22 15:41:11 uther kernel: hdk: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Mar 22 15:41:11 uther kernel: hdk: drive not ready for command
.. from all four disks. Also get these when attempting mke2fs on all
disks at the same time (no raid).
Im guessing (probably incorrectly) that this is a warning message only &
that I can ignore them; can anyone confirm / deny that for me? Got a bit
out of my depth with this..
Hardware is
ABit VP6 M/B, 2x1Ghz PIII, 512MB
2x Promise ultra100 PCI IDE controllers with 4x IBM-DTLA-307075 73Gb Drives
3Com 3C980 NIC
5th IBM-DTLA-307075 as root disk (no mirror), on M/B IDE controller.
Onboard 'raid' controler disabled in bios.
Software is
RedHat 7.01 distribution
Kernel 2.2.18 + E-IDE patches Rev 6.30 + Raid patches
(also tried with 2.4.2 + E-IDE patches Rev 6.31, same problem)
... let me know if there is any other info I can give you. Thanx,
Nick.
--
Nick Clark is now --> Nick.Clark@Bigfoot.com <-- Thanking you.
reply other threads:[~2001-03-24 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ABC7E56.2040003@bigfoot.com \
--to=nick.clark@bigfoot.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