Bug#984760: grub-efi-amd64: upgrade works, boot fails (error: symbol `grub_is_lockdown` not found)

[Colin Watson]

Control: tag -1 moreinfo

Sorry for our long delay in replying to this.

On Mon, Mar 08, 2021 at 02:20:08PM +1100, Anand Kumria wrote:
> grub went into grub rescue mode and displayed:
> 
> error: symbol `grub_is_lockdown` not found

In general, this means that grub-install is not installing to the place
that your firmware is actually booting from, which causes the core image
(installed to a file under /boot/efi/ on UEFI systems) to be out of sync
with the modules (installed to a subdirectory of /boot/grub/).  This is
much rarer on UEFI systems than on BIOS systems, but it's still possible
in some misconfigured cases.

Could you please attach the output of "sudo grub-install --debug", "sudo
efibootmgr -v", and "sudo find /boot/efi -ls"?

> Currently, I am booting using a rescue CD and then entering commands to manually start the laptop

What commands are you using?

> -- Package-specific info:
> 
> *********************** BEGIN /proc/mounts
> /dev/sda5 / ext4 rw,relatime,errors=remount-ro 0 0
> /dev/sda6 /home ext4 rw,relatime 0 0
> /dev/sda2 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
> *********************** END /proc/mounts
[...]
> *********************** BEGIN /dev/disk/by-id
> total 0
> lrwxrwxrwx 1 root root  9 Mar  8 11:14 ata-MATSHITADVD-RAM_UJ8C2_WP18_009183 -> ../../sr0
> lrwxrwxrwx 1 root root  9 Mar  8 11:14 ata-TOSHIBA_THNSNS128GCSP_922S10RGT2JY -> ../../sda
> lrwxrwxrwx 1 root root 10 Mar  8 11:14 ata-TOSHIBA_THNSNS128GCSP_922S10RGT2JY-part1 -> ../../sda1
> lrwxrwxrwx 1 root root 10 Mar  8 11:15 ata-TOSHIBA_THNSNS128GCSP_922S10RGT2JY-part2 -> ../../sda2
> lrwxrwxrwx 1 root root 10 Mar  8 11:14 ata-TOSHIBA_THNSNS128GCSP_922S10RGT2JY-part3 -> ../../sda3
> lrwxrwxrwx 1 root root 10 Mar  8 11:14 ata-TOSHIBA_THNSNS128GCSP_922S10RGT2JY-part4 -> ../../sda4
> lrwxrwxrwx 1 root root 10 Mar  8 11:14 ata-TOSHIBA_THNSNS128GCSP_922S10RGT2JY-part5 -> ../../sda5
> lrwxrwxrwx 1 root root 10 Mar  8 11:15 ata-TOSHIBA_THNSNS128GCSP_922S10RGT2JY-part6 -> ../../sda6
> *********************** END /dev/disk/by-id
> 
> *********************** BEGIN /dev/disk/by-uuid
> total 0
> lrwxrwxrwx 1 root root 10 Mar  8 11:14 141A3D7E1A3D5E44 -> ../../sda4
> lrwxrwxrwx 1 root root  9 Mar  8 11:15 2020-11-30-03-01-21-00 -> ../../sr0
> lrwxrwxrwx 1 root root 10 Mar  8 11:15 26cd5a33-dd28-4968-b2b4-2d134be2e444 -> ../../sda6
> lrwxrwxrwx 1 root root 10 Mar  8 11:14 A65030AD50308659 -> ../../sda1
> lrwxrwxrwx 1 root root 10 Mar  8 11:15 DE31-8EDF -> ../../sda2
> lrwxrwxrwx 1 root root 10 Mar  8 11:14 a49dde0e-f2e4-4679-8c56-b9013d7b0fd2 -> ../../sda5
> *********************** END /dev/disk/by-uuid

I notice that not all your partitions are mounted.  What's on partitions
1, 3, and 4?  ("sudo parted -s /dev/sda print" might help.)

Thanks,

-- 
Colin Watson (he/him)                              [cjwatson at debian.org]