Your message dated Sat, 18 May 2019 19:22:50 +0100 with message-id <18052019192054.8c06a50e42ca@desktop.copernicus.org.uk> and subject line Re: Bug#650819: grub-installer: The contents of grub.cfg depend on the kernel installed has caused the Debian Bug report #650819, regarding grub-installer: The contents of grub.cfg depend on the kernel installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 650819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650819 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: grub-installer: The contents of grub.cfg depend on the kernel installed
- From: Brian Potkin <claremont102@gmail.com>
- Date: Sat, 3 Dec 2011 14:08:21 +0000
- Message-id: <20111203140820.GA27312@desktop>
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 dataAttachment: syslog-686-pae.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: 650819-close@bugs.debian.org
- Subject: Re: Bug#650819: grub-installer: The contents of grub.cfg depend on the kernel installed
- From: Brian Potkin <claremont102@gmail.com>
- Date: Sat, 18 May 2019 19:22:50 +0100
- Message-id: <18052019192054.8c06a50e42ca@desktop.copernicus.org.uk>
- In-reply-to: <20111203140820.GA27312@desktop>
- References: <20111203140820.GA27312@desktop>
X-CrossAssassin-Score: 8030
--- End Message ---