Bug#686754: Is there any hope that this bug will be fixed?

[Colin Watson]

On Tue, Jan 14, 2014 at 09:03:49AM +0100, Karsten Malcher wrote:
> menuentry "Debian GNU/Linux, mit Linux 3.2.0-3-amd64 (on /dev/sda3)" --class gnu-linux --class gnu --class os {
>     insmod part_msdos
>     insmod ext2
>     set root='(/dev/sda,msdos3)'
>     search --no-floppy --fs-uuid --set=root 6bfc15a0-2e9d-4020-9346-9fd52d2696f5
>     linux /boot/vmlinuz-3.2.0-3-amd64 root=UUID=5c902625-e63e-446f-a5c5-c24a1176dec7 ro quiet
>     initrd /boot/initrd.img-3.2.0-3-amd64
> }
> menuentry "Debian GNU/Linux, mit Linux 3.2.0-3-amd64
> (Wiederherstellungsmodus) (on /dev/sda3)" --class gnu-linux --class
> gnu --class os {
>     insmod part_msdos
>     insmod ext2
>     set root='(/dev/sda,msdos3)'
>     search --no-floppy --fs-uuid --set=root 6bfc15a0-2e9d-4020-9346-9fd52d2696f5
>     linux /boot/vmlinuz-3.2.0-3-amd64 root=UUID=5c902625-e63e-446f-a5c5-c24a1176dec7 ro single
>     initrd /boot/initrd.img-3.2.0-3-amd64

GRUB doesn't generate those kernel parameters itself; it relies on
os-prober to fetch them from the boot loader configuration files on
those other systems.  It's quite possible that the problem is simply
that the boot loader configuration inside the filesystem on /dev/sda3
(or its associated /boot filesystem) is wrong.  Could you find the
relevant configuration file and attach it?

-- 
Colin Watson                                       [cjwatson at debian.org]