From: Terrence Martin <tmartin@physics.ucsd.edu>
To: linux-raid@vger.kernel.org
Subject: Best Practice for Raid1 Root
Date: Wed, 14 Jan 2004 15:43:04 -0800 [thread overview]
Message-ID: <4005D408.8060002@physics.ucsd.edu> (raw)
Hi,
I wanted to post this question for a while.
On several systems I have configured a root software raid setup with two
IDE hard drives. The systems are always some version of redhat. Each
disk has its own controller and is partitioned similar to the following,
maybe with more partitions, but this is the minimum.
hda1 fd 100M
hda2 swap 1024M
hda3 fd 10G
hdc1 fd 100M
hdc2 swap 1024M
hdc3 fd 10G
The Raid devices would be
/dev/md0 mounted under /boot made of /dev/hda1 and /dev/hdc1
/dev/md1 mounted under / made of /dev/hda3 and /dev/hdc3
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.
So my main question is what is the best practice to get a workable boot
sector on /dev/hdc? How are other people making sure that their system
remains bootable after a disk failure of the boot disk? Is it even
possible with software raid and PC BIOS? Also when you replace /dev/hda
how are you getting a valid boot sector on that disk?
I have found grub to often be problematic so that even when I move the
good drive to be hda grub does not like to install itself correctly.
I am sure I am approaching this incorrect in some way, I am just not
sure what is the right way.
Terrence Martin
UCSD Physics
next reply other threads:[~2004-01-14 23:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 23:43 Terrence Martin [this message]
2004-01-15 0:06 ` Best Practice for Raid1 Root Christian Kivalo
2004-01-15 0:32 ` Michael Tokarev
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=4005D408.8060002@physics.ucsd.edu \
--to=tmartin@physics.ucsd.edu \
--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).