I moved my root filesystem to a raid5 array, and lilo now refuses to install a boot. It gives the error message "Fatal: Only RAID1 devices are supported for boot images". I understand that the boot cannot be put on a raid5 device, but that's not what I'm trying to do. My root is now raid5, but the boot image is on an ordinary partition. I suspect a bug in lilo, but maybe I'm just confused.
I kept a copy of the old root that is not on raid5, and now, running with my root on raid5, I can successfully run lilo by using the "-r" option to chroot to the old root: "lilo -r /old-root". It's nice to have a work around, but I don't want to have to keep the old root around forever.
Here are some details. It's a Slackware 10 distribution, running Linux 2.6.9, lilo 2.5.9 (and I tried lilo 2.6.1, too). My lilo.conf, the one on the new root that doesn't work, says:
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/sda
message = /old-root/boot/boot_message.txt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
# VESA framebuffer console @ 1024x768x256
vga = 773
menu-title=" Ling Server "
# End LILO global section
# Linux bootable partition config begins
image = /old-root/boot/bzImage269r
root = /dev/md0
append = "md=0,/dev/sdc2,/dev/sdd2./dev/sde2./dev/sdf2./dev/sdg2./dev/sdh2"
label = Linux
image = /old-root/boot/vmlinuz
root = /dev/sda2
label = Linux24
image = /old-root/boot/bzImage269
root = /dev/sda2
label = Linux269
# Linux bootable partition config ends
where /old-root is on /dev/sda2. Lilo is apparently not complaining about installing the image with "root = /dev/md0", because I can comment out that section and I still get the same error.
What am I doing wrong (if anything)?