It seems like this bug is related to GRUB lacking LUKS2 support. Back
in buster, GRUB only supported LUKS1, so this bug could only be worked-
around by using LUKS1 for /boot.
Now GRUB has some support for LUKS2 at boot time, but grub-probe
doesn't recognise LUKS2 devices properly so the necessary
For what it's worth, I am unable to reproduce it on the latest weekly build of
Bullseye. Paolo, are you OK for this bug to be closed?
--
Regards,
A
Hi Mark and all,
I'm in the same situation. So what do we do ?
Thx
On Thu, 4 Jul 2019 18:34:01 +0200 Mark Caglienzi
wrote:
> Hi all,
> is this bug relevant yet?
>
> I have a buster laptop (so no VM, but real hardware, and no fresh
> install) with encrypted disk, and I blocked the upgrade of gr
Hi all,
is this bug relevant yet?
I have a buster laptop (so no VM, but real hardware, and no fresh
install) with encrypted disk, and I blocked the upgrade of grub since
March because of the fear to not be able to boot it after the upgrade of
grub.
I am still with 2.02+dfsg1-12 because of this.
I noticed that I haven't told that I'm on buster (I took it for granted based
on the package version).
On 2019-03-30 I upgraded my system and I suffer again of this bug: without
explicit "insmod luks" in /boot/efi/EFI/debian/grub.cfg the boot stops in a
grub shell.
This packages where upgrad
Il 23/03/19 15:01, Colin Watson ha scritto:
> Could you please describe, in as much detail as possible, how to set up
> an environment that replicates this bug?
Hello Colin, thanks for your reply.
Installing the package grub-efi-amd64 with this command line:
apt install --reinstall grub-efi
On Wed, Mar 20, 2019 at 08:33:05AM +, Paolo Miotto wrote:
> this is a continuation of BUG #917117, that is archived.
>
> In that bug every GRUB2 update removes cryptomount call from
> /boot/efi/EFI/debian/grub.cfg, and thus breaks the boot.
>
> Now if I call update-grub, all is fine, but eve
Package: grub-efi-amd64
Version: 2.02+dfsg1-13
Severity: critical
Dear Maintainer,
this is a continuation of BUG #917117, that is archived.
In that bug every GRUB2 update removes cryptomount call from
/boot/efi/EFI/debian/grub.cfg, and thus breaks the boot.
Now if I call update-grub, all is fi
8 matches
Mail list logo
