Comment 1 for bug 428785

Am Sonntag, den 13.09.2009, 10:13 +0000 schrieb Rotbart van Dainig:
> Public bug reported:
>
> grub-mkconfig and subsequently, update-grub simply stop to run after
> adding the memtest entry if there are LUKS partitions on the system,
> thus making any update including kernel and grub updates stop - no
> matter if done via Synaptics or apt-get:
>
> Generating grub.cfg ...
> Found linux image: /boot/vmlinuz-2.6.31-10-generic
> Found initrd image: /boot/initrd.img-2.6.31-10-generic
> Found linux image: /boot/vmlinuz-2.6.31-9-generic
> Found initrd image: /boot/initrd.img-2.6.31-9-generic
> Found memtest86+ image: /boot/memtest86+.bin
> --> stop
>
> On manual grub-mkconfig or update-grub, hitting Enter multiple times
> will finish the update:
>
> $ sudo update-grub
> Generating grub.cfg ...
> Found linux image: /boot/vmlinuz-2.6.31-10-generic
> Found initrd image: /boot/initrd.img-2.6.31-10-generic
> Found linux image: /boot/vmlinuz-2.6.31-9-generic
> Found initrd image: /boot/initrd.img-2.6.31-9-generic
> Found memtest86+ image: /boot/memtest86+.bin
> Found on Password
> is not yet supported by grub-mkconfig.
> Found on Password
> is not yet supported by grub-mkconfig.
> done
>
> This is no option when running Synaptics or apt-get, though, as Enter doesn't penetrate the package install script layer - the only option is to cancel the package install script with CTRL-C.
> However, that causes the grub package to be marked as partially installed, and subsequently, any update/install will trigger the package install scripts of the grub package, leading to te aformentioned problems... meaning that updates always require manual intervention.
>

Please run sudo os-prober, if that has the same problem.
I think it's more caused by os-prober then grub-mkconfig or more
specific grub-probe

--
Felix Zielcke
Proud Debian Maintainer