Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot

[Julian Andres Klode]

On Tue, Sep 05, 2023 at 08:32:39PM +0200, Agustin Martin wrote:
> On Tue, Sep 05, 2023 at 07:34:13PM +0200, Julian Andres Klode wrote:
> > On Tue, Sep 05, 2023 at 12:26:56PM -0400, M. Zhou wrote:
> > > I am able to boot with 2.12~rc1-7 now. And my currrent status is
> > >
> > > grub-common/unstable,now 2.12~rc1-7 amd64 [installed]
> > > grub-efi-amd64-bin/unstable,now 2.12~rc1-7 amd64 [installed,automatic]
> > > grub-efi-amd64-signed/unstable,now 1+2.12~rc1+7 amd64
> > > [installed,automatic]
> > > grub-efi-amd64/unstable,now 2.12~rc1-7 amd64 [installed,automatic]
> > > grub2-common/unstable,now 2.12~rc1-7 amd64 [installed,automatic]
> > >
> > > I reinstalled grub using 2.12~rc1-7.
> > > But I still cannot guarantee it is safe to upgrade.
> > >
> > >
> > > I believe the issue is the missing versioned dependency, which
> > > allowed partial upgrade.
> >
> > Thanks for confirming this, this makes sense, if you boot without
> > secure boot, the signed grub 2.06 could then try to upload
> > incompatible modules from 2.12~rc1 and crash.
> 
> This may not be all the problem, I am still having problems with 2.12-rc1-7
> and most recent packages installed with my old setup (/boot/efi not
> mounted by default).
> 
> If /boot/efi is not mounted I get for new versions

Well that's *your problem*, sorry. Mounting /boot/efi is mandatory,
you can't just go unmount it. By the same argument unmounting /boot
(if a separate partition) yields an unbootable system too (eventually
once /boot on / becomes out of sync with actual boot partition grub
uses).

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en