Your message dated Fri, 27 Nov 2009 22:45:44 +0100
with message-id <20091127214544.ga5...@thorin>
and subject line Re: Bug#558312: error: grub_gettext not found
has caused the Debian Bug report #558312,
regarding error: grub_gettext not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
558312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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:



--- End Message ---
--- Begin Message ---
On Fri, Nov 27, 2009 at 06:15:26PM -0300, 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

Hi,

There's no bug here.  You installed different versions of GRUB to different
drives using the same /boot/grub/.  One of them stopped booting because of
ABI incompatibility.

Just tell the debconf template to install GRUB to each drive and you'll be ok.

-- 
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."


--- End Message ---

Reply via email to