From: Travis Morgan <lkml@bigfiber.net>
To: linux-kernel@vger.kernel.org
Subject: Promise PDC 20376 and 2.6.1
Date: Thu, 15 Jan 2004 14:07:29 -0700 [thread overview]
Message-ID: <1074200848.5941.44.camel@castle.bigfiber.net> (raw)
I've been using the SATA drivers with my MSI motherboard and Promise PDC
20376 controller for some time now. I finally decided, having two
identical Seagate Barracuda drives, that I wanted to RAID them and use
them as my system drive.
I created a striped array within the controller's BIOS and it says that
the array is active and healthy.
When I get into Linux it still has two seperate devices.
lr-xr-xr-x 1 root root 33 Jan 15 07:14 /dev/sda ->
scsi/host0/bus0/target0/lun0/disc
lr-xr-xr-x 1 root root 33 Jan 15 07:14 /dev/sdb ->
scsi/host1/bus0/target0/lun0/disc
Should it not have just /dev/sda now? Or does the driver for this
controller not support RAID? I searched the mailing list archives and
tried to find something about it in the Documentation but wasn't able to
find out either way. If not, are there plans for this? Or is it an issue
with Promise IP still?
They are 160 gig drives. I take it they use 512 block sizes.
[02:04:15]<root@castle:~> cat /sys/block/sd[ab]/size
312581808
312581808
And if I try to fdisk one it says 160 gigs.
00:0d.0 RAID bus controller: Promise Technology, Inc. PDC20376 (rev 02)
Subsystem: Promise Technology, Inc.: Unknown device 6620
Flags: bus master, 66Mhz, medium devsel, latency 96, IRQ 19
I/O ports at e800 [size=64]
I/O ports at e400 [size=16]
I/O ports at e000 [size=128]
Memory at dfffe000 (32-bit, non-prefetchable) [size=4K]
Memory at dffc0000 (32-bit, non-prefetchable) [size=128K]
Capabilities: [60] Power Management version 2
Regards,
Travis M
reply other threads:[~2004-01-15 21:16 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=1074200848.5941.44.camel@castle.bigfiber.net \
--to=lkml@bigfiber.net \
--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
all inboxes | Powered by JetHome®