grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Neil Brown <neilb@suse.de>,
	The development of GNU GRUB <grub-devel@gnu.org>,
	John Sheu <john.sheu@gmail.com>,
	linux-raid@vger.kernel.org,
	Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Subject: Re: Software RAID and Fakeraid
Date: Tue, 1 Feb 2011 11:26:42 -0500	[thread overview]
Message-ID: <20110201162642.GU343@caffeine.csclub.uwaterloo.ca> (raw)
In-Reply-To: <4D47627A.1080509@cfl.rr.com>

On Mon, Jan 31, 2011 at 08:31:38PM -0500, Phillip Susi wrote:
> What do you mean help?

If the raid stores the raid info at the end, then the data starts at
sector 0.  So no space for a bootloader at all.

> It is left empty afaik, which is the whole point of shifting it over to 4kb.

Certainly makes sense.  Now is 4K enough for a boot loader?  Not sure.

> Obviously doing nothing is the simplest thing one can do.  Instead I  
> would like to do something and end up with a better, more functional  
> system.  Hence my suggestion on WHAT to do and the existence of this  
> entire thread.

I personally consider soft raid on raw devices so convluted that I
have never done it.  I would rather have something I know works with my
bootloader and other tools, than gain that extra 1MB (at most) that not
having partitions gives.  Also given many PCs won't boot from a drive
without a partition table, it isn't even an option then.

Really I think it comes down to only being able to handle the case
where there is a 4K gap, if you can fit grub in there in a format that
a system would be able to boot reading just sector 0 of the device.
The raid info at the start and raid info at the end both prevent you
from having any boot code in sector 0 so can't be supported at all.

-- 
Len Sorensen


  parent reply	other threads:[~2011-02-01 16:26 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 [this message]
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=20110201162642.GU343@caffeine.csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=grub-devel@gnu.org \
    --cc=john.sheu@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=psusi@cfl.rr.com \
    /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).