From: Michael Tokarev <mjt@tls.msk.ru>
To: Christian Kivalo <valo@valo.at>
Cc: linux-raid@vger.kernel.org
Subject: Re: Best Practice for Raid1 Root
Date: Thu, 15 Jan 2004 03:32:12 +0300 [thread overview]
Message-ID: <4005DF8C.7080206@tls.msk.ru> (raw)
In-Reply-To: <NMEHJKFGFEGJPIPOLFFECEMHDEAA.valo@valo.at>
Christian Kivalo wrote:
>>Hi,
>>
>
> [snip]
>
>>The boot loader is grub and I want both /boot and / raided.
>>
>>In the event of a failure of hda I would like the system to switch to
>>hdc. This works fine. However what I have had problems with is if the
>>system reboots. If /dev/hda is unavailable I no longer have a disk with
>>a boot sector set up correctly. Unless I have a floppy or CDROM with a
>>boot loader the system will not come up.
[]
> one possible solution would be to use lilo. lilo is capable of booting
> from md raid1 arrays. look at lilo.conf(5) manpage for 'raid-extra-boot'
> in 'GLOBAL OPTIONS'. i use it on most of my maschines. AFAIK grub is not
> able to boot from /dev/mdX.
When using raid-extra-boot, lilo treats second disk as bios #0x81,
3rd disk as bios #0x82 and so on. That to say - if your first disk
fails and BIOS will substitute second disk in place of first, making
it 0x80 instead of 0x81, lilo will not boot too, exactly in a way
why grub installed into /dev/hdb (that was e.g. temporarily plugged
into another machine just to make it bootable etc) does not want to
boot from it when it will be /dev/hda again (when returned back into
it's own machine).
Instead of using raid-extra-boot, IMHO, it is more safe to install
lilo into the raid array instead of the MBR, and use standard MBR
to boot from active partition. But granted, lilo's raid-extra-boot
will work around different disk layouts, while lilo on raid with
standard MBR will not.
/mjt
next prev parent reply other threads:[~2004-01-15 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 23:43 Best Practice for Raid1 Root Terrence Martin
2004-01-15 0:06 ` Christian Kivalo
2004-01-15 0:32 ` Michael Tokarev [this message]
2004-01-15 12:48 ` Luca Berra
2004-01-15 0:26 ` Michael Tokarev
2004-01-15 0:59 ` Terrence Martin
2004-01-15 1:22 ` Terrence Martin
2004-01-15 8:42 ` Gordon Henderson
2004-01-18 21:58 ` Frank van Maarseveen
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=4005DF8C.7080206@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-raid@vger.kernel.org \
--cc=valo@valo.at \
/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.