grub-mkconfig stops on encrypted partitions

Bug #428785 reported by Rotbart van Dainig
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
os-prober (Debian)
Fix Released
Unknown
os-prober (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

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.

Revision history for this message
Felix Zielcke (fzielcke) wrote : Re: [Bug 428785] [NEW] grub-mkconfig stops on encrypted partitions

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

Revision history for this message
Rotbart van Dainig (rotbart-van-dainig) wrote :

> 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

You are correct, os-prober asks for passwords, twice.

$ sudo os-prober
Password:
Password:

Felix Zielcke (fzielcke)
affects: grub2 (Ubuntu) → os-prober (Ubuntu)
Changed in os-prober (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package os-prober - 1.33

---------------
os-prober (1.33) unstable; urgency=low

  * Distinguish Windows 7, based on a patch from "mattduckman"
    (LP: #393565).
  * Don't try to mount LUKS partitions (thanks, Chow Loong Jin and Soren
    Hansen; closes: #546546, LP: #428785).

 -- Colin Watson <email address hidden> Tue, 15 Sep 2009 14:20:08 +0100

Changed in os-prober (Ubuntu):
status: New → Fix Released
Changed in os-prober (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.