From: Jeff Garzik <jgarzik@pobox.com>
To: Daniel Kirkegaard Mouritsen <daniel@mouritsen.info>
Cc: linux-raid@vger.kernel.org
Subject: Re: SATA raid options..
Date: Sat, 03 Jul 2004 13:05:05 -0400 [thread overview]
Message-ID: <40E6E741.9090800@pobox.com> (raw)
In-Reply-To: <1088865298.4974.67.camel@faetterbox.faetter.net>
Daniel Kirkegaard Mouritsen wrote:
> I own a Gigabyte GA-8KNXP motherboard, which has 4 serial-ata ports. Two
> of which features RAID functionality.
>
> The serial-ata controller on the motherboard is a Silicon Image 3112A (a
> chip which i haven't been able to find much information about,
> siimage.com doesn't even list it as a product).
>
> I'll soon get a new sata disk(identical to my current disk), and I would
> love to be able to do the following:
>
> * keep using a 2.6.* kernel
> * Use the RAID BIOS administration interface to stripe/administer the
> disks
> * Have both my grub, /boot / and a NTFS-windows partition reside on
> striped set.
>
> Is this at all possible? Can GRUB detect devices created with the
> on-board BIOS assisted raid?
>
> Another thing, I'm getting severely confused what I'm supposed to use as
> a driver for the thing. ATM I found: udev+raiddetect or the
> not-yet-released(or is it? maybe its just me who cant find it :]) dmraid
> is the way to go. Does these both use the device-mapper tool? And can
> anybody tell me if dmraid is 2 or 20 months aways?
dmraid will be required for use, and its 2-4 months away, I would guess.
Why not just use md raid? BIOS RAID is _always_ crap.
Jeff
next prev parent reply other threads:[~2004-07-03 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 14:34 SATA raid options Daniel Kirkegaard Mouritsen
2004-07-03 17:05 ` Jeff Garzik [this message]
2004-07-04 3:55 ` Ricky Beam
2004-07-03 17:36 ` John Lange
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=40E6E741.9090800@pobox.com \
--to=jgarzik@pobox.com \
--cc=daniel@mouritsen.info \
--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).