Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
El mar, 5 sept 2023 a las 20:32, Agustin Martin () escribió: > > If /boot/efi is not mounted I get for new versions > > $ LC_ALL=C sudo dpkg-reconfigure grub-efi-amd64 > Installing for x86_64-efi platform. > grub-install: error: cannot find EFI directory. > Failed: grub-install --target=x86_64-efi --force-extra-removable > WARNING: Bootloader is not properly installed, system may not be bootable > Generating grub configuration file ... One thing I did not remark. After this error, configuration continues and apt dist-upgrade finishes without leaving grub-efi-amd64 unconfigured. This makes harder to notice this problem until standalone package configuration is retried when debugging the problem. Regards, -- Agustin
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
Just after sending my previous message I noticed the following versions were available after an apt upgrade: grub2-common 2.12~rc1-9 grub-common 2.12~rc1-9 grub-efi-amd64 2.12~rc1-9 grub-efi-amd64-bin 2.12~rc1-9 grub-efi-amd64-signed 2.12~rc1-7 so I bit the bullet and made an upgrade. It works. The computer boots normally. The only thing I noticed is the grub screen saying version rc-1.7... Shouldn't it be version rc-1.9? Anyway, it works. Thank you!
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
> On Tue, Sep 05, 2023 at 07:34:13PM +0200, Julian Andres Klode wrote: > I wrote > > 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). Hi, Julian, thanks for your reply. It was my understanding that grub-install did know how to find and use the efi partition if not mounted, seems I was wrong. But for some reason this problem did not show up in previous version, see below. El mar, 5 sept 2023 a las 21:40, Julian Andres Klode () escribió: > I wrote > > $ LC_ALL=C sudo dpkg-reconfigure grub-efi-amd64 > > Installing for x86_64-efi platform. > > grub-install: error: cannot find EFI directory. > > Failed: grub-install --target=x86_64-efi --force-extra-removable > > WARNING: Bootloader is not properly installed, system may not be bootable > > Generating grub configuration file ... > > > > (same without --force-extra-removable). No such error with previous version. > > Also, that's not true. grub-install for EFI of course always > requires /boot/efi present, always has and always will* > > * on Ubuntu we mount to /var/lib/grub/esp if /boot/efi is not > mounted (or you have multiple ESPs configured), but the script > isn't in Debian yet, it's a bit hacky and duplicates lots of postinst > sightly different :( I am rechecking 2.06-13 in a different efi box that was installed as efi from the beginning (previous one was not). Although /boot/efi is not mounted, error in grub-efi-amd64 configuration does not happen (this does not mean that installation is fully OK, just that error does not happen and grub is bootable). I do not remember to have changed /etc/fstab to set noauto instead of defaults in that entry, but this happened some years ago and sincerely, cannot be sure. $ dpkg -l 'grub*' | grep ^i ii grub-common 2.06-13 amd64GRand Unified Bootloader (common files) ii grub-efi-amd642.06-13 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin2.06-13 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 modules) ii grub-efi-amd64-signed 1+2.06+13amd64GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) ii grub2-common 2.06-13 amd64GRand Unified Bootloader (common files for version 2) $ grep /boot/efi /etc/fstab # /boot/efi was on /dev/nvme0n1p1 during installation UUID=5451-8D5D /boot/efi vfatumask=0077,noauto 0 1 $ mount | grep -i efi efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) $ LC_ALL=C sudo apt-get install --reinstall grub-efi-amd64 Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/45.7 kB of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 546089 files and directories currently installed.) Preparing to unpack .../grub-efi-amd64_2.06-13_amd64.deb ... Unpacking grub-efi-amd64 (2.06-13) over (2.06-13) ... Setting up grub-efi-amd64 (2.06-13) ... Generating grub configuration file ... Found background image: .background_cache.png Found linux image: /boot/vmlinuz-6.3.0-1-amd64 Found initrd image: /boot/initrd.img-6.3.0-1-amd64 Found linux image: /boot/vmlinuz-6.1.0-9-amd64 Found initrd image: /boot/initrd.img-6.1.0-9-amd64 Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for UEFI Firmware Settings ... done Processing triggers for shim-signed:amd64 (1.39+15.7-1) ... Regards, -- Agustin
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
Hello Just for your information. I managed to get all grub packages grub2-common grub-common grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed updated to 2.12~rc1-7 and the system DOES NOT BOOT. I downgraded all those grub packages to 2.06-3~deb11u5 (the one found in stable) and it boots without problems. So, I'm concerned if the 2.12~rc1-9 version will boot on my machine.
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
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 > > $ LC_ALL=C sudo dpkg-reconfigure grub-efi-amd64 > Installing for x86_64-efi platform. > grub-install: error: cannot find EFI directory. > Failed: grub-install --target=x86_64-efi --force-extra-removable > WARNING: Bootloader is not properly installed, system may not be bootable > Generating grub configuration file ... > > (same without --force-extra-removable). No such error with previous version. Also, that's not true. grub-install for EFI of course always requires /boot/efi present, always has and always will* * on Ubuntu we mount to /var/lib/grub/esp if /boot/efi is not mounted (or you have multiple ESPs configured), but the script isn't in Debian yet, it's a bit hacky and duplicates lots of postinst sightly different :( -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
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
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
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 $ LC_ALL=C sudo dpkg-reconfigure grub-efi-amd64 Installing for x86_64-efi platform. grub-install: error: cannot find EFI directory. Failed: grub-install --target=x86_64-efi --force-extra-removable WARNING: Bootloader is not properly installed, system may not be bootable Generating grub configuration file ... (same without --force-extra-removable). No such error with previous version. If I update everything with /boot/efi mounted and keep it mounted afterwards, new grub versions are booting. Regards, -- Agustin
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
On Tue, Sep 05, 2023 at 12:26:56PM -0400, M. Zhou wrote: > On Tue, 5 Sep 2023 18:11:55 +0200 "Miguel A. Vallejo" > wrote: > > M. Zhou wrote: > > > > > But after that I noticed that the most important > > > package grub-efi-amd64-signed:amd64 (1+2.06+13, > > > 1+2.12~rc1+7) was not upgraded along with the other > > > grub packages. > > > > You are right. I revised apt log and grub-efi-amd64-signed was NOT > > updated, in fact, the version I have installed now is 1+2.06+13, but > > all other grub packages have 2.06-3~deb11u5. > > > > Now, if I run apt update, and apt list --upgradable it shows: > > > > grub-common/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06- > 3~deb11u5] > > grub-efi-amd64-bin/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06- > 3~deb11u5] > > grub-efi-amd64-signed/unstable 1+2.12~rc1+7 amd64 [upgradable from: > 1+2.06+13] > > grub-efi-amd64/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06- > 3~deb11u5] > > grub2-common/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06- > 3~deb11u5] > > > > > > All of them with version 2.12~rc1-7 > > > > Is it safe to upgrade now? I'll wait a bit until I hear from the > > package maintainers. > > 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. > > If you check the testing, you will find that > > grub-efi-amd64-signed/1+2.06+13 Depends: grub-common (>= 2.06-13) > > Then, if we upgrade grub-common to 2.12~rc1-7, without > upgrading grub-efi-amd64-signed itself, then the boot is broken. > > TLDR: the boot is broken with the following partial upgrade: > grub-common/2.12~rc1-7 > grub-efi-amd64-signed/2.06+13 > > A possible fix might be specifying > Depends: grub-common (>= 2.12~rc1-7)), grub-common (<= 2.13~) > to prevent incompatible grub-common and grub-efi-amd64-signed > from co-existing. Although it does not help this time. > 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. The 2.12~rc1-8 and -9 uploads change this in two steps to avoid this by making the signed package require a matching unsigned one again, and by making the existing -bin package Breaks << 1+2.12~rc1 such that you cannot partially upgrade those with incompatible older grubs. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Processed: Re: Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
Processing control commands: > tag -1 unreproducible Bug #1051271 [grub2] GRUB2 2.12~rc1-7 prevent machine to boot Added tag(s) unreproducible. -- 1051271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
Control: tag -1 unreproducible On Tue, Sep 05, 2023 at 04:19:01PM +0200, Miguel A. Vallejo wrote: > Package: grub2 > Version: 2.12~rc1-7 > Severity: critical > > This morning I noticed an apt upgrade in Debian unstable/Sid upgraded > grub-common, grub2-common, grub-efi-amd64 and grub-efi-amd64-bin. The > upgrade went normally and no errors were shown. Then I turned the > computer off and after a few hours I tried to turn it on, but it > didn't boot, it tried to boot but finally showed the bios screen. You are going to have to provide a lot more details than this, because it works in qemu, on the XPS13 I have for testing, and it's been in Ubuntu devel for over a month now with no such issues. - What hardware are you running this on? - It seems you have not updated grub-efi-amd64-signed, is that installed? - Is grub even loaded, what happens if you press Shift very quickly all the time during boot? - If grub is loaded, drop to console (c) and set debug=all, then normal and try to boot the entry again. - If grub is not loaded, set mokutil --set-verbosity true before trying to boot and record a video of your device screen. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
On Tue, 5 Sep 2023 18:11:55 +0200 "Miguel A. Vallejo" wrote: > M. Zhou wrote: > > > But after that I noticed that the most important > > package grub-efi-amd64-signed:amd64 (1+2.06+13, > > 1+2.12~rc1+7) was not upgraded along with the other > > grub packages. > > You are right. I revised apt log and grub-efi-amd64-signed was NOT > updated, in fact, the version I have installed now is 1+2.06+13, but > all other grub packages have 2.06-3~deb11u5. > > Now, if I run apt update, and apt list --upgradable it shows: > > grub-common/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06- 3~deb11u5] > grub-efi-amd64-bin/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06- 3~deb11u5] > grub-efi-amd64-signed/unstable 1+2.12~rc1+7 amd64 [upgradable from: 1+2.06+13] > grub-efi-amd64/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06- 3~deb11u5] > grub2-common/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06- 3~deb11u5] > > > All of them with version 2.12~rc1-7 > > Is it safe to upgrade now? I'll wait a bit until I hear from the > package maintainers. 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. If you check the testing, you will find that grub-efi-amd64-signed/1+2.06+13 Depends: grub-common (>= 2.06-13) Then, if we upgrade grub-common to 2.12~rc1-7, without upgrading grub-efi-amd64-signed itself, then the boot is broken. TLDR: the boot is broken with the following partial upgrade: grub-common/2.12~rc1-7 grub-efi-amd64-signed/2.06+13 A possible fix might be specifying Depends: grub-common (>= 2.12~rc1-7)), grub-common (<= 2.13~) to prevent incompatible grub-common and grub-efi-amd64-signed from co-existing. Although it does not help this time.
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
M. Zhou wrote: > But after that I noticed that the most important > package grub-efi-amd64-signed:amd64 (1+2.06+13, > 1+2.12~rc1+7) was not upgraded along with the other > grub packages. You are right. I revised apt log and grub-efi-amd64-signed was NOT updated, in fact, the version I have installed now is 1+2.06+13, but all other grub packages have 2.06-3~deb11u5. Now, if I run apt update, and apt list --upgradable it shows: grub-common/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06-3~deb11u5] grub-efi-amd64-bin/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06-3~deb11u5] grub-efi-amd64-signed/unstable 1+2.12~rc1+7 amd64 [upgradable from: 1+2.06+13] grub-efi-amd64/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06-3~deb11u5] grub2-common/unstable 2.12~rc1-7 amd64 [upgradable from: 2.06-3~deb11u5] All of them with version 2.12~rc1-7 Is it safe to upgrade now? I'll wait a bit until I hear from the package maintainers.
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
El mar, 5 sept 2023 a las 17:21, Agustin Martin () escribió: > > On Tue, Sep 05, 2023 at 04:19:01PM +0200, Miguel A. Vallejo wrote: > > Package: grub2 > > Version: 2.12~rc1-7 > > Severity: critical > > > > This morning I noticed an apt upgrade in Debian unstable/Sid upgraded > > grub-common, grub2-common, grub-efi-amd64 and grub-efi-amd64-bin. The > > upgrade went normally and no errors were shown. Then I turned the > > computer off and after a few hours I tried to turn it on, but it > > didn't boot, it tried to boot but finally showed the bios screen. > > > > After booting with a live USB and chroot into the hard drive, I > > downgraded those four packages to version 2.06-3~deb11u5, and after > > run install-grub, the computer booted normally. > > > > Anyone can confirm problems with version 2.12~rc1-7 and UEFI machines? > > Same problem here. I can confirm that downgrading all above grub packages to 2.06-13, reinstalling grub and updating grub.cfg works around this issue. Did all together, only part of the above might be required. Previously tried to change grub.cfg to an old version to check if I could reach the grub menu, but no luck. diffing old (the one generated by buggy grub) and new grub.cfg created after downgrading I see a dis_ucode_ldr parameter as well as an 'UEFI Firmware Settings' entry in old grub.cfg. Hope this helps -- Agustin
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
Same here. But I have some different conclusions after fixing my machine. Before my machine becoming unable to boot, the last apt log involves Start-Date: 2023-09-05 00:09:00 Commandline: apt upgrade Requested-By: lumin (1000) Upgrade: libimath-3-1-29:amd64 (3.1.9-2, 3.1.9-3), python3-brlapi:amd64 (6.6-2, 6.6-4), libtrilinos-aztecoo-13.2:amd64 (13.2.0-4, 13.2.0-5), libgtk-4-common:amd64 (4.12.1+ds-2, 4.12.1+ds-3), xbrlapi:amd64 (6.6-2, 6.6-4), libldb2:amd64 (2:2.7.2+samba4.18.6+dfsg-1, 2:2.8.0+samba4.19.0+dfsg-1), libwayland-cursor0:amd64 (1.22.0-2, 1.22.0-2.1), libbrlapi0.8:amd64 (6.6-2, 6.6-4), libtrilinos-ml- 13.2:amd64 (13.2.0-4, 13.2.0-5), libwayland-server0:amd64 (1.22.0-2, 1.22.0-2.1), libtrilinos-epetraext-13.2:amd64 (13.2.0-4, 13.2.0-5), dvisvgm:amd64 (3.1-1, 3.1.1+ds-1), libtrilinos-ifpack-13.2:amd64 (13.2.0-4, 13.2.0-5), libsuperlu6:amd64 (6.0.0+dfsg1-3, 6.0.1+dfsg1-1), libtrilinos-trilinosss-13.2:amd64 (13.2.0-4, 13.2.0-5), libtrilinos- kokkos-13.2:amd64 (13.2.0-4, 13.2.0-5), libwbclient0:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), libtrilinos-amesos-13.2:amd64 (13.2.0-4, 13.2.0-5), libsmbclient:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), gir1.2-gtk-4.0:amd64 (4.12.1+ds-2, 4.12.1+ds-3), grub-efi-amd64:amd64 (2.06-13, 2.12~rc1-7), gir1.2-accountsservice- 1.0:amd64 (23.13.9-3, 23.13.9-4), libnet-http-perl:amd64 (6.22-1, 6.23- 1), libtrilinos-epetra-13.2:amd64 (13.2.0-4, 13.2.0-5), libtrilinos- teuchos-13.2:amd64 (13.2.0-4, 13.2.0-5), libscotch-7.0:amd64 (7.0.3-2, 7.0.4-1), libtrilinos-zoltan-13.2:amd64 (13.2.0-4, 13.2.0-5), libunbound8:amd64 (1.17.1-2, 1.18.0-1), libtrilinos-galeri-13.2:amd64 (13.2.0-4, 13.2.0-5), grub-efi-amd64-bin:amd64 (2.06-13, 2.12~rc1-7), grub2-common:amd64 (2.06-13, 2.12~rc1-7), libwayland-egl1:amd64 (1.22.0-2, 1.22.0-2.1), libtrilinos-triutils-13.2:amd64 (13.2.0-4, 13.2.0-5), fonts-noto-cjk:amd64 (1:20230817+repack1-1, 1:20230817+repack1-3), grub-common:amd64 (2.06-13, 2.12~rc1-7), libgtk- 4-1:amd64 (4.12.1+ds-2, 4.12.1+ds-3), accountsservice:amd64 (23.13.9-3, 23.13.9-4), samba-libs:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), libptscotch-7.0:amd64 (7.0.3-2, 7.0.4-1), libgtk-4-bin:amd64 (4.12.1+ds-2, 4.12.1+ds-3), libgtk-4-media-gstreamer:amd64 (4.12.1+ds- 2, 4.12.1+ds-3), libwayland-client0:amd64 (1.22.0-2, 1.22.0-2.1), libaccountsservice0:amd64 (23.13.9-3, 23.13.9-4) End-Date: 2023-09-05 00:09:25 The machine does not boot since here. Then I wanted to reinstall grub without noticing that the package to install is no longer grub2 in the EFI era. Ignore this change. Start-Date: 2023-09-05 10:34:44 Commandline: apt install grub2 Install: grub2:amd64 (2.12~rc1-7), grub-pc-bin:amd64 (2.12~rc1-7, automatic), grub-pc:amd64 (2.12~rc1-7, automatic) Remove: grub-efi-amd64:amd64 (2.12~rc1-7) End-Date: 2023-09-05 10:34:47 I have tried some other ways to fix the boot, including rolling back grub to the testing version. But after that I noticed that the most important package grub-efi-amd64-signed:amd64 (1+2.06+13, 1+2.12~rc1+7) was not upgraded along with the other grub packages. Start-Date: 2023-09-05 10:48:36 Commandline: apt upgrade Requested-By: lumin (1000) Upgrade: evince:amd64 (45~alpha-2, 45~rc-1), libnghttp2-14:amd64 (1.55.1-1, 1.56.0-1), eog:amd64 (45~alpha-1, 45~rc-1), libevdocument3- 4:amd64 (45~alpha-2, 45~rc-1), libeatmydata1:amd64 (130-2+b1, 131-1), libevview3-3:amd64 (45~alpha-2, 45~rc-1), evince-common:amd64 (45~alpha-2, 45~rc-1), grub-efi-amd64-signed:amd64 (1+2.06+13, 1+2.12~rc1+7), gir1.2-evince-3.0:amd64 (45~alpha-2, 45~rc-1), eatmydata:amd64 (130-2, 131-1), libucx0:amd64 (1.15.0~rc3-1, 1.15.0~rc4-1) End-Date: 2023-09-05 10:48:43 After this, I removed all the extra config files I wrote in order to fix the boost. Then I did yet another clean grub install update-initramfs -k all -u update-grub2 Then reboot is successful with 1+2.12~rc1+7 . So my conclusion is that there might be something wrong in the Depends: sections of some of the grub2 packages, which did not specify versioned dependency to express incompatibility. I believe the maintainers have fully tested the grub loader before pushing it to unstable. But unfortunately, the asynchronized mirror update, resulted into partial upgrade of grub2 at the user end, which eventually affected a large amount of users. If it was a issue in the Depends field, it is still a critical bug which may damage user system, even if the trigger is partial upgrade due to mirror sync.
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
On Tue, Sep 05, 2023 at 04:19:01PM +0200, Miguel A. Vallejo wrote: > Package: grub2 > Version: 2.12~rc1-7 > Severity: critical > > This morning I noticed an apt upgrade in Debian unstable/Sid upgraded > grub-common, grub2-common, grub-efi-amd64 and grub-efi-amd64-bin. The > upgrade went normally and no errors were shown. Then I turned the > computer off and after a few hours I tried to turn it on, but it > didn't boot, it tried to boot but finally showed the bios screen. > > After booting with a live USB and chroot into the hard drive, I > downgraded those four packages to version 2.06-3~deb11u5, and after > run install-grub, the computer booted normally. > > Anyone can confirm problems with version 2.12~rc1-7 and UEFI machines? Same problem here. -- Agustin
Bug#1051271: GRUB2 2.12~rc1-7 prevent machine to boot
Package: grub2 Version: 2.12~rc1-7 Severity: critical This morning I noticed an apt upgrade in Debian unstable/Sid upgraded grub-common, grub2-common, grub-efi-amd64 and grub-efi-amd64-bin. The upgrade went normally and no errors were shown. Then I turned the computer off and after a few hours I tried to turn it on, but it didn't boot, it tried to boot but finally showed the bios screen. After booting with a live USB and chroot into the hard drive, I downgraded those four packages to version 2.06-3~deb11u5, and after run install-grub, the computer booted normally. Anyone can confirm problems with version 2.12~rc1-7 and UEFI machines? Thanks in advance.
