Debian Bug report logs - #588370
symbol not found: 'grub_xputs'

Package: grub2; Maintainer for grub2 is GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>; Source for grub2 is src:grub2.

Reported by: Martin Bagge / brother <brother@bsnet.se>

Date: Wed, 7 Jul 2010 19:30:01 UTC

Severity: critical

Done: Martin Bagge / brother <brother@bsnet.se>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#588370; Package grub2. (Wed, 07 Jul 2010 19:30:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Martin Bagge / brother <brother@bsnet.se>:
New Bug report received and forwarded. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Wed, 07 Jul 2010 19:30:04 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Martin Bagge / brother <brother@bsnet.se>
To: submit@bugs.debian.org
Subject: symbol not found: 'grub_xputs'
Date: Wed, 7 Jul 2010 21:27:25 +0200 (CEST)
severity: critical
package: grub2

I am not sure but I do think I did a dist-upgrade in sid and installd 
grub2 to replace the old solution. I haven't used the computer for some 
days now
but it can not boot anymore.

Right after "Welcome to grub!" it drops to the grub rescue prompt.
I can list my drives with ls.
I can set root to hd0,1 and list the file system for / as far as I can 
tell.
When doing insmod /boot/grub/linux.mod I get the grub_xputs error above.

What to do?


found some livecd suggestion at #grub at freenode and will try to test 
that during the coming week.
http://grub.enbug.org/Grub2LiveCdInstallGuide




Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#588370; Package grub2. (Thu, 08 Jul 2010 08:15:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Pier <pierg75@yahoo.it>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Thu, 08 Jul 2010 08:15:02 GMT) Full text and rfc822 format available.

Message #10 received at 588370@bugs.debian.org (full text, mbox):

From: Pier <pierg75@yahoo.it>
To: 588370@bugs.debian.org
Subject: bug grub2
Date: Thu, 8 Jul 2010 01:10:40 -0700 (PDT)
I got the same error.
I tried to reinstall grub, without success.
I tried to start with a debian live cd and chroot in the /.
Reconfigured grub, i always get grub_xputs.
My system is a amd64 (sorry cannot mail from my system, is unusable).

Pier









Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#588370; Package grub2. (Thu, 08 Jul 2010 10:33:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Thu, 08 Jul 2010 10:33:03 GMT) Full text and rfc822 format available.

Message #15 received at 588370@bugs.debian.org (full text, mbox):

From: Colin Watson <cjwatson@debian.org>
To: Martin Bagge / brother <brother@bsnet.se>, 588370@bugs.debian.org
Subject: Re: Bug#588370: symbol not found: 'grub_xputs'
Date: Thu, 8 Jul 2010 11:31:41 +0100
On Wed, Jul 07, 2010 at 09:27:25PM +0200, Martin Bagge / brother wrote:
> I am not sure but I do think I did a dist-upgrade in sid and installd
> grub2 to replace the old solution. I haven't used the computer for
> some days now but it can not boot anymore.
>
> Right after "Welcome to grub!" it drops to the grub rescue prompt.
> I can list my drives with ls.
> I can set root to hd0,1 and list the file system for / as far as I can  
> tell.
> When doing insmod /boot/grub/linux.mod I get the grub_xputs error above.

This means that your GRUB core image, as installed by grub-install, and
your GRUB modules in /boot/grub are out of sync.  This happens when you
grub-install to a location other than that from which your computer
actually boots.

Please show the output of:

  debconf-show grub-pc
  fdisk -l

-- 
Colin Watson                                       [cjwatson@debian.org]




Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#588370; Package grub2. (Thu, 08 Jul 2010 10:36:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Thu, 08 Jul 2010 10:36:05 GMT) Full text and rfc822 format available.

Message #20 received at 588370@bugs.debian.org (full text, mbox):

From: Colin Watson <cjwatson@debian.org>
To: Pier <pierg75@yahoo.it>, 588370@bugs.debian.org
Subject: Re: Bug#588370: bug grub2
Date: Thu, 8 Jul 2010 11:32:46 +0100
On Thu, Jul 08, 2010 at 01:10:40AM -0700, Pier wrote:
> I got the same error.

Please file a separate bug, Severity: normal, attaching the output of
'debconf-show grub-pc' and 'fdisk -l' from this system.

(I'm getting too old to attempt to debug multiple people's problems in
the same bug report, even if they have similar symptoms.)

-- 
Colin Watson                                       [cjwatson@debian.org]




Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#588370; Package grub2. (Fri, 09 Jul 2010 07:51:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Michael <codejodler@gmx.ch>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Fri, 09 Jul 2010 07:51:02 GMT) Full text and rfc822 format available.

Message #25 received at 588370@bugs.debian.org (full text, mbox):

From: Michael <codejodler@gmx.ch>
To: 588370@bugs.debian.org
Cc: cjwatson@debian.org
Subject: (#588370) symbol not found: 'grub_xputs'
Date: Fri, 9 Jul 2010 09:49:30 +0200
Colin,

> debconf-show grub-pc

Look not everyone is a geek. At least you could have told Martin how he could have done this (via the proper boot-cd and chroot). But then, why not just telling him how to fix it in the first place ?

> This happens when you grub-install to a location other than that from which your computer
> actually boots.

I had the same incident after a regular weekly update, yesterday. I did not change any setting or anything. It just didn't work anymore. This is sid of course...

I was able to resolve the problem by burning a debian netinstall amd64 'testing' boot cd from the debian installer homepage, on my laptop. After booting it i chose rescue mode,  and reinstall bootloader. Then i entered a root shell (still on the cd filesystem), mounted my harddisk / and exchanged the /boot/grub folder. Because if i didn't do that it still wouldn't boot. I tried it.
Then rebooted and switched the harddisk grub into 'edit' mode ('ESC' -> 'e') and then edited the kernel image and initrd version numbers (which were still from the other system) to have them fit to the harddisk ones. I booted regularly, removed the /boot/grub folder again and reinstalled grub from within the main system.
  
I believe there must be an easier solution. Actually, i did not tell you the whole story (an outdated harddisk rescue system was involved) to make it short.

I just wanted to give you a hint how many complex things could be involved to fix such an issue.
I know a package maintainer is not supposed to give support on a bug tracker. But this is a special case, it's a 'super-critical' bug. I would even introduce this category for this kind of bugs. And people easily feel left in the dark by the debian project if the debian package system breaks their computer. Wouldn't it be appropriate to offer immediate help, instead of asking for extra data and send people to file another bug report ? At least, you could tell them a proper mailing list.

/ r: debconf-show grub-pc
  grub2/kfreebsd_cmdline:
* grub2/device_map_regenerated:
* grub2/linux_cmdline:
  grub-pc/install_devices_empty: false
  grub-pc/install_devices_failed: false
* grub-pc/chainload_from_menu.lst: true
  grub-pc/kopt_extracted: true
* grub-pc/install_devices: /dev/disk/by-id/ata-ST3320620AS_5QF1HAVQ
  grub-pc/postrm_purge_boot_grub: false
  grub-pc/install_devices_failed_upgrade: true
  grub-pc/disk_description:
  grub2/kfreebsd_cmdline_default: quiet
  grub-pc/partition_description:
  grub-pc/install_devices_disks_changed:
* grub2/linux_cmdline_default:
  grub-pc/mixed_legacy_and_grub2: true

This is still the same grub package as before, reinstallation just used the cached version. Isn't it strange it works now again ? I will try to do some more tests later.

OS is Linux 2.6.32-4-amd64. The update was done under 2.6.32-5 but i didn't boot into that again right now. I will try this next. 2.6.32-5 was running for quite some weeks before, though, with several updates w/o problems.

/ r: fdisk -l

This looks complicated but in a nutshell, there are 2 different systems (main and rescue) and some media and backup partitions on 3 harddisks but i did run only the main one for some months, with weekly updates. The main system has /boot as folder in / (but some complicated other mountpoints which i believe do not matter here).

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005bd28

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       12158    97659103+  83  Linux
/dev/sda2           12159       38913   214909537+   5  Extended
/dev/sda5           12159       18237    48829536   83  Linux
/dev/sda6           18238       24316    48829536   83  Linux
/dev/sda7           24317       26748    19535008+  83  Linux
/dev/sda8           26749       27964     9767488+  83  Linux
/dev/sda9           27965       28450     3903763+  83  Linux
/dev/sda10  *       28451       30882    19535008+  83  Linux
/dev/sda11          30883       31368     3903763+  82  Linux swap / Solaris
/dev/sda12          31369       32584     9767488+  83  Linux
/dev/sda13          32585       33800     9767488+  83  Linux
/dev/sda14          33801       38906    41013913+  83  Linux
/dev/sda15          38907       38913       56196   83  Linux

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00092098

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       29792   239304208+  83  Linux
/dev/sdb2   *       29793       30401     4891792+  82  Linux swap / Solaris

Disk /dev/sdc: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xffffffff

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       20668   166015678+  83  Linux
/dev/sdc2           20669       32827    97667167+  83  Linux
/dev/sdc3           32828       36477    29318625    5  Extended
/dev/sdc4   *       36478       38913    19567170   83  Linux
/dev/sdc5           32828       36477    29318593+  83  Linux

hth mi









Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#588370; Package grub2. (Fri, 09 Jul 2010 09:09:08 GMT) Full text and rfc822 format available.

Acknowledgement sent to Colin Watson <cjwatson@debian.org>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Fri, 09 Jul 2010 09:09:08 GMT) Full text and rfc822 format available.

Message #30 received at 588370@bugs.debian.org (full text, mbox):

From: Colin Watson <cjwatson@debian.org>
To: Michael <codejodler@gmx.ch>
Cc: 588370@bugs.debian.org
Subject: Re: (#588370) symbol not found: 'grub_xputs'
Date: Fri, 9 Jul 2010 10:08:38 +0100
On Fri, Jul 09, 2010 at 09:49:30AM +0200, Michael wrote:
> Colin,
> 
> > debconf-show grub-pc
> 
> Look not everyone is a geek. At least you could have told Martin how
> he could have done this (via the proper boot-cd and chroot).

Martin already referred to the live CD instructions in his original
report.

> But then, why not just telling him how to fix it in the first place ?

Because I don't know the proper fix until I diagnose what's happening on
his system!  Would you also ask that a doctor prescribe medication
before finding out what's wrong?

> > This happens when you grub-install to a location other than that from which your computer
> > actually boots.
> 
> I had the same incident after a regular weekly update, yesterday. I
> did not change any setting or anything. It just didn't work anymore.
> This is sid of course...

Could you also please file a separate bug report?  I'm happy to
investigate people's problems, but I can't keep track of lots of
different people's problems when they're all bundled together into a
single bug report.  And yes, I know that the symptoms are the same, but
all this symptom means is "the GRUB core image and its modules have got
out of sync" - there are several different possible causes for it.

> I just wanted to give you a hint how many complex things could be
> involved to fix such an issue.
> I know a package maintainer is not supposed to give support on a bug
> tracker.

I'm entirely happy to give support in bug reports when it seems likely
that it can result in improvements to the software.

> But this is a special case, it's a 'super-critical' bug. I would even
> introduce this category for this kind of bugs.

Ah yes, escalation always helps ... do you believe that I'm dealing with
these problems more slowly because they aren't filed at a high enough
priority?  They all land in my inbox just the same way, and I'm dealing
with them all as fast as I can.

> And people easily feel left in the dark by the debian project if the
> debian package system breaks their computer. Wouldn't it be
> appropriate to offer immediate help, instead of asking for extra data
> and send people to file another bug report ?

No, it wouldn't, because I *cannot provide help until I know what's
wrong*.  Please don't second-guess me on this - it consumes extra time
that I could be using to help people.

> At least, you could tell them a proper mailing list.

Bug reports are fine.  I just don't want to have to deal with multiple
different problems in a single bug report.  It is not helpful to anyone
that way - it confuses users who happen upon the bug later just as much
as it confuses me.

> * grub-pc/install_devices: /dev/disk/by-id/ata-ST3320620AS_5QF1HAVQ

The likely cause is that you selected a disk here which isn't the one
that your BIOS is actually booting from.  Since you have three disks,
this is quite plausible.  'dpkg-reconfigure grub-pc' and select all
three disks.

(This can't be done by default because then a different set of people
would have problems - that's why the current dialog structure doesn't
let you proceed until you take an active decision.)

Regards,

-- 
Colin Watson                                       [cjwatson@debian.org]




Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#588370; Package grub2. (Fri, 09 Jul 2010 09:54:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Michael <earlymorning@gmx.ch>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Fri, 09 Jul 2010 09:54:06 GMT) Full text and rfc822 format available.

Message #35 received at 588370@bugs.debian.org (full text, mbox):

From: Michael <earlymorning@gmx.ch>
To: 588370@bugs.debian.org
Cc: Colin Watson <cjwatson@debian.org>
Subject: Re: (#588370) symbol not found: 'grub_xputs'
Date: Fri, 9 Jul 2010 11:50:43 +0200
Colin,

thank you - i believe you found the reason.

> > * grub-pc/install_devices: /dev/disk/by-id/ata-ST3320620AS_5QF1HAVQ
> 
> The likely cause is that you selected a disk here which isn't the one
> that your BIOS is actually booting from.  Since you have three disks,
> this is quite plausible.  'dpkg-reconfigure grub-pc' and select all
> three disks.

Actually the debconf dialog had sdc checked where i had sda before. 
But i did not see this dialog at any point before !
Or maybe a long time ago so that i already forgot about it. But usually i do not forget such important things. Well i have some very loaded months behind me.

So what can i remember.

At the time when i upgraded to grub2, i had only 2 disks but and in different SATA channels. I modified that all later, including some partitioning. Later again there was that official move to device IDs in fstab, which i accepted and it went ok. Some 2 weeks ago however, i decided to ditch that fstab design again in favor for more human partition labels, just using tune2fs and editing fstab manually.

I can not figure how that could have confused things. Or maybe debconf was preconfigured and did not detect my last changes somehow. So that the database somehow was not up-to-date anymore, and by using the preconfigured defaults (and maybe relying on the device IDs now) it installed grub with the wrong parameters ?





Information forwarded to debian-bugs-dist@lists.debian.org, GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>:
Bug#588370; Package grub2. (Thu, 15 Jul 2010 13:18:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Martin Bagge / brother <brother@bsnet.se>:
Extra info received and forwarded to list. Copy sent to GRUB Maintainers <pkg-grub-devel@lists.alioth.debian.org>. (Thu, 15 Jul 2010 13:18:03 GMT) Full text and rfc822 format available.

Message #40 received at 588370@bugs.debian.org (full text, mbox):

From: Martin Bagge / brother <brother@bsnet.se>
To: Colin Watson <cjwatson@debian.org>
Cc: 588370@bugs.debian.org
Subject: Re: Bug#588370: symbol not found: 'grub_xputs'
Date: Thu, 15 Jul 2010 14:51:34 +0200
On 2010-07-08 12:31, Colin Watson wrote:
> This means that your GRUB core image, as installed by grub-install, and
> your GRUB modules in /boot/grub are out of sync.  This happens when you
> grub-install to a location other than that from which your computer
> actually boots.

I did manage to get a CD to burn the Live image of ubuntu to and using
that to create the chroot as described in the link I found earlier. It
all worked after that.

Sorry to bother.

-- 
brother
http://sis.bthstudent.se




Reply sent to Martin Bagge / brother <brother@bsnet.se>:
You have taken responsibility. (Thu, 15 Jul 2010 13:18:07 GMT) Full text and rfc822 format available.

Notification sent to Martin Bagge / brother <brother@bsnet.se>:
Bug acknowledged by developer. (Thu, 15 Jul 2010 13:18:08 GMT) Full text and rfc822 format available.

Message #45 received at 588370-done@bugs.debian.org (full text, mbox):

From: Martin Bagge / brother <brother@bsnet.se>
To: 588370-done@bugs.debian.org
Subject: Re: Bug#588370: symbol not found: 'grub_xputs'
Date: Thu, 15 Jul 2010 14:52:07 +0200
thanks.
Workaround in earlier message.
-- 
brother
http://sis.bthstudent.se




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Fri, 13 Aug 2010 07:38:02 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sun Apr 20 21:07:19 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.