lilo itself runs perfectly well when installing on a system
which has both / and /boot on separate software raid1
devices. It installs on both sda and sdb as expected.
"lilo -R", on the other hand, fares less well: it results in
[root@sarek sct]# /sbin/lilo -R test
boot = /dev/sdb, map = /boot/map.0815
and next boot (from /dev/sda) does _not_ run the requested
new image. For both / and /boot, /dev/sdb is listed before
/dev/sda in /proc/mdstat --- don't blame me, that's how the
rh6.1 installer left things.
Assigned to dledford
I haven't seen this behavior in newer releases; can you replicate it there?
Closing due to inactivity. If you have further information, please reopen this bug.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.