PXE over IPv4 no boot device available

Users
1

I am using a headless Ubuntu 22.04 server for region+rack. I have imported images and discovered. Everything seemed to be operating correctly before the weekend (June 28 -29 2025). The target server was automatically discovered by MAAS and an Ubuntu 24.04 image was being pxe booted onto the target server with a cloud-init error. I came back in on Monday to move forward with commissioning the server. However, when I turned the server back on (maas $profile machine power-on $id) I am no seeing that it timesout due to the following:

>>>Start PXE over IPv4
Station IP address is 192.168.xx.xxx

Server IP address is 192.168.xx.xxx  #This still points to the previous MAAS IP. But, is still a valid IP in DHCP.
NBP filename is bootx64.efi
NBP filesize is 0 bytes
PXE-E18: Server response timeout. 
...

No boot device available.

I did try several BIOS and iDRAC configuration changes and subnet/interface updates. Along with completely removing then reinstalling MAAS and Postgres. Plus, clearing any remaining directories associated with MAAS and Postgres. The MAAS api ip did change.

Is this a configuration issue? or, is this a server issue in not clearing out something?

2

maybe you have a wrong MAAS URL in the regiond.conf?

3

In general I would suggest to sudo snap remove --purge maas and the database and start from scratch

4

It has the correct URL.

5

I have started from scratch twice now.

6

How? Do you have another DHCP server on the network?

7

Yes, I have another DHCP server running. I had to create a new VLAN for PXE only, to separate conflicts with the existing DHCP server. Then just assign the ports for the target servers. After that, create an interface to the PXE network on the region+rack server. Then create the VLAN, subnet, and dynamic IPs in MAAS. After that, MAAS picked up the target servers and executed the boot.efi.

8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.