Joey Hess wrote:
Package: lilo-installer
I'm proposing a patch to solve this problem. It is quite simple: let's check if the boot device it's a raid device and let's see if its filesystem is xfs. If both are true let's pass raid-extra-boot=mbr-only to lilo.conf .
Maybe the getfs function is a duplicate and can be removed.I haven't tried it yet, for I don't know how to build the installer, but I hope it can help you fixing the bug.
Bye -- Non c'è più forza nella normalità, c'è solo monotonia.
--- postinst.orig 2004-10-30 10:50:32.000000000 +0200
+++ postinst 2004-10-30 11:43:56.000000000 +0200
@@ -22,6 +22,10 @@
mount | grep "on /target${1%/} " | cut -d' ' -f1
}
+getfs () {
+ mount | grep "on /target${1%/} " | cut -d' ' -f5
+}
+
lvm_vg () {
# Map from /dev/mapper/<vg>-<lv> to /dev/<vg>/<lv> for
# Dup of code in partman.
@@ -58,6 +62,17 @@
fi
disc_offered=$(mapdevfs "$disc_offered_devfs")
+if [ "$prefix" == /dev/md ]; then
+ bootfilesystem=$(getfs /boot)
+ if [ "$bootfilesystem" == xfs ]; then
+ raid_extra_boot="raid-extra-boot=mbr-only"
+ else
+ raid_extra_boot="#raid-extra-boot="
+ fi
+else
+ raid_extra_boot="#raid-extra-boot="
+fi
+
db_capb backup
db_subst lilo-installer/bootdev disc "$disc_offered"
@@ -219,6 +234,15 @@
#
root=${rootfs}
+# Specifies how to write the boot loader to the boot device when it
+# is a raid device. The default action is auto, meaning, automatically
+# generate auxilary boot records as needed on skewed raid sets. The
+# option mbr-only suppresses generation of a boot record on the raid
+# device and writes the boot records to all Master Boot Records. This
+# is needed if the boot device as got an xfs filesystem.
+#
+${raid_extra_boot}
+
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
Attachment:
signature.asc
Description: OpenPGP digital signature