From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Software RAID and Fakeraid
Date: Sat, 25 Dec 2010 20:55:42 +0100 [thread overview]
Message-ID: <4D164C3E.9020509@gmail.com> (raw)
In-Reply-To: <AANLkTinhWh4FQ7q=Vkym_fd9aucXLMhgzgFuw23Z9o59@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]
On 11/25/2010 11:26 AM, John Sheu wrote:
> What's the preferred way to differentiate BIOS fakeraid from regular
> software mdraid?
>
> 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:
>
Right now GRUB2 is unable to distinguish between 2 cases. However you
can inform it that you have scamraid by adding following line to device.map:
(hd0) /dev/md0
> if (0 && dest_dev[0] == 'm' && dest_dev[1] == 'd'
> && ((dest_dev[2] >= '0' && dest_dev[2] <= '9') || dest_dev[2] == '/'))
> {
> char **devicelist;
> int i;
>
> devicelist = grub_util_raid_getmembers (dest_dev);
>
> for (i = 0; devicelist[i]; i++)
> {
> setup (arguments.dir ? : DEFAULT_DIRECTORY,
> arguments.boot_file ? : DEFAULT_BOOT_FILE,
> arguments.core_file ? : DEFAULT_CORE_FILE,
> root_dev, grub_util_get_grub_dev (devicelist[i]), 1,
> arguments.force, arguments.fs_probe);
> }
> }
>
> For a fakeraid setup, however, the BIOS presents the entire device as
> "regular" int13 device, so GRUB2 really should be installing it to the
> entire /dev/md### device, not the individual members.
>
> So what's the preferred way to differentiate BIOS fakeraid? Is there
> some ioctl that would make this easier than having to parse /proc/mdstat?
>
> Thanks,
> -John Sheu
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2010-12-25 19:55 UTC|newest]
Thread overview: 22+ 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
2010-11-30 22:25 ` Neil Brown
2010-12-02 22:13 ` Phillip Susi
2010-12-03 1:36 ` Neil Brown
2010-12-03 3:15 ` Phillip Susi
2010-12-08 22:43 ` Neil Brown
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 22:12 ` Lennart Sorensen
2011-02-01 1:31 ` Phillip Susi
2011-02-01 11:04 ` Michal Suchanek
2011-02-01 16:26 ` Lennart Sorensen
2011-02-02 0:08 ` Phillip Susi
2011-02-02 3:22 ` NeilBrown
2011-02-02 15:34 ` Phillip Susi
2011-02-02 16:09 ` hansbkk
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 [this message]
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=4D164C3E.9020509@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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).