On Fri, Feb 15, 2013 at 2:29 PM, Yamaban
The bug is https://bugzilla.novell.com/show_bug.cgi?id=804065
Short-list for repair:
You wish to use Grub2:
1. uninstall 'grub' (rpm -e grub)
Done.
2. edit file: /etc/sysconfig/bootloader line LOADER_TYPE to LOADER_TYPE="grub2"
Done.
3. to make sure edit /boot/grub2/grub.cfg to match your kernel.
Done.
4. call "/sbin/update-bootloader --refresh" to make sure the config is active.
Fails with: Perl-Bootloader: 2013-02-15 16:35:48 ERROR: Core::ReadFiles: Failed to open /boot/grub2/device.map Can't use an undefined value as a HASH reference at /usr/lib/perl5/vendor_perl/5.16.0/Bootloader/Core/GRUB2.pm line 1105. The file /boot/grub2/device.map does in fact not exist on this system.
Just why the install of grub2 killed /boot/grub/menu.lst, but did not change LOADER_TYPE is a mystery to me.
It turns out that the grub2 upgrade did not cause the problem. The system was actually built in this broken state by SUSE Studio. I have the original image (as downloaded from SUSE Studio) lying around and am able to reproduce the problem in VMWare on my laptop and can see that it has /etc/sysconfig/bootloader configured wrong. I vaguely remember a bootloader selection in SUSE Studio but don't remember what I put there (if I could login to SUSE Studio I would examine how I had configured the virtual machine image, but SUSE Studio login is completely broken ATM...). Perhaps there is something about VMWare image builds that violates assumptions of the grub2 install? -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org