curtin

  1. Bug #1789650
  2. Comment #13

Comment 13 for bug 1789650

Revision history for this message
Rod Smith (rodsmith) wrote :

Ryan and Andres, here are some things you've requested....

The attachment is the /root/curtin-install* files from a server that works as expected. (That server is jehan, a Quanta D52B-1U, FWIW.) Here are the before and after "efibootmgr -v" outputs from jehan:

ubuntu@jehan:~$ sudo efibootmgr -v
BootCurrent: 0006
Timeout: 5 seconds
BootOrder: 0006,0008,0007,0005,0009,000A,000B,000C,0000,0003
Boot0000* ubuntu HD(1,GPT,489c1060-e2fd-4f57-b2e4-beb55dec5764,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0003 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0005* UEFI: Slot5 Port0 HTTP IPv4 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/MAC(a81e84f296c5,0)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()..BO
Boot0006* UEFI: Slot5 Port0 PXE IPv4 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/MAC(a81e84f296c5,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0007* UEFI: Slot5 Port1 HTTP IPv4 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x1)/MAC(a81e84f296c6,0)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()..BO
Boot0008* UEFI: Slot5 Port1 PXE IPv4 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x1)/MAC(a81e84f296c6,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0009* UEFI: Slot5 Port0 HTTP IPv6 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/MAC(a81e84f296c5,0)/IPv6([::]:<->[::]:,0,0)/Uri()..BO
Boot000A* UEFI: Slot5 Port0 PXE IPv6 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/MAC(a81e84f296c5,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot000B* UEFI: Slot5 Port1 HTTP IPv6 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x1)/MAC(a81e84f296c6,0)/IPv6([::]:<->[::]:,0,0)/Uri()..BO
Boot000C* UEFI: Slot5 Port1 PXE IPv6 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x1)/MAC(a81e84f296c6,0)/IPv6([::]:<->[::]:,0,0)..BO
MirroredPercentageAbove4G: 0.00
MirrorMemoryBelow4GB: false

After re-deploying:

ubuntu@jehan:~$ sudo efibootmgr -v
BootCurrent: 0006
Timeout: 5 seconds
BootOrder: 0006,0008,0007,0005,0009,000A,000B,000C,0000,0003
Boot0000* ubuntu HD(1,GPT,6cdb926d-5f7b-4f83-a88d-d9a65ff43d3b,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0003 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0005* UEFI: Slot5 Port0 HTTP IPv4 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/MAC(a81e84f296c5,0)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()..BO
Boot0006* UEFI: Slot5 Port0 PXE IPv4 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/MAC(a81e84f296c5,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0007* UEFI: Slot5 Port1 HTTP IPv4 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x1)/MAC(a81e84f296c6,0)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()..BO
Boot0008* UEFI: Slot5 Port1 PXE IPv4 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x1)/MAC(a81e84f296c6,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0009* UEFI: Slot5 Port0 HTTP IPv6 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/MAC(a81e84f296c5,0)/IPv6([::]:<->[::]:,0,0)/Uri()..BO
Boot000A* UEFI: Slot5 Port0 PXE IPv6 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/MAC(a81e84f296c5,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot000B* UEFI: Slot5 Port1 HTTP IPv6 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x1)/MAC(a81e84f296c6,0)/IPv6([::]:<->[::]:,0,0)/Uri()..BO
Boot000C* UEFI: Slot5 Port1 PXE IPv6 Intel(R) 82599 10 Gigabit Dual Port Network Connection PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x1)/MAC(a81e84f296c6,0)/IPv6([::]:<->[::]:,0,0)..BO
MirroredPercentageAbove4G: 0.00
MirrorMemoryBelow4GB: false

These outputs are identical except for the GUID of the ESP on the Boot0000 line, which of course changed when the server was re-deployed.

One difference I've noticed between this system and the problem computers is that the problem computers have just one PXE-boot entry, whereas the working system has multiple PXE-boot entries, one for each network device. I'm skeptical that this is relevant, since there must be other servers with just one PXE-boot entry, but I thought it was worth mentioning. (Note that the problem computers do have multiple bootable network devices, but the firmware seems to fold them all into a single entry, as seen by efibootmgr and the firmware's own boot manager.)

As to Andres' questions, both the systems initially had firmware version 2.01, released in April of 2016. I checked, and more recent firmware is now available -- version 2.50, released in October of 2017. I upgraded one system (jolteon) to the new firmware and re-tested it. This change had no effect; the system still comes up set to boot from Shim/GRUB on the hard disk after deployment, rather than PXE-booting.

Also, the efibootmgr and firmware setup tools on the problem system (jolteon in my tests) show the same boot order, although the latter hides several options. Specifically, after installing, the firmware setup utility shows the boot order as:

<ubuntu>
<PXE Network>
<Hard Disk 0>

After adjusting this order in the firmware to PXE-boot first, efibootmgr in Ubuntu shows PXE-boot first (BootOrder beginning with 0002 -- see the original problem report or post #4). After re-deploying, both efibootmgr and the firmware show the "ubuntu" option first in the boot order. Thus, the firmware setup utility and efibootmgr in Ubuntu show consistent results; it doesn't look like there's a disconnect between the two.