Well, I got it working by booting to a remotely mounted DOS CD and doing a:
fdisk /mbr
on each drive. I'm not really sure why that was necessary though so here is the extra information:
I did not use madm.conf, here is the command given to create the raid:
Code:
mdadm -Cv /dev/md0 -l1 -n2 /dev/sda1 /dev/sdb1
Lilo.conf
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/md0
#compact # faster, but won't work on all systems.
# Standard menu.
message = /boot/boot_message.txt
# Append any additional kernel parameters:
append="Linux vt.default_utf8=0"
#prompt
#timeout = 5
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/md0
label = Linux
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
So my guess is that this lilo.conf wrote to /dev/md0 (or /dev/sda1 and /dev/sdb1), but it does not put any record to /dev/sda and /dev/sdb, and the fdisk /mbr wrote the master boot record to /dev/sda and /dev/sdb for me?
Is there a better way to do this?
man lilo.conf say to use something like /dev/md0, which I did.
