On Monday 28 June 2010 16:49:09 Colin Watson wrote:
> Sounds like #542165, or possibly #550704. Could you please try the
> version of grub-common and grub-pc in unstable?
>
> If that doesn't help, please show me the output of:
>
> cat /boot/grub/device.map
> sh -x /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg
>
I confirm that I get this bug too. And yes, it seems to be #550704, and
installing grub from unstable fixes this.
On a side note, /usr/sbin/grub-mkconfig starts with "#!/bin/sh -e", and
running the command you suggested (without additional -e) succeeds, creating a
broken grub.cfg:
====
[...]
++ /usr/sbin/grub-probe --target=device /
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
+ GRUB_DEVICE=
[...]
====
====
menuentry "Debian GNU/Linux, with Linux 2.6.32-5-amd64" --class debian --class
gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set
80387b58-47f2-461f-9c6b-41eb95463bdd
echo Loading Linux 2.6.32-5-amd64 ...
linux /vmlinuz-2.6.32-5-amd64 root= ro
echo Loading initial ramdisk ...
initrd /initrd.img-2.6.32-5-amd64
}
====
(Note the empty "root=" in kernel cmdline).
So is there any reason for not using set -e in grub-mkconfig, or should
another (wishlist?) bug be filed about this?
--
Vadim Solomin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
