From: Michael Tokarev <mjt@tls.msk.ru>
To: "Cress, Andrew R" <andrew.r.cress@intel.com>
Cc: donj@asaca.com, linux-raid@vger.kernel.org
Subject: Re: Booting from a raid1 device ?
Date: Thu, 30 Oct 2003 03:54:48 +0300 [thread overview]
Message-ID: <3FA06158.9040007@tls.msk.ru> (raw)
In-Reply-To: <E5DA6395B8F9614EB7A784D628184B200E33DE@hdsmsx402.hd.intel.com>
Cress, Andrew R wrote:
> Don,
>
> Yes, it certainly can be done. I do it all the time.
>
> It's not hard with lilo, but grub doesn't support raid/md boot devices
> yet. This means that the grub boot record doesn't automatically get
> written to the second disk. In short, choose lilo for root mirroring if
> possible.
Ugh-blah. Excuse me folks, but.. maybe someone will be able to
answer this one:
why the hell a boot loader should "mirror" anything to the second disk? :)
That is. Place standard MBR into the boot sector. An MBR that will boot
from active partition. Be it e.g. /dev/hda and /dev/hdb. Create raid1
device from /dev/hda1 and /dev/hdb1. Mark both partitions as active.
And install whatever boot loader you want into /dev/md1 - it will be
mirrored automatically to /dev/hda1 and /dev/hdb1 (and to whatever else
disks you'll use).
Should your first disk fail, the system will either not boot because
of bios limitations, or bios may "remap" /dev/hdb into /dev/hda (to
be 0x80), and in this case boot procedure will work.
Well, ok, a boot loader should be able to determine real offsets from
the start of the disk, not from the start of raid device. I don't
know whenever grub can do that - lilo apparently does, as all our
systems are set up exactly this way...
/mjt
next prev parent reply other threads:[~2003-10-30 0:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 21:14 Booting from a raid1 device ? Cress, Andrew R
2003-10-30 0:54 ` Michael Tokarev [this message]
2003-10-30 10:00 ` Lars Marowsky-Bree
2003-10-31 8:28 ` Luca Berra
2003-10-31 17:40 ` Bill Rugolsky Jr.
-- strict thread matches above, loose matches on Subject: below --
2003-10-30 15:22 Cress, Andrew R
2003-10-30 14:11 Cress, Andrew R
2003-10-30 14:26 ` Michael Tokarev
2003-10-29 15:50 Cress, Andrew R
2003-10-31 14:41 ` Eric Wood
2003-10-27 15:25 Don Jessup
2003-10-27 15:37 ` Gordon Henderson
2003-10-27 16:00 ` Paul Clements
2003-10-27 22:11 ` Hermann Himmelbauer
2003-10-27 23:02 ` maarten van den Berg
2003-10-28 10:56 ` Lars Marowsky-Bree
2003-10-28 16:23 ` Michael
2003-10-28 20:31 ` Sandro Dentella
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=3FA06158.9040007@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=andrew.r.cress@intel.com \
--cc=donj@asaca.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.