[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#650819: grub-installer: The contents of grub.cfg depend on the kernel installed



Package: grub-installer
Severity: normal


This is using today's daily build #1 for i386. The install was to a USB
stick (/dev/sdc) on a machine with one IDE drive carrying a Wheezy
install with two kernels. The result was the same installing to either
drive of a two SATA disk machine.

In short: the 30_os-prober section of grub.cfg is empty when the kernel
installed is linux-image-686-pae but correctly written when
linux-image-486 is used.

Attached are syslog-486 and syslog-686-pae. Both start at the point menu
item 'grub-installer' was selected.


brian@desktop:/media/sdd2$ grep ": result" syslog-486 
Dec  3 12:18:42 90linux-distro: result: /dev/sda1:Debian GNU/Linux (wheezy/sid):Debian:linux
Dec  3 12:18:43 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.1.0-1-686-pae:/boot/vmlinuz-3.1.0-1-686-pae:/boot/initrd.img-3.1.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10
Dec  3 12:18:43 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.0.0-1-686-pae:/boot/vmlinuz-3.0.0-1-686-pae:/boot/initrd.img-3.0.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10
Dec  3 12:20:44 90linux-distro: result: /dev/sda1:Debian GNU/Linux (wheezy/sid):Debian:linux
Dec  3 12:20:46 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.1.0-1-686-pae:/boot/vmlinuz-3.1.0-1-686-pae:/boot/initrd.img-3.1.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10
Dec  3 12:20:46 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.0.0-1-686-pae:/boot/vmlinuz-3.0.0-1-686-pae:/boot/initrd.img-3.0.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10
Dec  3 12:20:49 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.1.0-1-686-pae:/boot/vmlinuz-3.1.0-1-686-pae:/boot/initrd.img-3.1.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10
Dec  3 12:20:49 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.0.0-1-686-pae:/boot/vmlinuz-3.0.0-1-686-pae:/boot/initrd.img-3.0.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10


brian@desktop:/media/sdd2$ grep ": result" syslog-686-pae 
Dec  3 11:54:49 90linux-distro: result: /dev/sda1:Debian GNU/Linux (wheezy/sid):Debian:linux
Dec  3 11:54:49 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.1.0-1-686-pae:/boot/vmlinuz-3.1.0-1-686-pae:/boot/initrd.img-3.1.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10
Dec  3 11:54:49 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.0.0-1-686-pae:/boot/vmlinuz-3.0.0-1-686-pae:/boot/initrd.img-3.0.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10
Dec  3 11:56:50 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.1.0-1-686-pae:/boot/vmlinuz-3.1.0-1-686-pae:/boot/initrd.img-3.1.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10
Dec  3 11:56:50 40grub2: result: /dev/sda1:/dev/sda1:Debian GNU/Linux, with Linux
3.0.0-1-686-pae:/boot/vmlinuz-3.0.0-1-686-pae:/boot/initrd.img-3.0.0-1-686-pae:root=UUID=cb83bfa2-57b7-4312-abb1-b0fc2fb7588a ro video=VGA-1:1280x1024 video=TV-1:1280x10


With linux-image-686-pae it appears update-grub does not pick up the
kernels on /dev/sda when chrooted to /target. Additionally, the lines

Dec  3 11:56:49 50mounted-tests: warning: failed to umount /var/lib/os-prober/mount
Dec  3 11:56:50 50mounted-tests: warning: failed to umount /var/lib/os-prober/mount

are in syslog-686-pae but not in syslog-486.


Attachment: syslog-486.gz
Description: Binary data

Attachment: syslog-686-pae.gz
Description: Binary data


Reply to: