Bug#498614: debian-installer: Invalid grub2 configuration generated after fresh lenny install
Package: debian-installer Severity: grave Justification: renders package unusable I did a fresh install of lenny today. I selected to use the experimental grub2 instead of legacy grub. After reboot I got the debian splash image in grub. Waited 5 seconds and then grub gave me some error message I can't remember now. Another partition contained a Windows installation. There was an entry in the menu for that, but I couldn't boot into that either. Using the grub shell I was able to boot into debian. I had to specify: linux (hd0,5)/boot/vm... to let grub know on which partition the kernel was located. I guess somehow the set root command didn't work. I'm not using lvm. Marked as grave since it renders my system unusable (and alot of people wouldn't know how to fix easily). You might want to downgrade since I did answer yes on the big fat warning that grub2 is experimental. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498614: extra information
I was able to find out more precisely what went wrong. I first tried booting into Windows, which executed "set root=(hd0,0)". That's the wrong partition, it should have been (hd0,1). So it failed booting, returning me to the menu. Then I selected debian, but it couldn't find the kernel because the root was set to (hd0,0). To protect against this the menu-entry for debian should include the set root command. Alexander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
