Bug#574350: grub-pc: boot failure after upgrade to 1.98
On Thu, Mar 18, 2010 at 06:46:34PM -0400, Andres Cimmarusti wrote: > I had to do a fresh install of squeeze because I got a new hard drive. > Shortly after finishing up the installation I full-upgraded and that pulled > grub-pc 1.98-1 and it installed without errors. > > The reason for the previous failure was that I was running 2.6.33 kernel > from experimental. This changed my /dev/hd* to /dev/sd* and caused > grub-setup to fail. So, in reality, you should close this bug, because it > doesn't affect squeeze (strictly speaking). However, work might be required > when 2.6.33 enters sid. No, this bug (which I've merged with a cluster of other similar bugs) should remain open because it affects all kinds of situations where device names might change, not just the narrow situation involved in the transition to libata. /dev/[hs]d* device names have not been stable for some years now, and GRUB should not be relying on them. For example, consider the case of removable USB devices on a system that also has SCSI disks - which one happens to get /dev/sda is essentially random in many configurations. Don't worry - this bug is well-understood and we're on the path to a fix, so there's little point trying to optimise things by closing the bug. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574350: grub-pc: boot failure after upgrade to 1.98
I had to do a fresh install of squeeze because I got a new hard drive. Shortly after finishing up the installation I full-upgraded and that pulled grub-pc 1.98-1 and it installed without errors. The reason for the previous failure was that I was running 2.6.33 kernel from experimental. This changed my /dev/hd* to /dev/sd* and caused grub-setup to fail. So, in reality, you should close this bug, because it doesn't affect squeeze (strictly speaking). However, work might be required when 2.6.33 enters sid. Best regards Andres 2010/3/18 Colin Watson > merge 554790 574350 > thanks > > On Wed, Mar 17, 2010 at 10:34:14AM -0400, Andres Cimmarusti wrote: > > When I upgraded today to grub 1.98-1 (on two different laptops), I > noticed > > the following message (apt): > > > > /usr/sbin/grub-setup: error: no mapping exists for `hd0' > > > > Upon restarting the system grub2 went it rescue mode after failing to > boot > > and showing me this message: > > > > error: the symbol 'grub_env_find' not found > > This is the same as the cluster of bugs described in #554790. I intend > to get this fixed soon, although in some cases it will result in a > debconf question on upgrade when we can't automatically work out the > right answer reliably. > > Thanks, > > -- > Colin Watson [cjwat...@debian.org] >
Bug#574350: grub-pc: boot failure after upgrade to 1.98
merge 554790 574350 thanks On Wed, Mar 17, 2010 at 10:34:14AM -0400, Andres Cimmarusti wrote: > When I upgraded today to grub 1.98-1 (on two different laptops), I noticed > the following message (apt): > > /usr/sbin/grub-setup: error: no mapping exists for `hd0' > > Upon restarting the system grub2 went it rescue mode after failing to boot > and showing me this message: > > error: the symbol 'grub_env_find' not found This is the same as the cluster of bugs described in #554790. I intend to get this fixed soon, although in some cases it will result in a debconf question on upgrade when we can't automatically work out the right answer reliably. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574350: grub-pc: boot failure after upgrade to 1.98
> set locale_dir=3D($root)/boot/grub/locale > set lang=3Den > insmod gettext > set timeout=3D5 > ### END /etc/grub.d/00_header ### > > ### BEGIN /etc/grub.d/05_debian_theme ### > insmod ext2 > set root=3D'(hd0,1)' > search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb24= > insmod png > if background_image /boot/grub/moreblue-orbit-grub.png ; then > set color_normal=3Dblack/black > set color_highlight=3Dmagenta/black > else > set menu_color_normal=3Dcyan/blue > set menu_color_highlight=3Dwhite/blue > fi > ### END /etc/grub.d/05_debian_theme ### > > ### BEGIN /etc/grub.d/10_linux ### > menuentry "Debian GNU/Linux, with Linux 2.6.33-2-amd64" --class debian = --class gnu-linux --class gnu --class os { > insmod ext2 > set root=3D'(hd0,1)' > search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb2= 4 > echoLoading Linux 2.6.33-2-amd64 ... > linux /boot/vmlinuz-2.6.33-2-amd64 > root=3DUUID=3Da34090d4-6bd6-45ea-8e= 76-8aaad107fb24 ro quiet > echoLoading initial ramdisk ... > initrd /boot/initrd.img-2.6.33-2-amd64 > } > menuentry "Debian GNU/Linux, with Linux 2.6.33-2-amd64 (recovery mode)"= --class debian --class gnu-linux --class gnu --class os { > insmod ext2 > set root=3D'(hd0,1)' > search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb2= 4 > echoLoading Linux 2.6.33-2-amd64 ... > linux /boot/vmlinuz-2.6.33-2-amd64 > root=3DUUID=3Da34090d4-6bd6-45ea-8e= 76-8aaad107fb24 ro single=20 > echoLoading initial ramdisk ... > initrd /boot/initrd.img-2.6.33-2-amd64 > } > menuentry "Debian GNU/Linux, with Linux 2.6.32-3-amd64" --class debian = --class gnu-linux --class gnu --class os { > insmod ext2 > set root=3D'(hd0,1)' > search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb2= 4 > echoLoading Linux 2.6.32-3-amd64 ... > linux /boot/vmlinuz-2.6.32-3-amd64 > root=3DUUID=3Da34090d4-6bd6-45ea-8e= 76-8aaad107fb24 ro quiet > echoLoading initial ramdisk ... > initrd /boot/initrd.img-2.6.32-3-amd64 > } > menuentry "Debian GNU/Linux, with Linux 2.6.32-3-amd64 (recovery mode)"= --class debian --class gnu-linux --class gnu --class os { > insmod ext2 > set root=3D'(hd0,1)' > search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb2= 4 > echoLoading Linux 2.6.32-3-amd64 ... > linux /boot/vmlinuz-2.6.32-3-amd64 > root=3DUUID=3Da34090d4-6bd6-45ea-8e= 76-8aaad107fb24 ro single=20 > echoLoading initial ramdisk ... > initrd /boot/initrd.img-2.6.32-3-amd64 > } > ### END /etc/grub.d/10_linux ### > > ### BEGIN /etc/grub.d/30_os-prober ### > ### END /etc/grub.d/30_os-prober ### > > ### BEGIN /etc/grub.d/40_custom ### > # This file provides an easy way to add custom menu entries. Simply ty= pe the > # menu entries you want to add after this comment. Be careful not to c= hange > # the 'exec tail' line above. > ### END /etc/grub.d/40_custom ### > *** END /boot/grub/grub.cfg > > -- System Information: > Debian Release: squeeze/sid > APT prefers testing > APT policy: (500, 'testing'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.33-2-amd64 (SMP w/1 CPU core) > Locale: LANG=3Den_US.UTF-8, LC_CTYPE=3Den_US.UTF-8 (charmap=3DUTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages grub-pc depends on: > ii debconf [debconf-2.0] 1.5.28 Debian configuration manag= ement sy > ii grub-common 1.98-1 GRand Unified Bootloader, = version=20 > ii libc6 2.10.2-6 Embedded GNU C Library: Sh= ared lib > ii ucf 3.0025 Update Configuration File:= preserv > > grub-pc recommends no packages. > > Versions of packages grub-pc suggests: > ii desktop-base 5.0.5 common files for the Debia= n Deskto > > -- debconf information: > grub-pc/kopt_extracted: false > grub2/kfreebsd_cmdline: > * grub-pc/install_devices: (hd0) > grub-pc/postrm_purge_boot_grub: false > * grub2/linux_cmdline: > grub2/kfreebsd_cmdline_default: quiet > * grub2/linux_cmdline_default: quiet > grub-pc/chainload_from_menu.lst: true > > > > ___ > Pkg-grub-devel mailing list > pkg-grub-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel > > =20 --=20 Regards Vladimir '=CF=86-coder/phcoder' Serbinenko signature.asc Description: OpenPGP digital signature
Bug#574350: grub-pc: boot failure after upgrade to 1.98
Package: grub-pc Version: 1.98-1 Severity: grave Justification: renders package unusable When I upgraded today to grub 1.98-1 (on two different laptops), I noticed the following message (apt): /usr/sbin/grub-setup: error: no mapping exists for `hd0' Upon restarting the system grub2 went it rescue mode after failing to boot and showing me this message: error: the symbol 'grub_env_find' not found I had to boot off the CD/DVD with the debian installer in rescue mode, mount root partition and reinstall grub-common and grub-pc (yes, version 1.98-1 worked with no errors this time). Upon reboot everything worked the way it was supposed to. However, for testing I tried reinstalling grub-pc again. Apt showed me the same error!. So before rebooting, I looked at the file /boot/grub/device.map which showed: (hd0) /dev/hda I changed hda to sda. Then reinstalled again and got no errors, restarted and everything worked well. There is an error in grub-pc when detecting drives during the upgrade/installation. Please fix it, as it renders the system unbootable. -- Package-specific info: *** BEGIN /proc/mounts /dev/disk/by-uuid/a34090d4-6bd6-45ea-8e76-8aaad107fb24 / ext4 rw,noatime,errors=remount-ro,barrier=1,data=ordered 0 0 /dev/sda6 /home ext4 rw,noatime,barrier=1,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/device.map (hd0) /dev/sda *** END /boot/grub/device.map *** BEGIN /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by /usr/sbin/grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi set default="0" if [ ${prev_saved_entry} ]; then set saved_entry=${prev_saved_entry} save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z ${boot_once} ]; then saved_entry=${chosen} save_env saved_entry fi } insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb24 if loadfont /usr/share/grub/unicode.pf2 ; then set gfxmode=640x480 insmod gfxterm insmod vbe if terminal_output gfxterm ; then true ; else # For backward compatibility with versions of terminal.mod that don't # understand terminal_output terminal gfxterm fi fi insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb24 set locale_dir=($root)/boot/grub/locale set lang=en insmod gettext set timeout=5 ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb24 insmod png if background_image /boot/grub/moreblue-orbit-grub.png ; then set color_normal=black/black set color_highlight=magenta/black else set menu_color_normal=cyan/blue set menu_color_highlight=white/blue fi ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/10_linux ### menuentry "Debian GNU/Linux, with Linux 2.6.33-2-amd64" --class debian --class gnu-linux --class gnu --class os { insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb24 echoLoading Linux 2.6.33-2-amd64 ... linux /boot/vmlinuz-2.6.33-2-amd64 root=UUID=a34090d4-6bd6-45ea-8e76-8aaad107fb24 ro quiet echoLoading initial ramdisk ... initrd /boot/initrd.img-2.6.33-2-amd64 } menuentry "Debian GNU/Linux, with Linux 2.6.33-2-amd64 (recovery mode)" --class debian --class gnu-linux --class gnu --class os { insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb24 echoLoading Linux 2.6.33-2-amd64 ... linux /boot/vmlinuz-2.6.33-2-amd64 root=UUID=a34090d4-6bd6-45ea-8e76-8aaad107fb24 ro single echoLoading initial ramdisk ... initrd /boot/initrd.img-2.6.33-2-amd64 } menuentry "Debian GNU/Linux, with Linux 2.6.32-3-amd64" --class debian --class gnu-linux --class gnu --class os { insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb24 echoLoading Linux 2.6.32-3-amd64 ... linux /boot/vmlinuz-2.6.32-3-amd64 root=UUID=a34090d4-6bd6-45ea-8e76-8aaad107fb24 ro quiet echoLoading initial ramdisk ... initrd /boot/initrd.img-2.6.32-3-amd64 } menuentry "Debian GNU/Linux, with Linux 2.6.32-3-amd64 (recovery mode)" --class debian --class gnu-linux --class gnu --class os { insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set a34090d4-6bd6-45ea-8e76-8aaad107fb24 echoLoading Linux 2.6.32-3-amd64 ... linux /boot/vmlinuz-2.6.32-3-amd64 root=UUID=a34090d4-6bd6-45ea-8e76-8