On Sat, Feb 09, 2019 at 01:38:10AM +0100, Robert Senger wrote: >Package: grub-efi-amd64 >Version: 2.02+dfsg1-10 >Severity: important > >Dear Maintainer, > > > * What led up to the situation? >Installed Debian Buster on mdraid 1 (2 disks) system using debootstrap. Disks >are partitioned to allow both UEFI and legacy boot. Configured things in >chroot. Installed grub-efi-amd64 and grub-pc-bin package. > > * What exactly did you do (or not do) that was effective (or > ineffective)? >Ran "grub-install --target=i386-pc /dev/sda", "grub-install --target=i386-pc >/dev/sdb" to install grub in bios-grub partition, "grub-install >--target=x86_64-efi --no-nvram --removable" to install grub into efi partition, >done in chroot on laptop with disks attached via usb and mdraid started. Moved >disks to target system. Tried to boot up. > > * What was the outcome of this action? >System does not boot, neither UEFI nor legacy mode. GRUB drops to shell. > > * What outcome did you expect instead? >Expected to get to GRUB menu. > > * Workaround >Downgraded all GRUB packages to current Debian Stretch versions. No other >changes. Ran "grub-install ..." in chroot as above. Moved disks to target >system. Result: System boots fine in both UEFI and legacy mode. >Upgraded GRUB to Buster versions on running target system, reinstalled GRUB >(both legacy and efi). After that, system does not boot any more, as above. > > * Note >System information is not from affected server system, it's from the laptop >that's running reportbug.
Hi Robert, Can you please show the output from your grub-install command lines please? I'm surprised that this ever worked for you even in Stretch, I'll be honest! -- Steve McIntyre, Cambridge, UK. st...@einval.com "C++ ate my sanity" -- Jon Rabone
