[Bug 1183884] New: GRUB2 error: symbol 'grub_verify_string' not found
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 Bug ID: 1183884 Summary: GRUB2 error: symbol 'grub_verify_string' not found Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs@suse.de Reporter: linuxkamarada@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 847531 --> http://bugzilla.opensuse.org/attachment.cgi?id=847531&action=edit GRUB2 error: symbol 'grub_verify_string' not found I'm using openSUSE Leap 15.3 Beta. Recently I did a zypper up, but after rebooting I was unable to enter the GRUB menu: Welcome to GRUB! error: symbol 'grub_verify_string' not found. Entering rescue mode... grub rescue> Searching for this error message, this was the only page I found: https://linux.debian.bugs.dist.narkive.com/ivKLDzDq/bug-984867-grub-pc-repor... The suggested solution (try to boot manually) didn't work for me. Following the presented steps, insmod normal returned me that same error message: grub rescue> set root=(hd0,5) grub rescue> set prefix=(hd0,5)/@/boot/grub2 grub rescue> insmod normal error: symbol 'grub_verify_string' not found. grub rescue> (see attached image) As a workaround, I tried this and it worked for me: https://www.suse.com/support/kb/doc/?id=000016528 Using the Linux Kamarada 15.2 (based on openSUSE Leap 15.2) LiveUSB (I believe the official openSUSE Live could work as well): # mkdir -p /mnt/opensuse # mount /dev/sda5 /mnt/opensuse -o subvol=@ # mount /dev/sda1 /mnt/opensuse/boot/efi/ # grub2-install --root-directory=/mnt/opensuse /dev/sda Installing for x86_64-efi platform. Installation finished. No error reported. # umount /mnt/opensuse/boot/efi/ # umount /mnt/opensuse/ # reboot (note: no chroot was used) After rebooting, the GRUB menu appeared and I booted as usual. If I understood the procedure above well, I've installed GRUB from Leap 15.2 into my SSD. The grub2 package installed on my system is version 2.04-17.2. The package changelog says it was last updated Thu Mar 11 09:00:00 2021. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c3 --- Comment #3 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 847744 --> http://bugzilla.opensuse.org/attachment.cgi?id=847744&action=edit Output of efibootmgr -v -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c4 --- Comment #4 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 847745 --> http://bugzilla.opensuse.org/attachment.cgi?id=847745&action=edit Output of find /boot/efi -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c5 --- Comment #5 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 847746 --> http://bugzilla.opensuse.org/attachment.cgi?id=847746&action=edit Output of lsblk -f -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c6 --- Comment #6 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 847747 --> http://bugzilla.opensuse.org/attachment.cgi?id=847747&action=edit Output of cat /proc/self/mounts -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c7 --- Comment #7 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 847748 --> http://bugzilla.opensuse.org/attachment.cgi?id=847748&action=edit /var/log/pbl.log -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c8 Projeto Linux Kamarada <linuxkamarada@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(linuxkamarada@gma | |il.com) | --- Comment #8 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Sorry for the delay, here is the information you requested. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 Christian Deckelmann <christian.deckelmann@microfocus.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.deckelmann@microf | |ocus.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c9 --- Comment #9 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Today I did a zypper up and rebooted. That error message appeared again. I solved applying the same workaround. The grub2 package installed on my system is now version 2.04-18.4. The package changelog says it was last updated Tue Mar 16 09:00:00 2021. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c10 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(linuxkamarada@gma | |il.com) --- Comment #10 from Michael Chang <mchang@suse.com> --- (In reply to Projeto Linux Kamarada from comment #3)
Created attachment 847744 [details] Output of efibootmgr -v
The efi boot entry didn't look good to me...
Boot0002* Kamarada PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,GPT,7142e6bb-de6c-425b-9f70-ed70c6798843,0x800,0x32000)/File(\EFI\Linux_Kamarada\grubx64.efi)A01 .. Boot0003* Unknown Device: HD(1,GPT,7142e6bb-de6c-425b-9f70-ed70c6798843,0x800,0x32000)/File(\EFI\opensuse\grubx64.efi)RC Boot0004* Unknown Device: HD(1,GPT,7142e6bb-de6c-425b-9f70-ed70c6798843,0x800,0x32000)/File(\EFI\opensuse\grubx64.efi)RC Boot2001* EFI USB Device RC Boot2002* EFI DVD/CDROM RC Boot2003* EFI Network RC
Why the lable was written as "Unknown Device" whereas the grubx64.efi was installed into \EFI\opensuse\... ? The correct label should be "opensuse", so I wonder is that a change made by firmware ? Also why would the path contain trailing 'RC' or 'A01 ..' that would make the device path 'invalid' ? Which boot entry you were using to boot the opensuse? Have you tried the 'Unknown Device' ? Besides we may need the config files which would be used for efi label creation. /etc/default/grub /etc/os-release And the output of the command ls -lR /boot/efi The access time would be useful to tell which grubx64.efi was updated and when ... Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c11 --- Comment #11 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- I imagine where the confusion comes from. Actually, I installed Linux Kamarada 15.2, which is based on openSUSE Leap 15.2, using Calamares. Then recently I upgraded it to openSUSE Leap 15.3 Beta using zypper. I'm not able to answer your first questions, because I don't know much about EFI... I don't know what "Unknown Device", "RC" or "A01" mean.
Which boot entry you were using to boot the opensuse? Have you tried the 'Unknown Device' ?
Probably I'm booting Kamarada.
Besides we may need the config files which would be used for efi label creation.
/etc/default/grub /etc/os-release
And the output of the command
ls -lR /boot/efi
I'll attach them.
The access time would be useful to tell which grubx64.efi was updated and when ...
Yesterday I did a zypper up, the same error appeared and I applied the same workaround. The grub2 package installed on my system is now version 2.04-20.1. The package changelog says it was last updated Fri Apr 23 2021 09:00:00.
Thanks.
Thank you too! Please note that while I was using Kamarada 15.2 / Leap 15.2, updates worked well. I imagine if there is some hardcoded string pointing to EFI/opensuse into the 15.3 grub package. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c12 --- Comment #12 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 848903 --> http://bugzilla.opensuse.org/attachment.cgi?id=848903&action=edit /etc/default/grub -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c13 --- Comment #13 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 848904 --> http://bugzilla.opensuse.org/attachment.cgi?id=848904&action=edit /etc/os-release -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c14 Projeto Linux Kamarada <linuxkamarada@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(linuxkamarada@gma | |il.com) | --- Comment #14 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 848905 --> http://bugzilla.opensuse.org/attachment.cgi?id=848905&action=edit Output of ls -lR /boot/efi -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c16 Projeto Linux Kamarada <linuxkamarada@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #847744|0 |1 is obsolete| | --- Comment #16 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 849305 --> http://bugzilla.opensuse.org/attachment.cgi?id=849305&action=edit Output of efibootmgr -v (2nd try) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c17 --- Comment #17 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- (In reply to Michael Chang from comment #15) I followed your instructions.
If 'opensuseleap' didn't show up in the firmware's boot list or cannot load grub, then I would suspect either firmware or efibootmgr needs check.
That's what happened. Only Kamarada and Windows showed on the boot list. UEFI is enabled, but Secure Boot is not. What could I try next? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c18 Projeto Linux Kamarada <linuxkamarada@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(linuxkamarada@gma | |il.com) | --- Comment #18 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 849306 --> http://bugzilla.opensuse.org/attachment.cgi?id=849306&action=edit Boot list -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c19 Projeto Linux Kamarada <linuxkamarada@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #849305|0 |1 is obsolete| | --- Comment #19 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- Created attachment 849307 --> http://bugzilla.opensuse.org/attachment.cgi?id=849307&action=edit Output of efibootmgr -v (3rd try) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 Projeto Linux Kamarada <linuxkamarada@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #849306|0 |1 is obsolete| | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c20 --- Comment #20 from Projeto Linux Kamarada <linuxkamarada@gmail.com> --- (In reply to Michael Chang from comment #15) I remembered that there is a specific setting on my BIOS. I needed to enable Secure Boot, then an option became available: "Select an UEFI file as trusted for executing". I navigated through a kind of file manager and selected EFI/opensuse/grubx64.efi as trusted. I did this and disabled Secure Boot again. Then I was able to boot from "opensuseleap". According to efibootmgr -v, I booted from "opensuseleap". So, this seems to have worked:
Would you please try the manual step to create the boot variable for booting the opensuse grub ?
efibootmgr -c -L 'opensuseleap' -l '\EFI\opensuse\grubx64.efi' -d /dev/sda -p 1 efibootmgr -v
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c21 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(linuxkamarada@gma | |il.com) --- Comment #21 from Michael Chang <mchang@suse.com> --- (In reply to Projeto Linux Kamarada from comment #20)
(In reply to Michael Chang from comment #15)
I remembered that there is a specific setting on my BIOS. I needed to enable Secure Boot, then an option became available: "Select an UEFI file as trusted for executing". I navigated through a kind of file manager and selected EFI/opensuse/grubx64.efi as trusted. I did this and disabled Secure Boot again. Then I was able to boot from "opensuseleap".
Frankly this design sounds a bit silly, the file you can select doesn't link to anything you can trust, merely you want it to do the work for you. If that can work then why there are phishing email and website in the first place. To prevent running malicious software the integrity and authenticity has to be verified by a trusted authority (CA) and is by no means your own decision. I have no idea why they provide this function. IMHO it should respect all usable boot entries and the boot order you made, and use secure boot to verify the image for you. It is not you to "Select an UEFI file as trusted for executing" ...
According to efibootmgr -v, I booted from "opensuseleap".
So, this seems to have worked:
Would you please try the manual step to create the boot variable for booting the opensuse grub ?
efibootmgr -c -L 'opensuseleap' -l '\EFI\opensuse\grubx64.efi' -d /dev/sda -p 1 efibootmgr -v
As long as \EFI\opensuse\grubx64.efi is used, you should not run into "symbol 'grub_verify_string' not found" in future updates. Did you agree to close this ticket because the problem is due to firmware which ignores opensuse boot entry and also now we have a workaround ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c22 --- Comment #22 from Michael Chang <mchang@suse.com> --- (In reply to Michael Chang from comment #21)
(In reply to Projeto Linux Kamarada from comment #20)
(In reply to Michael Chang from comment #15)
Frankly this design sounds a bit silly, the file you can select doesn't link to anything you can trust, merely you want it to do the work for you. If that can work then why there are phishing email and website in the first place. To prevent running malicious software the integrity and authenticity has to be verified by a trusted authority (CA) and is by no means your own decision.
Sorry this is a bit misleading. Certainly you can decide to trust "your own" bootloader and follow that process may work (although it is still insecure because it can be replaced if you don't put enough attention). But in this case bootloader is provided by third party like opensuse, it is not you to decide trust or not because you may be using, for eg, tempered image downloading from fake website. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com