I image bare metal servers to CentOS 7 and 8 all of the the time via network DHCP/TFTP using UEFI options, from a CentOS 7 PXE server. I'm looking to also build Ubuntu 20.04 servers.

I've followed the docs, extracted vmlinuz and initrd from the casper dir of the Ubuntu ISO and just placed them at the base tftpboot dir. Things hum along, the ISO downloads to the client, after it enters BusyBox and fires up initramfs, it completes loading the ISO, but then stops at "Unable to find a live file system on the network". The thing is, I'm able to navigate and find the ISO on the client, and I'm even able to mount it and see that all of the contents are there.

I've used different ISOs (Ubuntu desktop, for example). I've verified sha sums of the ISO.

Here's the grub.cfg that I'm using, paring everything back to isolate the issue.


menuentry 'Ubuntu 20.04.2' {
  linuxefi /vmlinuz ip=dhcp url=
  initrdefi /initrd

menuentry 'CentOS 7.8' {
  linuxefi /centos/images/pxeboot/vmlinuz ip=dhcp inst.repo=
  initrdefi /centos/images/pxeboot/initrd.img

The CentOS install works just fine (/centos is the path to a dump of a CentOS ISO).

Is there anything I'm missing?


I've gotten this to work with the following parameters in my default config:

LABEL Ubuntu 20 LTS
    MENU LABEL Install Ubuntu 20 LTS
    KERNEL ubuntu20/casper/vmlinuz # On PXE server, relative to TFTP Root
    INITRD ubuntu20/casper/initrd
    APPEND autoinstall ip=dhcp interface=enp5s0 ds=nocloud-net;s=http://<mywebserver>/ubuntu2004/autoinstall/ucshadoop06/ url=http://<mywebserver>/ubuntu-20/liveserver-iso/ubuntu-20.04.1-live-server-amd64.iso

It works with and without the ds parameter. My current challenge is figuring out why the ds parameter does nothing. Let me know if you got any further.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.