Hmm So your saying you can't disconnect any drive without LILO stuffing up... bad..
Umm Have you got your BIOS setup to autodetect the HD's?
A very simple way of putting LILO in both drives is to edit your /etc/lilo.conf:
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz
label=linux
root=/dev/sda1
initrd=/boot/initrd-2.0.36-0.7.img
read-only
If say your root drive is sda1 which is RAIDed to sdb1 then all you need to do is
change the boot= & root= lines once.
boot=/dev/sdb
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz
label=linux
root=/dev/sdb1
initrd=/boot/initrd-2.0.36-0.7.img
read-only
Now.. run lilo.
ignore the warning about lilo not being installed in the booted drive.
Your lilo config should have now been put into the second drive, this is independant
of the first drive as long as your RAID is setup correctly and swap is setup right:-)
You might want to change the config back to the orignal and make a note to do the
change each time you update the kernel.
Done! Now in you should be able to boot from any of the two drives:-)
If you still have trouble post your lilo.conf file.
If you put lilo in the MBR (someone correct me if I'm wrong) I don't think you need to
make the root partition bootable using fdisk as LILO runs from the MBR before even the
partitions get looked at.
If you put your swap partitions on both drives without RAIDing them you will/might get
a kernel crash if one of the drives fail depending on which drive the kernel put its
personal memory on.
If your not going to RAID swap then just put the swap on one drive so you get a 50%
chance that a disk crash won't knock the machione down.
Steve McPherson wrote:
> I hate to be such a knuckle head. I have swap partitions on hda AND hdc. Should I
>not? When I disconnect hda, I get LI. When I disconnect hdc, I get a *bunch* of
>01's scrolling up the screen. How did you put the kernel in the MBR of each drive?
>Is that what I'm missing? when I look at fdisk, both hda1 and hdc1 are bootable.
>Are there any other files I need to change? As I said earlier, I'm reasonably sure
>RAID is working. DMESG and mdstat seem to indicate it is working. When I shutdown
>or reboot I see unbind hda5 and hdc5.
>
> >>> David Robinson <[EMAIL PROTECTED]> 06/08/99 09:16PM >>>
> The best way to do a test is just to pull the power on one of the drives in the
>array. It's best not to pull the cable off as it might send a spike back to the IDE
>card and do some damage.
>
> If your doing mirroring then you'll be using RAID 1.
>
> Check your swap partition. If your swap partition is on the drive you are about to
>pull out and the swap is not on a RAID partition then your kernel will/may hang if
>there was memory swapped out to it.
>
> I have setup my swap on both drives but not as a RAID partition. If one drive dies
>the system will crash but after a reboot my system will just boot off the working
>drive as I have put the kernel in the Master Boot Record on both Drives.
> At least I won't loose any data:-)
>
> Steve McPherson wrote:
>
> > David,
> > I'm having some trouble with my raid, and I'm hoping you're willing to help
>me out.
> > I'm using RH 6.0 with the 2.2.5-15 kernel with raid 0 and 5 and multiple devices
>driver support and autodetect RAID partitions compiled in. I think everything is OK.
> I mean raid starts when I boot and it stops when I shutdown. I'm using two
>identical WD 4.3 gb hdd's. I'm trying to mirror hda1 and hdc1. I'd like to test my
>raid system. If I disconnect hda, I get a kernel panic message. Can you explain how
>I test my raid system?
> > Thanks David.
> >
> > -Steve McPherson
