ubuntu jammy 22.04 iso: unable to find a live file system on the network

This is going to be a casper and/or livecd-rootfs issue, so reassigning.

What I don't understand is that neither the blkid output nor the contents of /cdrom/.disk/casper-uuid-generic appear to match what I have here:
$ blkid ~/devel/iso/ubuntu-22.04-live-server-amd64.iso
/home/vorlon/devel/iso/ubuntu-22.04-live-server-amd64.iso: BLOCK_SIZE="2048" UUID="2022-04-21-06-14-25-00" LABEL="Ubuntu-Server 22.04 LTS amd64" TYPE="iso9660" PTUUID="c84e0225-4be7-447a-9fa1-ebf040bdc01f" PTTYPE="gpt"
$ cat /mnt/.disk/casper-uuid-generic
ba2335f2-81b6-46b2-a037-549fe52a8261
$

I don't know how blkid is figuring a UUID for an iso9660 filesystem, but here it is the timestamp of the image on the server, which is preserved by wget. It's surprising that yours has a timestamp months in the past...

Would you confirm that the sha256 sum of the iso matches https://releases.ubuntu.com/22.04/SHA256SUMS ?

I'm getting different results for the above commands.
The UUID there makes it look like you have a 2-month out of date iso.
Thanks!

# lsblk /dev/loop17 -J -O | jq '.blockdevices[0] | .label, .uuid'
"Ubuntu-Server 22.04 LTS amd64"
"2022-04-21-06-14-25-00"

# cat .disk/casper-uuid-generic
ba2335f2-81b6-46b2-a037-549fe52a8261

I did a test run of this using the instructions from https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 and things look good to me. Would you also try that and let us know?

I'm marking this "incomplete" since I can't reproduce the issue and that's the bug state used when more info is needed.

Oh indeed, somehow I ended up using an older iso. I deleted everything and started from scratch, and now this works as expected!

Sorry for wasting your time :-(

Hi, I just ran into exactly this problem with the 22.04.3 ISO freshly downloaded today. I copied the same NFS-based PXE-boot configuration as I used for 20.04:

        MENU LABEL Ubuntu 22.04 x64 LTS Server
        KERNEL installroot/Ubuntu/22.04/server/casper/vmlinuz
        APPEND boot=casper netboot=nfs nfsroot=192.168.1.12:/srv/pxe/installroot/Ubuntu/22.04/server initrd=installroot/Ubuntu/22.04/server/casper/initrd toram ip=dhcp root=/dev/nfs
        TEXT HELP
        Boot Ubuntu 22.04 x64 LTS Server
        ENDTEXT
        MENU LABEL Ubuntu 20.04 x64 LTS Desktop
        KERNEL installroot/Ubuntu/20.04/desktop/casper/vmlinuz
        APPEND boot=casper netboot=nfs nfsroot=192.168.1.12:/srv/pxe/installroot/Ubuntu/20.04/desktop initrd=installroot/Ubuntu/20.04/desktop/casper/initrd toram ip=dhcp
        TEXT HELP
        Boot Ubuntu 20.04 x64 LTS Desktop
        ENDTEXT

I added 'root=/dev/nfs' and it didn't help. However, adding 'ignore_uuid' did allow it to progress and start booting. Does sound like there's an issue with Casper here.

Cheers,
Rob J

We faced this issue too, it was caused by having the initrd and vmlinuz from a previous Ubuntu ISO

```
KERNEL vmlinuz # <= should be from casper/vmlinuz in Ubuntu ISO
INITRD initrd # <= should be from casper/initrd in Ubuntu ISO
APPEND root=/dev/ram0 ramdisk_size=1500000 ip=dhcp cloud-config-url=http://192.168.0.2/autoinstall.yaml url=http://192.168.0.2/ubuntu-22.04.3-live-server-amd64.iso autoinstall
```

See for example https://github.com/canonical/autoinstall-desktop#pxe-configuration

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1969970