[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode

[Andres Rodriguez]

Hi Rod,

Is this with Secure boot enabled? Could you also please attach:

Tcpdump of the pxe process for the specific MAC address.


That said, if there are other servers that boot fine in EFI mode, this, to me, would normally indicate that there is a bug in grub itself or in the firmware. I’m opening a task against grub.

** Changed in: maas
       Status: New => Incomplete

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1752687

Title:
  Quanta D52B-1U unable to PXE-boot in EFI mode

Status in MAAS:
  Incomplete
Status in grub2-signed package in Ubuntu:
  New

Bug description:
  Certification recently received a Quanta D52B-1U server (jehan). This
  server enlists, commissions, and deploys fine in BIOS/CSM/legacy mode;
  however, in EFI/UEFI mode, it fails, hanging at the "grub>" prompt;
  here's a capture from an IPMI SOL session:

  >>Checking Media Presence......
  >>Media Present......
  >>Start PXE over IPv4. Press ESC key to abort PXE boot.
    Station IP address is 10.1.10.164

    Server IP address is 10.1.10.2
    NBP filename is bootx64.efi
    NBP filesize is 1196736 Bytes

  >>Checking Media Presence......
  >>Media Present......
   Downloading NBP file...

    Succeed to download NBP file.
  Fetching Netboot Image

  
                     GNU GRUB  version 2.02~beta2-36ubuntu3.16

     Minimal BASH-like line editing is supported. For the first word, TAB   
     lists possible command completions. Anywhere else TAB lists possible   
     device or file completions.                                            

  
  grub> ls
  (memdisk) (hd0) (hd1) (hd1,msdos1) (hd2) (hd2,gpt1) 
  grub> ls (memdisk)/
  grub.cfg 
  grub> less (memdisk)/grub.cfg
  error: can't find command `less'.
  grub> cat (memdisk)/grub.cfg
  if [ -e $prefix/x86_64-efi/grub.cfg ]; then
          source $prefix/x86_64-efi/grub.cfg
  else
          source $prefix/grub.cfg
  fi

  grub>

  The interaction at the end ("ls" and other commands at the "grub>"
  prompt) is me trying to identify the GRUB environment; these commands
  were not entered automatically.

  I've tried dozens of combinations of firmware settings (enabling and
  disabling various options), with no success; the system always seems
  to fail at the same point.

  I've been unable to enlist the node in EFI mode; and once enlisted in
  BIOS mode, commissioning it in EFI mode fails. Because commissioning
  sets up partitions, including the critical EFI System Partition (ESP),
  which are different between BIOS- and EFI-mode boots, I have been
  unable to test deployment in EFI mode.

  Other systems have commissioned and deployed from this MAAS server
  both shortly before and after discovering the problem with jehan.

  This bug is similar in symptoms to several other "hang-at-grub>" bugs,
  such as bug #1690878 and bug #1437024; however, I have yet to find a
  workaround, and this problem occurs 100% of the time.

  I'm attaching the contents of /var/log/maas/* to this bug report.
  Here's the MAAS version information:

  $ dpkg -l '*maas*'|cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name                            Version                              Architecture Description
  +++-===============================-====================================-============-==================================================
  ii  maas                            2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          "Metal as a Service" is a physical cloud and IPAM
  ii  maas-cert-server                0.2.30-0~76~ubuntu16.04.1            all          Ubuntu certification support files for MAAS server
  ii  maas-cli                        2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          MAAS client and command-line interface
  un  maas-cluster-controller         <none>                               <none>       (no description available)
  ii  maas-common                     2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          MAAS server common files
  ii  maas-dhcp                       2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          MAAS DHCP server
  ii  maas-dns                        2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          MAAS DNS server
  ii  maas-proxy                      2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          MAAS Caching Proxy
  ii  maas-rack-controller            2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          Rack Controller for MAAS
  ii  maas-region-api                 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          Region controller API service for MAAS
  ii  maas-region-controller          2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          Region Controller for MAAS
  un  maas-region-controller-min      <none>                               <none>       (no description available)
  un  python-django-maas              <none>                               <none>       (no description available)
  un  python-maas-client              <none>                               <none>       (no description available)
  un  python-maas-provisioningserver  <none>                               <none>       (no description available)
  ii  python3-django-maas             2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          MAAS server Django web framework (Python 3)
  ii  python3-maas-client             2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          MAAS python API client (Python 3)
  ii  python3-maas-provisioningserver 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all          MAAS server provisioning libraries (Python 3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1752687/+subscriptions