linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonio Perez <ap23563m@gmx.com>
To: linux-raid@vger.kernel.org
Subject: Re: About seting up Raid5 on a four disk box.
Date: Wed, 14 Oct 2009 08:55:38 -0400	[thread overview]
Message-ID: <hb4hob$cg8$2@ger.gmane.org> (raw)
In-Reply-To: 20091014085606.GA13917@cthulhu.home.robinhill.me.uk

Robin Hill wrote:

> On Wed Oct 14, 2009 at 03:45:21AM -0400, Antonio Perez wrote:
> 
>> Robin Hill wrote:
[snip]
 
>> Is this assumption correct?
>> 
> Yes - anything that falls within the blocks covered by the array will
> get replicated, so "Area 2" will automatically get taken care of (you'll
> have to make sure the RAID metadata version is chosen correctly so as
> not to conflict though - 1.1/1.2 metadata may overlap with the area used
> by grub here).

Thanks. Yes, I am aware of the conflicts between metadata 1.x and grub. 
 
> As for "Area 1" - from what you've written (and reading the grub
> internals documentation), I can only assume you're referring to the
> stage1.5 bootloader (unless you're using grub2?).  This can live on the
> file system (I don't see anything obvious in the documentation about how
> you set where it goes - the documentation seems to suggest that the file
> system is the default), so so there may well be no need to do anything
> about this (other than the MBR itself).

I do use Grub2, but both gub-legacy and grub2 now do use the disk sectors 
following the MBR to embed the boot code.

Looking at:	http://thestarman.pcministry.com/asm/mbr/GRUB.htm

the pointer at 0x7C44 (disk offset 0x0044) is the sector which is to be 
loaded next. It is usually 0x0001, which means simply the next sector.

I'll look at the grub-source later, but I am pretty sure that is the case.

>> >> 2.- Is there a recomended way to trigger the said copy of question 2?
>> >> Where should a call to copy the MBR should be placed? On update-grub?
>> 
>> > I always just rerun the grub install for each disk manually (see
>>http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/008898.html
>> > for example).
>> 
>> That's the usual procedure on a first install, correct.
>> 
> It's what I do every update - it's a quick enough process, and grub
> updates aren't very common (all the development's on grub2 now).

Thanks, Robin

-- 
Antonio Perez


  reply	other threads:[~2009-10-14 12:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 13:13 About seting up Raid5 on a four disk box Antonio Perez
2009-10-13 14:04 ` Majed B.
2009-10-13 14:52   ` Antonio Perez
2009-10-13 15:10     ` Majed B.
2009-10-14  6:23       ` Antonio Perez
2009-10-14  6:40         ` Majed B.
2009-10-14 12:53           ` Antonio Perez
2009-10-14 13:41             ` Majed B.
2009-10-14 14:53               ` Antonio Perez
2009-10-14 21:08                 ` Bill Davidsen
2009-10-13 15:23 ` Robin Hill
2009-10-14  7:45   ` Antonio Perez
2009-10-14  8:56     ` Robin Hill
2009-10-14 12:55       ` Antonio Perez [this message]
2009-10-13 20:54 ` Bill Davidsen
2009-10-14  7:49   ` Antonio Perez

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='hb4hob$cg8$2@ger.gmane.org' \
    --to=ap23563m@gmx.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 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).