From: Phillip Susi <psusi@cfl.rr.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: linux-raid@vger.kernel.org, John Sheu <john.sheu@gmail.com>
Subject: Re: Software RAID and Fakeraid
Date: Tue, 30 Nov 2010 14:54:40 -0500 [thread overview]
Message-ID: <4CF55680.5010703@cfl.rr.com> (raw)
In-Reply-To: <AANLkTinhWh4FQ7q=Vkym_fd9aucXLMhgzgFuw23Z9o59@mail.gmail.com>
On 11/25/2010 5:26 AM, John Sheu wrote:
> What's the preferred way to differentiate BIOS fakeraid from regular
> software mdraid?
The only way I know of is detecting that it is a dmraid device as
opposed to md, which is why grub does it that way. This worked well in
the past when each tool exclusively handled one type of raid.
> I ask this as I'm booting with GRUB2 off a system that has one of those
> Intel fakeraid chipsets. As of a few months ago, the mdadm package has
> supported these fakeraid setups, so the RAID array comes up as a /dev/md###
> device. This is unfortunate, as GRUB2 assumes that any device of the type
> /dev/md### must be a pure software RAID device, and in
> util/grub-setup.c:939, tries to install itself to the RAID members
> individually:
For grub to support fakeraids activated by the md driver, it needs some
way to find out that it is actually a fake raid, and not a software
raid. Adding linux-raid to Cc list to see if they can suggest a way of
doing that.
WARNING: multiple messages have this Message-ID (diff)
From: Phillip Susi <psusi@cfl.rr.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: John Sheu <john.sheu@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Software RAID and Fakeraid
Date: Tue, 30 Nov 2010 14:54:40 -0500 [thread overview]
Message-ID: <4CF55680.5010703@cfl.rr.com> (raw)
In-Reply-To: <AANLkTinhWh4FQ7q=Vkym_fd9aucXLMhgzgFuw23Z9o59@mail.gmail.com>
On 11/25/2010 5:26 AM, John Sheu wrote:
> What's the preferred way to differentiate BIOS fakeraid from regular
> software mdraid?
The only way I know of is detecting that it is a dmraid device as
opposed to md, which is why grub does it that way. This worked well in
the past when each tool exclusively handled one type of raid.
> I ask this as I'm booting with GRUB2 off a system that has one of those
> Intel fakeraid chipsets. As of a few months ago, the mdadm package has
> supported these fakeraid setups, so the RAID array comes up as a /dev/md###
> device. This is unfortunate, as GRUB2 assumes that any device of the type
> /dev/md### must be a pure software RAID device, and in
> util/grub-setup.c:939, tries to install itself to the RAID members
> individually:
For grub to support fakeraids activated by the md driver, it needs some
way to find out that it is actually a fake raid, and not a software
raid. Adding linux-raid to Cc list to see if they can suggest a way of
doing that.
next prev parent reply other threads:[~2010-12-01 3:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 10:26 Software RAID and Fakeraid John Sheu
2010-11-30 19:54 ` Phillip Susi [this message]
2010-11-30 19:54 ` Phillip Susi
2010-11-30 22:25 ` Neil Brown
2010-11-30 22:25 ` Neil Brown
2010-12-02 22:13 ` Phillip Susi
2010-12-02 22:13 ` Phillip Susi
2010-12-03 1:36 ` Neil Brown
2010-12-03 1:36 ` Neil Brown
2010-12-03 3:15 ` Phillip Susi
2010-12-08 22:43 ` Neil Brown
2010-12-08 22:43 ` Neil Brown
2010-12-09 19:48 ` Phillip Susi
2010-12-09 19:48 ` Phillip Susi
2011-01-31 16:44 ` Phillip Susi
2011-01-31 17:03 ` Lennart Sorensen
2011-01-31 19:21 ` Phillip Susi
2011-01-31 19:21 ` Phillip Susi
2011-01-31 22:12 ` Lennart Sorensen
2011-02-01 1:31 ` Phillip Susi
2011-02-01 1:31 ` Phillip Susi
2011-02-01 11:04 ` Michal Suchanek
2011-02-01 11:04 ` Michal Suchanek
2011-02-01 16:26 ` Lennart Sorensen
2011-02-01 16:26 ` Lennart Sorensen
2011-02-02 0:08 ` Phillip Susi
2011-02-02 0:08 ` Phillip Susi
2011-02-02 3:22 ` NeilBrown
2011-02-02 3:22 ` NeilBrown
2011-02-02 15:34 ` Phillip Susi
2011-02-02 15:34 ` Phillip Susi
2011-02-02 16:09 ` hansbkk
2011-02-02 16:09 ` hansbkk
2011-02-02 21:12 ` Leslie Rhorer
2010-12-04 4:34 ` Leslie Rhorer
2010-12-07 17:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-25 19:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4CF55680.5010703@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=grub-devel@gnu.org \
--cc=john.sheu@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.