Bug#549627: grub: similar problems

[Felix Zielcke]

Am Freitag, den 09.10.2009, 22:45 +0200 schrieb Friedrich Delgado
Friedrichs:
> Package: grub
> Version: 0.97-58
> Severity: normal
> 
> Hi.
> 
> I'm not really sure if this is the same bug.
> 
> Most of the description seems to fit what I see. I can't configure
> linux-image-2.6.30-2-amd64 on my system:
> 
> I get the following error:

> Running update-grub.
> Generating grub.cfg ...
> User postinst hook script [update-grub] exited with value 139
> 
> Maybe it's a different error, I get return value 139 instead of 1, but
> the same error message from update-initramfs, however update-grub
> doesn't complain about not finding my drives.
> 
> Disk setup:
> 
> root at abrasax:~# df -h
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/mapper/lvm-root  1.8T  830G  959G  47% /
> tmpfs                 754M     0  754M   0% /lib/init/rw
> udev                   10M  172K  9.9M   2% /dev
> tmpfs                 754M     0  754M   0% /dev/shm
> /dev/sda1             1.9G  164M  1.6G  10% /boot
> root at abrasax:~# grub-probe -d /dev/mapper/lvm-root
> ext2
> root at abrasax:~# grub-probe -d /dev/sda1
> ext2

It would have been better if you have made a seperate bug report for
this.
Anyway I fixed this now by cloning the report and setting you as
submitter. And also properly reassigned both reports to grub-common
where this belongs to.

The relevant part here is the update-grub output and the exit code of
it.
139 in update-grub is very strange to me.

In the /etc/grub.d/* files either change the first line of them from
`#! /bin/sh -e' to `#! /bin/sh -ex' or you can write `set -x' in the
line after it.
40_custom can be skipped if you didn't modify it.
Then run update-grub, it should tell now which command fails.

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer