CentOS - Apr 2005 - MIrrored drives won't boot after installation

I have a p4 motherboard with 2 ide interfaces, I connect 2 40 GB drives as
hda and hdc, I install Centos 4 from a CDROM, and partition the drives as 2
x raid partition each plus a swap partition on hda, the make md0 and md1 to
install /boot and / respectively. Install goes well, everything looks great,
go to reboot from drives, and all I get is "grub" but no boot. I have
tried
this ten times, doesn't seem I can get around it.

I have to configure this server so that the drives are mirrored. I have
installed redhat 9 in this configuration without problems.

 

What am I doing wrong?

 

Chris Mason

www.anguillaguide.com

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20050417/1c3f4939/attachment-0001.html>

On Sun, 2005-04-17 at 10:27 -0400, Chris Mason (Lists)
wrote:
> I have a p4 motherboard with 2 ide interfaces, I connect 2 40 GB
> drives as hda and hdc, I install Centos 4 from a CDROM, and partition
> the drives as 2 x raid partition each plus a swap partition on hda,
> the make md0 and md1 to install /boot and / respectively. Install goes
> well, everything looks great, go to reboot from drives, and all I get
> is ?grub? but no boot. I have tried this ten times, doesn?t seem I can
> get around it.
> 
> I have to configure this server so that the drives are mirrored. I
> have installed redhat 9 in this configuration without problems.
With the help of Aleksandar Milivojevic I used the attached ks.cfg file
(not sure if it will come through on this list).
I used lilo not grub. Also working on a ks.cfg that uses LVM

Gerald

-------------- next part --------------
# Kickstart file .

install
cdrom
lang en_US.UTF-8
langsupport --default=en_US.UTF-8 en_US.UTF-8
keyboard us
mouse none
text
skipx
#xconfig --card "ATI Mach64" --videoram 8128 --hsync 31-60 --vsync
60-75 --resolution 800x600 --depth 16
network --device eth0 --bootproto static --ip 192.168.1.121 --netmask
255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.1 --hostname
adam.raqware.com
network --device eth1 --bootproto static --ip 192.168.0.121 --netmask
255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.1 --hostname
adam.raqware.com
rootpw --iscrypted $1$RR50eVyL$2J5hPzOVsC44x7hlR/7xI.
firewall --disabled
selinux --disabled
authconfig --enableshadow --enablemd5
timezone America/New_York
zerombr yes
#bootloader --location=mbr
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --all
part raid.01 --size=100 --ondisk hda --asprimary
part raid.11 --size=100 --ondisk hdc --asprimary
part raid.02 --size=4000 --ondisk hda
part raid.12 --size=4000 --ondisk hdc
part raid.03 --size=1024 --ondisk hda
part raid.13 --size=1024 --ondisk hdc
part raid.04 --size=1024 --grow --ondisk hda
part raid.14 --size=1024 --grow --ondisk hdc

raid /boot --level=1 --device=md0 raid.01 raid.11
raid / --level=1 --device=md1 raid.02 raid.12
raid swap --level=1 --device=md2 raid.03 raid.13
raid /home --level=1 --device=md3 raid.04 raid.14

bootloader --location=mbr --useLilo

%packages
@ web-server
@ server-cfg
@ dialup
@ admin-tools
@ smb-server
@ printing
@ text-internet
mdadm
grub
kernel
e2fsprogs

%post

--- "Chris Mason (Lists)" <lists at masonc.com>
wrote:
> I have a p4 motherboard with 2 ide interfaces, I
> connect 2 40 GB drives as
> hda and hdc, I install Centos 4 from a CDROM, and
> partition the drives as 2
> x raid partition each plus a swap partition on hda,
> the make md0 and md1 to
> install /boot and / respectively. Install goes well,
> everything looks great,
> go to reboot from drives, and all I get is "grub"
> but no boot. I have tried
> this ten times, doesn't seem I can get around it.
> 
> I have to configure this server so that the drives
> are mirrored. I have
> installed redhat 9 in this configuration without
> problems.
> 
>  
> 
> What am I doing wrong?
> 
>  
> 
> Chris Mason
hello chris,
i had a similar problem with two scsi drives and ended
up rebooting into rescue mode and installing and
configuring lilo.  machine comes up with no problems
at all now.  remember to run the lilo command after
configuring.

hth,
brett


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

Chris,

Grub needs to be configured to boot of either drive, run the two install
lines referenced in this doc and you should be good:

http://www.dur.ac.uk/a.d.stribblehill/mirrored_grub.html

Kevin

On Tue, 2005-04-26 at 12:00 +0000, centos-request at centos.org
wrote:
> Date: Mon, 25 Apr 2005 22:25:26 -0400
> From: "Chris Mason" <lists at masonc.com>
> Subject: RE: [CentOS] MIrrored drives won't boot after installation
> To: "'CentOS mailing list'" <centos at centos.org>
> Message-ID: <20050426023208.C929092C3FC at mercury.mason.home>
> Content-Type: text/plain;	charset="us-ascii"
> 
> > When you configure the drives as RAID1 the installer never request
where
> > to install the boot record. If configuring with one drive (no raid)
the
> > installer will ask where to install the record.
> > 
> > Gerald
> 
> So how do I fix this? I really need to get a mirrored drive system up and
> running.
> 
> Chris Mason
> US Number: (646)722-0001 US Fax (815)301-9759

On Cent OS 4 the very last screen says REBOOT. Before
click that do CTRL-ALT_F2 and get a prompt.
then enter the following commands.

This will allow the software raid arrays to boot.

grub
find /boot/grub/stage1
device (hd0) /dev/hda
root (hd0,0)
setup (hd0)

This is easier the setting up mdXXX commands after boot.

Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20050510/4004e6b4/attachment-0004.html>

Jerry Geis wrote:
> On Cent OS 4 the very last screen says REBOOT. Before
> click that do CTRL-ALT_F2 and get a prompt.
> then enter the following commands.
> 
> This will allow the software raid arrays to boot.
> 
> grub
> find /boot/grub/stage1
> device (hd0) /dev/hda
> root (hd0,0)
> setup (hd0)
> 
> This is easier the setting up mdXXX commands after boot.
The above would install Grub only on first disk.  If it fails, you would 
be unable to boot since there's no boot loader on the second drive.  To 
correctly set it up, it is a bit more complicated than above.  There's 
several ways to do it, all of them equally correct.  Following your path 
above, he'd need to repeat the last three steps for second disk too. 
Assuming first disk is /dev/hda, and second disk is /dev/hdc, and 
assuming partition containing /boot is first partition on each disk 
((hd0,0) and (hd1,0) parameters):

# grub

grub> find /boot/grub/stage1
(hd0,0)
(hd1,0)

or "find /grub/stage1", depending on partitioning configuration.

grub> device (hd0) /dev/hda
grub> root (hd0,0)
grub> setup (hd0)

grub> device (hd0) /dev/hdc
grub> root (hd0,0)
grub> setup (hd0)

A bit more complicated alternative is using "install" command
directly,
and removing "root" line from grub.conf.  Grub can usually guess what 
should be root correctly.  Something along the lines (assuming /boot is 
separate partition, if not prepend "/boot" to all paths that don't
have it):

install --stage2=/boot/grub/stage2 (hd0,0)/grub/stage1 (hd0) \
         (hd0,0)/grub/stage2 p (hd0,0)/grub/grub.conf

install --stage2=/boot/grub/stage2 (hd1,0)/grub/stage1 (hd1) \
         (hd1,0)/grub/stage2 p (hd1,0)/grub/grub.conf

The above commands are split into two lines for readability.  When 
typing them, remove "\" and type each of them as single line. 
Don't
forget to remove "root" line from /boot/grub/grub.conf if using second
approach.

-- 
Aleksandar Milivojevic <amilivojevic at pbl.ca>    Pollard Banknote
Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7