Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"
Package: grub-pc Version: 2.02+dfsg1-20+deb10u4 Followup-For: Bug #984426 Hi, just to inform that I suffered this problem too, after upgrading my system to Debian 10.9 (in the last security upgrade several days ago). I agree that the problem arose due to a misconfiguration in my system, as my main HDD was broken several months ago, so I "cloned" the system onto the new HDD, but I installed grub manually onto the new HDD, but I forgot to update debconf. The last time I replaced a HDD was 15 years ago, when LILO was the boot loader, so I did not take into account debconf for grub, my mistake. Anyway, in the upgrade process, I suggest to show a warning like other packages do (as example when a different version of kernel is running not corresponding to the driver version you are installing) to prevent to have an "inaccessible" system. If needed, I can open a new bug, with severity "wish list" to request this feature or to keep this bug open until the warning is implemented, so if other people have the same problem can fix it quickly. Thank you for your great work. Sincerely, Jose
Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"
Package: grub-pc Version: 2.02+dfsg1-20+deb10u4 Followup-For: Bug #984426 Hello, I experienced the same problem on a couple of my machines too. Yes, technically a misconfiguration at my end, but the number of me-too's suggests that there are many others not realising that debconf needs to know about *every* bootable disk to avoid this sort of issue. I know it's not your fault and is a bit annoying, but I suggest that grub check for and complain if it notices disks that have grub installed on it, yet are not listed in debconf's install_devices (eg. because at some point in the (possibly distant) past, the admin ran grub-install manually, and/or used a rescue disk to (re)install grub). In the absence of such an actual check, perhaps just put a reminder in NEWS.Debian to the effect that running grub-install behind debconf's back may have unforseen consequences, and that a bootloader installed in this way will not get updated automatically. -MD
Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"
On Thu, Mar 04, 2021 at 10:43:27AM +0100, Marco Kühnel wrote: > I have the same error message after the update to grub2/2.02+dfsg1- > 20+deb10u4, but with grub-efi-amd64* instead of grub-pc. After pressing > the "arbitrary key", Debian boots but fails to start lightdm. Should I > report a new bug? Anything involving UEFI is distinct from this bug, so please report it separately with full details. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"
I have the same error message after the update to grub2/2.02+dfsg1- 20+deb10u4, but with grub-efi-amd64* instead of grub-pc. After pressing the "arbitrary key", Debian boots but fails to start lightdm. Should I report a new bug? Marco -- codecivil Dr. Marco Kühnel ICT Services, Vechteweg 4, 30539 Hannover, Tel. 0170 7507391, Umsatzsteuer-Identifikationsnummer DE 296 659 690, Finanzamt Hannover-Mitte Meinen PGP-Schlüssel finden Sie unter http://www.codecivil.de/kueh...@codecivil.de.asc oder auf den gängigen Keyservern. Bitte unterstützen Sie die Kampagne "Public Money - Public Code", indem Sie den offenen Brief auf https://publiccode.eu/openletter unterzeichnen. signature.asc Description: This is a digitally signed message part
Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"
On Wed, Mar 03, 2021 at 06:24:30PM +0100, Karsten wrote: > Am 03.03.21 um 18:00 schrieb Colin Watson: > > Since you're reporting this against grub-pc 2.02+dfsg1-20+deb10u4, and > > since the mentioned grub_register_command_lockdown symbol was only > > introduced in that version, then there must have been a system update, > > because we only released that version yesterday. > > A search shows in /var/log/apt/history.log > > Start-Date: 2021-03-03 09:28:01 > Commandline: /usr/bin/unattended-upgrade > Upgrade: grub-common:amd64 (2.02+dfsg1-20+deb10u3, 2.02+dfsg1-20+deb10u4), > grub2-common:amd64 (2.02+dfsg1-20+deb10u3, > 2.02+dfsg1-20+deb10u4), grub-pc:amd64 (2.02+dfsg1-20+deb10u3, > 2.02+dfsg1-20+deb10u4), grub-pc-bin:amd64 > (2.02+dfsg1-20+deb10u3, 2.02+dfsg1-20+deb10u4) > End-Date: 2021-03-03 09:28:36 > > Start-Date: 2021-03-03 17:03:42 > Reinstall: grub-pc:amd64 (2.02+dfsg1-20+deb10u4) > End-Date: 2021-03-03 17:04:12 > > > How can such "unattended-upgrade" be killed? I can't help you with that, but it shouldn't be too hard to find documentation. > > What does "sudo debconf-show grub-pc" say? [...] > * grub-pc/install_devices: /dev/disk/by-id/ata-TOSHIBA_DT01ACA200_84H86A0GS According to the information in your initial report, this is your /dev/sda. I strongly suspect that your BIOS is actually loading the boot loader from one of the other disks in your system, probably /dev/sdb. Unfortunately it is more or less impossible to reliably determine this from the operating system (I tried some years back and failed). I would recommend using "sudo dpkg-reconfigure grub-pc" to tell the GRUB packaging to install the boot loader to the master boot records of *all* the non-removable disks on your system, which avoids this class of problem since then it doesn't matter which one the BIOS boots from. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"
Am 03.03.21 um 18:00 schrieb Colin Watson: > On Wed, Mar 03, 2021 at 05:20:39PM +0100, Karsten wrote: >> there was no system update or an installation. It booted perfect. > Since you're reporting this against grub-pc 2.02+dfsg1-20+deb10u4, and > since the mentioned grub_register_command_lockdown symbol was only > introduced in that version, then there must have been a system update, > because we only released that version yesterday. A search shows in /var/log/apt/history.log Start-Date: 2021-03-03 09:28:01 Commandline: /usr/bin/unattended-upgrade Upgrade: grub-common:amd64 (2.02+dfsg1-20+deb10u3, 2.02+dfsg1-20+deb10u4), grub2-common:amd64 (2.02+dfsg1-20+deb10u3, 2.02+dfsg1-20+deb10u4), grub-pc:amd64 (2.02+dfsg1-20+deb10u3, 2.02+dfsg1-20+deb10u4), grub-pc-bin:amd64 (2.02+dfsg1-20+deb10u3, 2.02+dfsg1-20+deb10u4) End-Date: 2021-03-03 09:28:36 Start-Date: 2021-03-03 17:03:42 Reinstall: grub-pc:amd64 (2.02+dfsg1-20+deb10u4) End-Date: 2021-03-03 17:04:12 How can such "unattended-upgrade" be killed? An upgrade on an other partition to Debian 11 (Testing) failed, so it is not an good idea to use grub on an failed installation. > What does "sudo debconf-show grub-pc" say? > grub-pc/install_devices_empty: false grub2/device_map_regenerated: grub2/kfreebsd_cmdline_default: quiet grub-pc/disk_description: grub2/force_efi_extra_removable: false grub2/update_nvram: true grub-pc/install_devices_failed_upgrade: true * grub-pc/install_devices: /dev/disk/by-id/ata-TOSHIBA_DT01ACA200_84H86A0GS * grub2/linux_cmdline: grub-pc/partition_description: grub-pc/hidden_timeout: false grub-pc/install_devices_failed: false grub-pc/timeout: 5 grub2/kfreebsd_cmdline: grub-pc/kopt_extracted: false grub-pc/mixed_legacy_and_grub2: true grub-pc/chainload_from_menu.lst: true grub-pc/postrm_purge_boot_grub: false * grub-pc/install_devices_disks_changed: /dev/disk/by-id/ata-TOSHIBA_DT01ACA200_84H86A0GS-part3 * grub2/linux_cmdline_default: quiet
Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"
On Wed, Mar 03, 2021 at 05:20:39PM +0100, Karsten wrote: > there was no system update or an installation. It booted perfect. Since you're reporting this against grub-pc 2.02+dfsg1-20+deb10u4, and since the mentioned grub_register_command_lockdown symbol was only introduced in that version, then there must have been a system update, because we only released that version yesterday. > I simply switched the PC off and the next time it does not boot any more! > Every entry of the boot menu ends up with the attached screenshot. > > To recover the PC i had to boot an Debian 10 installation from SD-Card and > select recover of grub. > > I have no idea if this is reproducible and the search for such an error is > empty. > So i report it here, if someone has the same error. What does "sudo debconf-show grub-pc" say? -- Colin Watson (he/him) [cjwat...@debian.org]
