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

[Karsten Malcher]

Am 14.01.2014 19:00, schrieb Colin Watson:
> 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? 

Hello Colin,

now i understand more.
I found this description of os-prober here:
http://joeyh.name/code/os-prober/

Calling os-prober only give this information:
# os-prober
/dev/sda2:Debian GNU/Linux (7.2):Debian:linux
/dev/sda3:Debian GNU/Linux (jessie/sid):Debian1:linux


It seems not to merge the information with the UUID of the partitions.
I found an other interesting effect, which explains that this bug has not been found.
Now an grub-update produces the correct grub.cfg.


menuentry "Debian GNU/Linux, mit Linux 3.12-1-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.12-1-amd64 root=UUID=6bfc15a0-2e9d-4020-9346-9fd52d2696f5 ro quiet
         initrd /boot/initrd.img-3.12-1-amd64
}
menuentry "Debian GNU/Linux, mit Linux 3.12-1-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.12-1-amd64 root=UUID=6bfc15a0-2e9d-4020-9346-9fd52d2696f5 ro single
         initrd /boot/initrd.img-3.12-1-amd64
}

What i did in the history:
1. I unpacked an backup of /dev/sdb1 (Grub partition with Debian wheezy) to /dev/sda3
2. I altered the fstab of the copy and run update-grub (After this i got this wrong grub.cfg)
3. I boot from /dev/sda3 and made an system-upgrade from wheezy to jessie
4. After the upgrade i run update-grub again from /dev/sdb1 to actualize the new kernel on /dev/sda3 (Now grub.cfg is 
correct)

Is it possible that the (wrong) information is extraced from initrd.img ?

Cheers
Karsten