On 2019-07-12 23:24 +0200, Diederik de Haas wrote: > Package: grub-efi-amd64 > Followup-For: Bug #931896 > > I don't have grub-efi-amd64 installed, but I ran into the same problem. > The only enabled lines in /etc/default/grub are these: > GRUB_DEFAULT=0 > GRUB_TIMEOUT=5 > GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` > GRUB_CMDLINE_LINUX_DEFAULT="quiet" > GRUB_CMDLINE_LINUX="" > > Which, afaik, is the default. > The versions reported are what's currently installed as with 2.04 my > system doesn't boot. > > I'm not sure/don't understand what Colin meant with 'firmware'. My guess > would be my BIOS, but I haven't changed that recently.
It is the system's firmware, called UEFI on modern systems or BIOS on older ones, where you would install grub-pc rather than grub-efi-amd64. > But up until version 2.04 grub2 has worked perfectly well and I don't > recall me having configured anything manually, so I wouldn't know why > it would be misconfigured. Most likely you had grub configured to install to the wrong disk, this is what happened to me. When I installed an SSD into my old PC back in December 2016, I copied all files from the already present hard drive, ran "grub-install /dev/sdb" and told the BIOS to boot from the SSD (which is /dev/sdb). Everything was working fine until I upgraded grub-pc to version 2.04. What I finally figured out after getting my system to boot again, is that grub was still configured to install its core image to /dev/sda, the old hard disk. This configuration is apparently only stored in the debconf database and nowhere else. > I can send my grub.cfg in a separate email if that would help. > (How can I do a followup with bugreport so that the full output is > reported as you'd get with an initial filing of a bug?) You can run "reportbug --template grub-pc" and paste the output to your preferred mailer. Cheers, Sven