Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"

Karsten debian at decotrain.de
Thu Mar 4 07:43:19 GMT 2021


Hello Colin,

Am 03.03.21 um 19:03 schrieb Colin Watson:
>> How can such "unattended-upgrade" be killed?
> I can't help you with that, but it shouldn't be too hard to find
> documentation.

I just purged the package unattended-upgrades now.

> [...]
>> * 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 have no idea what the BIOS is doing there.
I have not altered anything all the time.
Yesterday the error appears and has gone after the manual installation,
without altering the BIOS settings (see screenshots).

So this is the configuration all the time:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   1,8T  0 disk
├─sda1   8:1    0    10G  0 part
├─sda2   8:2    0    40G  0 part
├─sda3   8:3    0    40G  0 part
├─sda4   8:4    0     1K  0 part
├─sda5   8:5    0   256M  0 part [SWAP]
├─sda6   8:6    0    40G  0 part /win
└─sda7   8:7    0   1,7T  0 part /srv
sdb      8:16   0 119,2G  0 disk
├─sdb1   8:17   0    40G  0 part /
├─sdb2   8:18   0    40G  0 part /P2
└─sdb3   8:19   0  39,2G  0 part

A general question:
It's not possible that grub work independent from the BIOS?
The BIOS is doing more and more things the user does not want.

> 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.

I understand what you want to avoid with this, but if the SSD fails,
it make no sense to boot a wrong grub according to the installed OS
on the HDD.

Cheers
karsten
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BIOS.1.jpg
Type: image/jpeg
Size: 207060 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20210304/3888e3bb/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BIOS.2.jpg
Type: image/jpeg
Size: 166930 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20210304/3888e3bb/attachment-0003.jpg>


More information about the Pkg-grub-devel mailing list