Bug#558312: grub_gettext not found
Felix Zielcke wrote: Hello everybody, I also had the same bug just after an upgrade and I would like to thank to Sebastian for the helpful commands to boot from the grub prompt ! Felix Zielcke wrote: If grub-intall gets run on a device where you don't boot from, then all the modules in /boot/grub gets updated but the embed core.img which contains GRUB's kernel doestn't get updated. And so it gets out of sync. I did not find the file core.img in my /boot/grub directory. When I upgrade my system (Debian Sid), the new package grub-pc_1.97+20091130-1_i386.deb, the file core.img was there. I have not the package memtest86 installed on my system. The problem produced the next boot following an upgrade of my system, done the 11/28/2009 with the safe-upgrade option). I notice an new initrd image created the same day that the upgrade without any action by me. I hope these information could help you, because this bug is a little critical ;) Regards, Bernard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: grub_gettext not found
This bug affected me, as well. I have two hard drives, and memtest was NOT installed. Reconfiguring grub-pc and installing to both devices fixed this problem for me. Many thanks to Sebastian, without whose linux16 suggestion I would almost certainly still be angrily playing with a grub rescue prompt. -- ,---. Teri Solow tso...@tekniklr.com ( o o ) http://tekniklr.com ). .( '/|||\` When we talk of tomorrow, the gods laugh. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: grub_gettext not found
Package: grub-pc
Version: 1.97+20091125-1
Severity: normal
Hi,
just an update: I purged re-installed grub-pc again, this time without
grub-invaders and memtest86+ and so I have got a working bootloader. I will
try to find out which one of the two is the culprit.
Kind regards
Sebastian
PS: For means of completion, here is my whole fdisk layout and mount
information (without
nfs, though)
Platte /dev/hda: 120.0 GByte, 120034123776 Byte
255 K�pfe, 63 Sektoren/Spur, 14593 Zylinder
Einheiten = Zylinder von 16065 � 512 = 8225280 Bytes
Disk identifier: 0x5019e70c
Gerät boot. AnfangEnde Bl�cke Id System
/dev/hda1 1364729294496 83 Linux
/dev/hda23648 14593879237455 Erweiterte
/dev/hda53648 1446786911618+ 83 Linux
/dev/hda6 14468 14593 1012063+ 82 Linux Swap / Solaris
/dev/hda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/hda5 on /home type ext3 (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
(rw,noexec,nosuid,nodev)
nfsd on /proc/fs/nfsd type nfsd (rw)
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 / ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/hda5 /home ext3 rw,relatime,errors=continue,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/hda
*** 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 ###
set default=0
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
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
set locale_dir=/boot/grub/locale
set lang=de
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 c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
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.31-1-686 {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux /boot/vmlinuz-2.6.31-1-686
root=UUID=c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 ro quiet
initrd /boot/initrd.img-2.6.31-1-686
}
menuentry Debian GNU/Linux, with Linux 2.6.31-1-686 (recovery mode) {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux /boot/vmlinuz-2.6.31-1-686
root=UUID=c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 ro single
initrd /boot/initrd.img-2.6.31-1-686
}
menuentry Debian GNU/Linux, with Linux 2.6.30-2-686 {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux /boot/vmlinuz-2.6.30-2-686
root=UUID=c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 ro quiet
initrd /boot/initrd.img-2.6.30-2-686
}
menuentry Debian GNU/Linux, with Linux 2.6.30-2-686 (recovery mode) {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux /boot/vmlinuz-2.6.30-2-686
root=UUID=c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 ro single
initrd /boot/initrd.img-2.6.30-2-686
}
### 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 type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers proposed-updates
APT policy: (500,
Bug#558312: grub_gettext not found
Hi, after purging, removing their leftovers and reinstalling everything (grub-pc, grub-common, os-prober grub-invaders, memtest86+) I have a booting system again. During the process, grub-probe sometimes threw an error with some (null), but sometimes it did not. I am sorry, I cannot reproduce it any more. Kind regards Sebastian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: grub_gettext not found
I was also affected by this bug, many thanks to Sebastian for posting the recovery instructions! I also had os-prober and memtest86+ installed (but no grub-invaders), simply removing memtest86+ (and keeping os-probe) made the bug disappear, hope this helps to narrow it down. If not and you need help reproducing it, let me know and I will try to reinstall memtest86+ and see if it comes back. -- Dmitry Borodaenko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: grub_gettext not found
Am Sonntag, den 29.11.2009, 17:54 +0200 schrieb Dmitry Borodaenko: I was also affected by this bug, many thanks to Sebastian for posting the recovery instructions! I also had os-prober and memtest86+ installed (but no grub-invaders), simply removing memtest86+ (and keeping os-probe) made the bug disappear, hope this helps to narrow it down. If not and you need help reproducing it, let me know and I will try to reinstall memtest86+ and see if it comes back. Did you really test this correctly? I can't imagine the /etc/grub.d/20_memtest86+ provided by the memtest86+ package causes this. As i already said in the report (though to someone else) the only reason for that should be when the embed core.img is out of sync with /boot/grub Which only happens if grub-install gets run on a disk device where your BIOS isn't booting from. And that can happen because sometimes the kernel just thinks it's a good idea to renumber them and so the stored device in the grub-pc/install_devices debconf prompt is wrong. -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: grub_gettext not found
On Sun, Nov 29, 2009 at 6:07 PM, Felix Zielcke fziel...@z-51.de wrote: Did you really test this correctly? This is my production laptop, so I stopped testing this as soon as I got it working and I'm not eager to risk bricking it again. At least, not until next weekend :) I can't imagine the /etc/grub.d/20_memtest86+ provided by the memtest86+ package causes this. As i already said in the report (though to someone else) the only reason for that should be when the embed core.img is out of sync with /boot/grub Which only happens if grub-install gets run on a disk device where your BIOS isn't booting from. And that can happen because sometimes the kernel just thinks it's a good idea to renumber them and so the stored device in the grub-pc/install_devices debconf prompt is wrong. I don't see enough evidence to support that conclusion, quite the contrary. Both Sebastian's and my machine only have a single hard drive (/dev/hda in his case and /dev/sda in mine), so there's no other device for the kernel to get confused about. Having seen your comments about the debconf install_devices option I checked that, and it did refer to /dev/sda. Also, note how re-configuring grub-pc didn't help Sebastian, while removing memtest86+ did. Did you actually try and fail to reproduce this bug with grub-pc 1.97+20091125-1 and memtest86+ 4.00-2 on unstable? If yes, then it might make sense to see what was your test setup and how it differs from what my and Sebastian's machines have in common. Output of mount on my machine: /dev/mapper/root on / type ext3 (rw,relatime,errors=remount-ro,commit=0) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/sda8 on /usr type ext3 (rw,noatime,commit=0) /dev/sda3 on /boot type ext3 (rw,noatime,commit=0) tmpfs on /tmp type tmpfs (rw,size=512m) tmpfs on /home/angdraug/tmp type tmpfs (rw,size=512m) /dev/sda1 on /mnt/c type ntfs (ro,noatime,uid=1000,gid=1000,umask=022,nls=utf8) /dev/sda7 on /mnt/d type vfat (rw,noexec,noatime,uid=1000,gid=1000,umask=022,iocharset=utf8,showexec) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) -- Dmitry Borodaenko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: grub_gettext not found
Package: grub-pc
Version: 1.97+20091125-1
Severity: normal
Hi,
I wanted to confirm the bug for the package I upgraded to today. And for
those who like me are sitting at the prompt and don't know what to do, here
is what I did:
* booted from knoppix to access /boot/grub/grub.cfg
* determined kernel version
* booted again into grub rescue, typing:
insmod help
insmod ext2
insmod linux16
set root=(hd0,1)
linux16 /boot/vmlinuz-2.6.31-1-686 root=/dev/hda1 ro
initrd16 /boot/initrd.img-2.6.31-1-686
boot
The above must be fixed to the settings from your grub.cfg. I'm glad linux16
did work. insmod linux did not work because of the gettext problem.
Kind regards
Sebastian
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/hda1 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/hda5 /home ext3 rw,relatime,errors=continue,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/hda
*** 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 ###
set default=0
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
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
set locale_dir=/boot/grub/locale
set lang=de
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 c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
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.31-1-686 {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux /boot/vmlinuz-2.6.31-1-686
root=UUID=c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 ro quiet
initrd /boot/initrd.img-2.6.31-1-686
}
menuentry Debian GNU/Linux, with Linux 2.6.31-1-686 (recovery mode) {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux /boot/vmlinuz-2.6.31-1-686
root=UUID=c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 ro single
initrd /boot/initrd.img-2.6.31-1-686
}
menuentry Debian GNU/Linux, with Linux 2.6.30-2-686 {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux /boot/vmlinuz-2.6.30-2-686
root=UUID=c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 ro quiet
initrd /boot/initrd.img-2.6.30-2-686
}
menuentry Debian GNU/Linux, with Linux 2.6.30-2-686 (recovery mode) {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux /boot/vmlinuz-2.6.30-2-686
root=UUID=c1f10a1f-cc0e-4f85-ba9d-833dc59ae916 ro single
initrd /boot/initrd.img-2.6.30-2-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry Memory test (memtest86+) {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux16 /boot/memtest86+.bin
}
menuentry Memory test (memtest86+, serial console 115200) {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/22_invaders ###
menuentry GRUB Invaders {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c1f10a1f-cc0e-4f85-ba9d-833dc59ae916
multiboot /boot/invaders.exec
}
### END /etc/grub.d/22_invaders ###
### 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 type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux
Bug#558312: grub_gettext not found
Hi, «echo GET grub-pc/install_devices | debconf-communicate» shows 0 /dev/hda I will also try to purge and reinstall all grub-related packages. Kind regards Sebastian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: grub_gettext not found
Hi, I will also try to purge and reinstall all grub-related packages. did not work, same error. Also I had to manually remove /boot/grub after purging, although I think debconf had asked to do this for me. Debconf also only offers /dev/hda to me so I don't think I have duplicate grub versions installed. Kind regards Sebastian Bremicker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
