Red Hat Bugzilla – Bug 17608
During installation lilo.conf incorrect when / is software raid1, leaving system unbootable
Last modified: 2008-05-01 11:37:58 EDT
NOTE: This bug existed in RH 6.x install scripts.
If / filesystem is /dev/md0 and md0 is raid 1 backed by /dev/sda1 and
/dev/sdb1 then boot parameter at top of lilo.conf is incorrectly set to:
instead of raid partition. The resulting system is unbootable.
This can be corrected during installation just before exiting to reboot by
changing to the second console and performing the following:
pico /mnt/sysimage/etc/lilo.conf (changing boot to: boot=/dev/md0)
/mnt/sysimage/sbin/lilo -r /mnt/sysimage
Of course it would be much better if the installation scripts got it right
in the first place ;)
This seems to work in 7.0. Please reopen if it doesn't.
7.0 does indeed boot under those conditions (guess the bootloader was improved).
But lilo.conf still incorrectly references boot=/dev/sda instead of
As installed if sda fails there will be no bootloader on sdb and in spite of the
raid configuration it will not boot without a boot floppy.
By using boot=/dev/md0 lilo writes the boot record on sda and sdb to it can boot
with either drive.