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
