Bug#558312: error: grub_gettext not found
reopen 558312 reassign 558312 grub-pc # I knew we have already an open report for this forcemerge 554790 558312 thanks Am Samstag, den 28.11.2009, 07:42 +0100 schrieb Michael Biebl: Felix Zielcke wrote: I just tried it out in a vm. Installed squeeze beta3-1 where grub-pc/install_devices is not set at all. Then ran grub-install /dev/sda. Rebooted. Then upgraded to current sid version. Not running grub-install and neither it was ran by the postinst. And a reboot worked still fine. I had purged and reinstalled grub in between and I can't reproduce the problem anymore. Ok. I just assume it's the grub-pc/install_devices problem. Nonetheless, if I understand you resp. Robert correctly, it is no longer possible to boot from a rescue disc, mount the root partition manually, do a chroot and do a grub-install? That would be very unfortunate. Or did I misread Roberts answer? You did. It's still possible and recommended to chroot to the installed system just as before. The only thing you need to pay attention that you install to the MBR/disk device of the disk your BIOS boots from. 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. Michael -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#558312: error: grub_gettext not found
Package: grub2
Version: 1.97~beta3-1
Severity: critical
Justification: breaks the whole system
After upgrading to grub 1.97+20091125 grub fails at startup with:
error: grub_gettext not found
and leaves the box on grub_rescue prompt without help.mod not cat.mod
loaded (ls.mod is loaded).
The system is unbootable. Same problem with experimental 1.97+20091127.
Thanks.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/85d9d137-834b-449f-986e-2794f09fcb75 / ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sdb8 /home ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sdb5 /tmp ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sdb9 /usr ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sdc1 /var ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sda2 /home/Musica ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sdb7 /mnt/tmppart ext3 rw,relatime,errors=continue,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(fd0) /dev/fd0
(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdc
*** 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=(hd1,9)
search --no-floppy --fs-uuid --set 4f7f07c3-2087-4c53-a00e-7e434a3ca2fe
if loadfont /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 timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, Linux 2.6.30-2-amd64 {
insmod ext2
set root=(hd1,2)
search --no-floppy --fs-uuid --set 85d9d137-834b-449f-986e-2794f09fcb75
linux /boot/vmlinuz-2.6.30-2-amd64
root=UUID=85d9d137-834b-449f-986e-2794f09fcb75 ro quiet vga=791 8250.nr_uarts=8
initrd /boot/initrd.img-2.6.30-2-amd64
}
menuentry Debian GNU/Linux, Linux 2.6.30-2-amd64 (recovery mode) {
insmod ext2
set root=(hd1,2)
search --no-floppy --fs-uuid --set 85d9d137-834b-449f-986e-2794f09fcb75
linux /boot/vmlinuz-2.6.30-2-amd64
root=UUID=85d9d137-834b-449f-986e-2794f09fcb75 ro single
initrd /boot/initrd.img-2.6.30-2-amd64
}
menuentry Debian GNU/Linux, Linux 2.6.26-2-amd64 {
insmod ext2
set root=(hd1,2)
search --no-floppy --fs-uuid --set 85d9d137-834b-449f-986e-2794f09fcb75
linux /boot/vmlinuz-2.6.26-2-amd64
root=UUID=85d9d137-834b-449f-986e-2794f09fcb75 ro quiet vga=791 8250.nr_uarts=8
initrd /boot/initrd.img-2.6.26-2-amd64
}
menuentry Debian GNU/Linux, Linux 2.6.26-2-amd64 (recovery mode) {
insmod ext2
set root=(hd1,2)
search --no-floppy --fs-uuid --set 85d9d137-834b-449f-986e-2794f09fcb75
linux /boot/vmlinuz-2.6.26-2-amd64
root=UUID=85d9d137-834b-449f-986e-2794f09fcb75 ro single
initrd /boot/initrd.img-2.6.26-2-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 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 unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-amd64 (SMP w/1 CPU core)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub2 depends on:
ii grub-pc 1.97~beta3-1 GRand Unified Bootloader, version
grub2 recommends no packages.
grub2 suggests no packages.
-- debconf information:
grub2/numbering_scheme_transition:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: error: grub_gettext not found
notfound 558312 1.97~beta3-1 found 558312 1.97+20091125-1 tags 558312 unreproducible thanks On Fri, Nov 27, 2009 at 04:35:31PM -0300, Fernando M. Maresca wrote: Package: grub2 Version: 1.97~beta3-1 Severity: critical Justification: breaks the whole system After upgrading to grub 1.97+20091125 grub fails at startup with: error: grub_gettext not found Hi, I don't think we have any routine in our code that could possibly construct that error string. Could you re-check that this is *exactly* what it is printing? -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558312: error: grub_gettext not found
Hi, On Fri, Nov 27, 2009 at 10:00:38PM +0100, Robert Millan wrote: I don't think we have any routine in our code that could possibly construct that error string. Could you re-check that this is *exactly* what it is printing? Sorry. The exact message is: error: the symbol ``grub_gettext'' not found It's also displayed on grub_rescue mode when trying to insmod normal.mod or configfile.mod. My locale is es_AR.UTF-8. Thanks -- Fernando M. Maresca - - - - - - - - - - - - - Cel: 221 15 545 8196 Tel: 221 450 5378 signature.asc Description: Digital signature
Bug#558312: error: grub_gettext not found
tags 558312 -unreproducible thanks Fernando M. Maresca wrote: Hi, On Fri, Nov 27, 2009 at 10:00:38PM +0100, Robert Millan wrote: I don't think we have any routine in our code that could possibly construct that error string. Could you re-check that this is *exactly* what it is printing? Sorry. The exact message is: error: the symbol ``grub_gettext'' not found It's also displayed on grub_rescue mode when trying to insmod normal.mod or configfile.mod. My locale is es_AR.UTF-8. I can reproduce the problem, I get the exact same error message and boot failure. My locale is de_DE.UTF-8 fwiw, I noticed that grub.cfg references a directory /boot/grub/locale but I don't have such a directory. Maybe this is related. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#558312: error: grub_gettext not found
Am Freitag, den 27.11.2009, 22:51 +0100 schrieb Michael Biebl:
tags 558312 -unreproducible
thanks
Fernando M. Maresca wrote:
Hi,
On Fri, Nov 27, 2009 at 10:00:38PM +0100, Robert Millan wrote:
I don't think we have any routine in our code that could possibly
construct
that error string. Could you re-check that this is *exactly* what
it is
printing?
Sorry.
The exact message is:
error: the symbol ``grub_gettext'' not found
It's also displayed on grub_rescue mode when trying to insmod
normal.mod or configfile.mod.
My locale is es_AR.UTF-8.
I can reproduce the problem, I get the exact same error message and
boot failure.
As Robert just sent a few minutes ago in his -done mail, the problem is
that grub-install was run on a device where you currently don't boot
from.
That can happen if you choose only one device instead of all in the
grub-pc/install_devices debconf prompt and then on this package upgrade
the Linux kernel somehow decides to name the devices differently then
last time.
The only safe way currently is to just choose all devices in that
debconf prompt.
Hopefully we get to implement some /dev/disk/by-{id,uuid} for that one,
so it's consistent.
My locale is de_DE.UTF-8
fwiw, I noticed that grub.cfg references a directory /boot/grub/locale
but I
don't have such a directory. Maybe this is related.
No it isn't. It's just ignored that it doestn't exist.
Cheers,
Michael
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
Bug#558312: error: grub_gettext not found
Felix Zielcke wrote:
Am Freitag, den 27.11.2009, 22:51 +0100 schrieb Michael Biebl:
tags 558312 -unreproducible
thanks
Fernando M. Maresca wrote:
Hi,
On Fri, Nov 27, 2009 at 10:00:38PM +0100, Robert Millan wrote:
I don't think we have any routine in our code that could possibly
construct
that error string. Could you re-check that this is *exactly* what
it is
printing?
Sorry.
The exact message is:
error: the symbol ``grub_gettext'' not found
It's also displayed on grub_rescue mode when trying to insmod
normal.mod or configfile.mod.
My locale is es_AR.UTF-8.
I can reproduce the problem, I get the exact same error message and
boot failure.
As Robert just sent a few minutes ago in his -done mail, the problem is
that grub-install was run on a device where you currently don't boot
from.
That can happen if you choose only one device instead of all in the
grub-pc/install_devices debconf prompt and then on this package upgrade
the Linux kernel somehow decides to name the devices differently then
last time.
The only safe way currently is to just choose all devices in that
debconf prompt.
Hopefully we get to implement some /dev/disk/by-{id,uuid} for that one,
so it's consistent.
Well, this does not seem to apply to me.
I have a single / partition, where I booted my Debian from, did a grub update
and on the next boot grub was broken.
I had no debconf prompt, no booting from a separate partition, any of this.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#558312: error: grub_gettext not found
Am Freitag, den 27.11.2009, 23:04 +0100 schrieb Michael Biebl:
Felix Zielcke wrote:
Am Freitag, den 27.11.2009, 22:51 +0100 schrieb Michael Biebl:
tags 558312 -unreproducible
thanks
Fernando M. Maresca wrote:
Hi,
On Fri, Nov 27, 2009 at 10:00:38PM +0100, Robert Millan wrote:
I don't think we have any routine in our code that could possibly
construct
that error string. Could you re-check that this is *exactly*
what
it is
printing?
Sorry.
The exact message is:
error: the symbol ``grub_gettext'' not found
It's also displayed on grub_rescue mode when trying to insmod
normal.mod or configfile.mod.
My locale is es_AR.UTF-8.
I can reproduce the problem, I get the exact same error message and
boot failure.
As Robert just sent a few minutes ago in his -done mail, the problem
is
that grub-install was run on a device where you currently don't boot
from.
That can happen if you choose only one device instead of all in the
grub-pc/install_devices debconf prompt and then on this package
upgrade
the Linux kernel somehow decides to name the devices differently
then
last time.
The only safe way currently is to just choose all devices in that
debconf prompt.
Hopefully we get to implement some /dev/disk/by-{id,uuid} for that
one,
so it's consistent.
Well, this does not seem to apply to me.
I have a single / partition, where I booted my Debian from, did a grub
update
and on the next boot grub was broken.
I had no debconf prompt, no booting from a separate partition, any of
this.
What does `echo GET grub-pc/install_devices | debconf-communicate' show?
I just tried it out in a vm.
Installed squeeze beta3-1 where grub-pc/install_devices is not set at
all. Then ran grub-install /dev/sda. Rebooted. Then upgraded to current
sid version. Not running grub-install and neither it was ran by the
postinst.
And a reboot worked still fine.
Cheers,
Michael
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
Bug#558312: error: grub_gettext not found
Felix Zielcke wrote:
Am Freitag, den 27.11.2009, 23:04 +0100 schrieb Michael Biebl:
Felix Zielcke wrote:
Am Freitag, den 27.11.2009, 22:51 +0100 schrieb Michael Biebl:
tags 558312 -unreproducible
thanks
Fernando M. Maresca wrote:
Hi,
On Fri, Nov 27, 2009 at 10:00:38PM +0100, Robert Millan wrote:
I don't think we have any routine in our code that could possibly
construct
that error string. Could you re-check that this is *exactly*
what
it is
printing?
Sorry.
The exact message is:
error: the symbol ``grub_gettext'' not found
It's also displayed on grub_rescue mode when trying to insmod
normal.mod or configfile.mod.
My locale is es_AR.UTF-8.
I can reproduce the problem, I get the exact same error message and
boot failure.
As Robert just sent a few minutes ago in his -done mail, the problem
is
that grub-install was run on a device where you currently don't boot
from.
That can happen if you choose only one device instead of all in the
grub-pc/install_devices debconf prompt and then on this package
upgrade
the Linux kernel somehow decides to name the devices differently
then
last time.
The only safe way currently is to just choose all devices in that
debconf prompt.
Hopefully we get to implement some /dev/disk/by-{id,uuid} for that
one,
so it's consistent.
Well, this does not seem to apply to me.
I have a single / partition, where I booted my Debian from, did a grub
update
and on the next boot grub was broken.
I had no debconf prompt, no booting from a separate partition, any of
this.
What does `echo GET grub-pc/install_devices | debconf-communicate' show?
I just tried it out in a vm.
Installed squeeze beta3-1 where grub-pc/install_devices is not set at
all. Then ran grub-install /dev/sda. Rebooted. Then upgraded to current
sid version. Not running grub-install and neither it was ran by the
postinst.
And a reboot worked still fine.
I had purged and reinstalled grub in between and I can't reproduce the problem
anymore.
Nonetheless, if I understand you resp. Robert correctly, it is no longer
possible to boot from a rescue disc, mount the root partition manually, do a
chroot and do a grub-install? That would be very unfortunate. Or did I misread
Roberts answer?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
