From: "Cuenta de la lista de linux" <user_linux@citma.cu>
To: linux-raid lists <linux-raid@vger.kernel.org>
Subject: Promise SX6000 RAID problems
Date: Thu, 30 Jan 2003 16:31:13 -0500 [thread overview]
Message-ID: <20030130213113.M55931@webmail.citma.cu> (raw)
Hi,
I have installed Red Hat 7.2 (kernel 2.4.7-10) in a dual PII server.I want to
install a Promise SX600 card on it.I have made a 5 drive RAID 5
I have let the card initialize by it's BIOs and i have choose OS=other in the
card setup, compiled the kernel with i20 support on it(as module), but when i
tried to format de array with fdisk /dev/i2o/hda i got a unable to open messages.
I have the system in another hard drive in /dev/hda.
Is ther any problems with i20 and Red Hat 7.2 kernel 2.4.7-10?
Should I upgrade the kernel ? but Which kernel version is the best for
Promise SX6000?
Has any one got this card to work with and distro/kernel version???
is this card able to use the i20 kernel module?
Thanks for any help
David
reply other threads:[~2003-01-30 21:31 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=20030130213113.M55931@webmail.citma.cu \
--to=user_linux@citma.cu \
--cc=linux-raid@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).