MAAS stuck on grub prompt during second reboot on deploy

Discourse
1

Hi,

I’ve been trying to get my arm64 servers deployed through MAAS and am running into an issue where it keeps getting stuck in grub on a prompt and requires manual intervention (reboot cmd via kvm). Once rebooted it seems to then proceed as it should.

In the UI logs I notice when it fails only sends the 3 files below:
TFTP Request - bootaa64.efi
TFTP Request - bootaa64.efi
TFTP Request - grubaa64.efi ← fails here and ends up in grub prompt

On reboot/successful run it proceeds to additionally send the below files:
TFTP Request - /grub/grub.cfg-xx:xx:xx:xx:xx:xx
TFTP Request - /grub/grub.cfg
TFTP Request - /grub/arm64-efi/terminal.lst
/grub/arm64-efi/crypto.lst
/grub/arm64-efi/fs.lst
/grub/arm64-efi/command.lst

Any ideas why it may be failing/getting stuck here?

Stuck:
chrome_Cs47IMsnsW

Success:
chrome_3uP1ZigkjH

MAAS UI Log (Note timestamp):

xRDlGudSpa
xRDlGudSpa712×525 59 KB

2

Are your machines set to UEFI? Is your MAAS ipmi boot type set to UEFI? These are my initial sanity checks when I run into this issue.

3

I believe it is already set to UEFI. MAAS also correctly set the power boot type as EFI when it commissions the machine.

image

image

4

Are there any BMC f/w updates available? What NIC are you using?

5

It’s an intel I350 onboard NIC. I was going to test on a different connected NIC but strangly enough, changing the connection to the 2nd eth port seems to have “fixed” this issue. I’m not wholly certain why this is the case.

6

Could’ve been a bad onboard port. That’s the story I’m going to run with =)
Glad you got it working!

7

I’m facing the same issue, and the machines are already configured to use UEFI. Is there a way to enable additional logging to help troubleshoot why it fails after the reboot?

8

does it fail with the same message on the screen?