From: Phillip Susi <psusi@cfl.rr.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org, John Sheu <john.sheu@gmail.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Subject: Re: Software RAID and Fakeraid
Date: Mon, 31 Jan 2011 14:21:51 -0500 [thread overview]
Message-ID: <4D470BCF.20508@cfl.rr.com> (raw)
In-Reply-To: <20110131170349.GR343@caffeine.csclub.uwaterloo.ca>
On 1/31/2011 12:03 PM, Lennart Sorensen wrote:
> If you do software md raid on whole disks, I am not even sure if the
> BIOS could boot from that, since there won't be a partition table, no
> partition marked bootable (which some BIOSs requrie), sector 0 may not
> even contain boot code. Not sure there is anyway whole device software
> raid makes sense for a bootable drive at all. It makes sense for data
> drives perhaps. I just don't see this as a candidate for booting at all.
That is why I asked what the partition table should look like. When
grub is installed there will be one ( and boot code ), the question is
whether it should be empty, or have a protective partition that claims
the entire disk, like EFI does.
Normally with format 0.9, the raid array starts on sector 0, so the same
MBR appears both at the start of the first physical disk, and at the
start of the array. This is not possible with 1.1 or 1.2, so where do
they start the array? I must be at some point further away from sector
0, leaving room for a protective MBR on the component disks that would
be entirely separate from any MBR inside the array. This leaves room
for grub to be installed on each component disk, rather than only the
first. It also means that it is incompatible with formats 0.9, 1.1, and
possibly 1.0, depending on whether it includes the first sector in the
array like 0.9 does.
next prev parent reply other threads:[~2011-01-31 19:21 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 [this message]
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
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=4D470BCF.20508@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=grub-devel@gnu.org \
--cc=john.sheu@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=neilb@suse.de \
/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).