[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#928750: marked as done ([grub-efi-amd64] On EFI pxeboot grubx64.efi only loads config when loaded directly)

Your message dated Mon, 17 Jun 2019 17:16:49 +0100
with message-id <20190617161649.GE20741@tack.einval.com>
and subject line Re: Bug#928750 - Bug in grubx64.efi triggered by shim?
has caused the Debian Bug report #928750,
regarding [grub-efi-amd64] On EFI pxeboot grubx64.efi only loads config when loaded directly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
928750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928750
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: grub-efi-amd64
Version: 2.02+dfsg1-16
Severity: important

--- Please enter the report below this line. ---

https://d-i.debian.org/manual/en.amd64/ch04s05.html mentions that you need to 
configure
  filename "debian-installer/amd64/bootnetx64.efi";
as bootfile for booting via PXE in dhcp configs.

When doing so, grubx64.efi will be loaded in the next step, but will not try
to load its config files and - after 30s wait time showing the attached screen on console
present the Grub shell.
(As mentioned in https://lists.debian.org/debian-boot/2019/05/msg00076.html)

Excerpt from logs:

May  8 16:02:07 ssfnctl111 dhcpd: DHCPREQUEST for 10.45.10.32 (10.45.10.5) from 0c:c4:xxx via eth0
May  8 16:02:07 ssfnctl111 dhcpd: DHCPACK on 10.45.10.32 to 0c:c4:xxx via eth0
May  8 16:02:07 ssfnctl111 in.tftpd[21355]: RRQ from ::ffff:10.45.10.32 filename debian-installer/amd64/bootnetx64.efi
May  8 16:02:07 ssfnctl111 in.tftpd[21355]: tftp: client does not accept options
May  8 16:02:08 ssfnctl111 in.tftpd[21356]: RRQ from ::ffff:10.45.10.32 filename debian-installer/amd64/bootnetx64.efi
May  8 16:02:08 ssfnctl111 in.tftpd[21357]: RRQ from ::ffff:10.45.10.32 filename debian-installer/amd64/grubx64.efi
(Nothing re tftp afterwards)

If you change the boot option in dhcp. conf to
  filename "debian-installer/amd64/grubx64.efi";
it changes to:

May 10 10:51:20 ssfnctl111 in.tftpd[16770]: RRQ from ::ffff:10.45.10.32 filename debian-installer/amd64/grubx64.efi
May 10 10:51:20 ssfnctl111 in.tftpd[16770]: tftp: client does not accept options
May 10 10:51:21 ssfnctl111 in.tftpd[16771]: RRQ from ::ffff:10.45.10.32 filename debian-installer/amd64/grubx64.efi
May 10 10:51:21 ssfnctl111 in.tftpd[16773]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/command.lst
May 10 10:51:21 ssfnctl111 in.tftpd[16773]: sending NAK (1, File not found) to ::ffff:10.45.10.32
May 10 10:51:21 ssfnctl111 in.tftpd[16774]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/fs.lst
May 10 10:51:21 ssfnctl111 in.tftpd[16774]: sending NAK (1, File not found) to ::ffff:10.45.10.32
May 10 10:51:21 ssfnctl111 in.tftpd[16775]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/crypto.lst
May 10 10:51:21 ssfnctl111 in.tftpd[16775]: sending NAK (1, File not found) to ::ffff:10.45.10.32
May 10 10:51:21 ssfnctl111 in.tftpd[16776]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/terminal.lst
May 10 10:51:21 ssfnctl111 in.tftpd[16776]: sending NAK (1, File not found) to ::ffff:10.45.10.32
May 10 10:51:21 ssfnctl111 in.tftpd[16777]: RRQ from ::ffff:10.45.10.32 filename /grub/grub.cfg
May 10 10:51:21 ssfnctl111 in.tftpd[16777]: sending NAK (1, File not found) to ::ffff:10.45.10.32

After adding a symlink in /var/lib/tftpboot/ grub -> debian-10/debian-installer/amd64/grub
(additional to debian-installer -> debian-10/debian-installer), Grub will load and we can chose a menu
to start our preseeded install:

May 10 10:53:55 ssfnctl111 in.tftpd[18546]: RRQ from ::ffff:10.45.10.32 filename debian-installer/amd64/grubx64.efi
May 10 10:53:55 ssfnctl111 in.tftpd[18546]: tftp: client does not accept options
May 10 10:53:55 ssfnctl111 in.tftpd[18547]: RRQ from ::ffff:10.45.10.32 filename debian-installer/amd64/grubx64.efi
May 10 10:53:56 ssfnctl111 in.tftpd[18548]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/command.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18549]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/fs.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18550]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/fs.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18551]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/fs.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18552]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/fs.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18553]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/crypto.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18554]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/crypto.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18555]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/crypto.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18556]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/terminal.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18557]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/terminal.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18558]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/terminal.lst
May 10 10:53:56 ssfnctl111 in.tftpd[18559]: RRQ from ::ffff:10.45.10.32 filename /grub/grub.cfg
May 10 10:53:56 ssfnctl111 in.tftpd[18560]: RRQ from ::ffff:10.45.10.32 filename /grub/grub.cfg
May 10 10:53:56 ssfnctl111 in.tftpd[18561]: RRQ from ::ffff:10.45.10.32 filename /grub/grub.cfg
May 10 10:53:56 ssfnctl111 in.tftpd[18562]: RRQ from ::ffff:10.45.10.32 filename /grub/font.pf2
May 10 10:53:56 ssfnctl111 in.tftpd[18563]: RRQ from ::ffff:10.45.10.32 filename /isolinux/splash.png
May 10 10:53:56 ssfnctl111 in.tftpd[18563]: sending NAK (1, File not found) to ::ffff:10.45.10.32
May 10 10:53:56 ssfnctl111 in.tftpd[18564]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/play.mod
May 10 10:53:56 ssfnctl111 in.tftpd[18565]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/play.mod
May 10 10:53:56 ssfnctl111 in.tftpd[18566]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/play.mod
May 10 10:53:56 ssfnctl111 in.tftpd[18567]: RRQ from ::ffff:10.45.10.32 filename /grub/x86_64-efi/play.mod


--- System information. ---
Architecture: 
Kernel:       Linux 4.19.0-4-amd64

Debian Release: buster/sid
  990 testing         security.debian.org 
  990 testing         ftp2.de.debian.org 
  990 buster          download.docker.com 

--- Package information. ---
Depends                        (Version) | Installed
========================================-+-==================
debconf                        (>= 0.5)  | 1.5.71
 OR debconf-2.0                          | 
grub-common            (= 2.02+dfsg1-16) | 2.02+dfsg1-16
grub2-common           (= 2.02+dfsg1-16) | 2.02+dfsg1-16
grub-efi-amd64-bin     (= 2.02+dfsg1-16) | 2.02+dfsg1-16
ucf                                      | 3.0038+nmu1


Package's Recommends field is empty.

Package's Suggests field is empty.

Attachment: Screenshot_20190509_113044.png
Description: PNG image

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
On Mon, Jun 10, 2019 at 09:13:55PM +0200, Michael Kesper wrote:
>Hi Steve,
>
>On 10.06.19 18:57, Steve McIntyre wrote:
>> In fact, I'm looking at a different fix: using a specific build of the
>> Grub netboot image with the d-i prefix configured. Watch this space!
>
>Thanks for investigating and keeping me informed! :)

And thanks for the bug report in the first place. :-)

It's taken a little time for all the pieces to come together, but
we're just about there. I've just pushed changes to the d-i build to
use that new Grub netboot binary. The next build of the installer
overnight tonight will have this fix included, so I'm marking this bug
as done.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"Yes, of course duct tape works in a near-vacuum. Duct tape works
 anywhere. Duct tape is magic and should be worshipped."
   -― Andy Weir, "The Martian"

--- End Message ---
Reply to: