Good day, does grub 2.12 (without rc1) help? There are a good pile of fixups between rc1 and release. E.g. https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12&id=1f5b180742ff2706bc3a696d115ddbc677ec75b9 or https://git.savannah.gnu.org/cgit/grub.git/commit/?h=grub-2.12&id=67ae3981dc5113e5af3a0539174bcd7eab8f7722 could help.
Additionally, the ZFS fixes are needed to boot from volumes touched by ZFS 2.2 ( https://github.com/openzfs/zfs/issues/13873 ), so migrating to 2.12 is helpful in either case. Best regards, Michael Fritscher On Sat, 25 Nov 2023 17:36:41 -0500 Nicolas Haller <nico...@boiteameuh.org> wrote: > Package: grub-efi-amd64 > Version: 2.06-13 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > My old laptop (Lenovo 11e) runs Sid and all was right before I updated > it the other day (I don't do that very often). After that upgrade, GRUB > wasn't able to load any kernel with the pretty much generic error > "Error: can't load image". The version of GRUB was 2.12~rc1-12. > If I try to boot again, GRUB tells me that I need to load the image > first (I guess it somehow ignores the linux command and sends that when > trying to load the initrd). > > I tried to reinstall grub, grub-install /dev/sda, update-grub, reinstall > the kernel, update-initramfs from the rescue mode but nothing worked. > The "file" command was able to read the vmlinuz file and none seemed > truncated. The system has one partition with both / and /boot and isn't > running out of space. > I did not see any error message during those operation besides GRUB > saying it wasn't able to update EFI parameters. > > I don't know if there is a way to get more logs or error message during > the boot explaining why it wasn't able to load the image. > > I tried to get the last version of GRUB from Bookworm, that is > 2.06-13, and now I'm able to boot. The kernel version did not change, > the only change I did is to downgrade GRUB (and dependencies apt was > asking for). > > I'm not sure which GRUB package I should use for reporting so I took the > one that seems the most specific to my system. Apologies if it is not > correct. > > Let me know if you need more info. > > Thanks, > > -- > Nicolas Haller > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > > -- Package-specific info: > > *********************** BEGIN /proc/mounts > /dev/sda2 / ext4 rw,relatime,errors=remount-ro 0 0 > /dev/sda1 /boot/efi vfat > rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro > 0 0 > *********************** END /proc/mounts >