https://bugzilla.novell.com/show_bug.cgi?id=278568 Summary: Perl bootloader creates menu.lst booting from only 1 raid1 Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: volker3204@paradise.net.nz QAContact: qa@suse.de 10.2 final, with perl-Bootloader-0.4.14-1.2, installing 2.6.18.8-0.3-default Apart from writing a menu.lst with a default section which no longer exists (old kernel uninstalled), the new menu.lst also mangled one section to boot from the wrong disk of a raid1. These are the relevant parts only: gfxmenu (hd0,4)/boot/message title openSUSE 10.2 root (hd0,4) kernel /boot/vmlinuz-2.6.18.8-0.1-default root=/dev/md0 title openSUSE 10.2 (disk 2) root (hd1,4) gfxmenu (hd1,4)/boot/message kernel /boot/vmlinuz-2.6.18.8-0.1-default root=/dev/md0 title Failsafe -- openSUSE 10.2 root (hd0,4) kernel /boot/vmlinuz-2.6.18.8-0.1-default root=/dev/md0 Together with /etc/grub.conf setup --stage2=/boot/grub/stage2 (hd0) (hd0,4) setup --stage2=/boot/grub/stage2 (hd1) (hd1,4) quit this allows to boot from either disk when the other is missing. Installing the new kernel turned this into: gfxmenu (hd0,4)/boot/message title openSUSE 10.2 - 2.6.18.8-0.3 root (hd1,4) kernel /boot/vmlinuz-2.6.18.8-0.3-default root=/dev/md0 title Failsafe -- openSUSE 10.2 - 2.6.18.8-0.3 root (hd1,4) kernel /boot/vmlinuz-2.6.18.8-0.3-default root=/dev/md0 The first entry is now always booting and getting the gfxmenu from the second disk, as is the second entry. I probably created /etc/grub.conf manually, although IMHO yast should do that for raid1, and IIRC yast was able to do it for 9.x. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.