On Wed, Aug 07, 2019 at 11:19:55AM +0200, J. Pietschmann wrote: > The problem appears to be that grub 2.04 uses only devices by disk-id > and didn't install on /dev/sda even though grub 2.02 did.
No, that's incorrect. GRUB 2.02 behaved just the same way; you just didn't notice the problem because you happened to have a GRUB core image installed on /dev/sda that was compatible with the GRUB modules that you had installed at the time. Things were already broken but you just didn't know it yet. I've said this in this bug already, but I'll keep repeating it: this is *not* a behaviour change in GRUB 2.04. > Fortunately > dpkg-reconfigure grub-pc > fixes the calamity. > What's the preferred way to reinstall grub on a new disk with 2.04? > Preferrably non-interactive/scriptable. "dpkg-reconfigure grub-pc" is preferred. Doing this noninteractively is possible but fiddly: you'd need to figure out the by-id paths for your disks and then do something like this (obviously substituting the correct by-id paths rather than the example ones I've used): echo 'grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/ata-foo /dev/disk/by-id/ata-bar' | sudo debconf-set-selections sudo dpkg-reconfigure --unseen-only grub-pc (I would not disagree that this should be easier; but this has been the case for a long time, and isn't new in 2.04.) -- Colin Watson [cjwat...@debian.org]
