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 [details]
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-reports-grub-verify-string-not-found

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: