Comment 9 for bug 2038401

Thank you for this clarification, Julian.

For your info: here is fstab of one of my problem devices:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=f02fe823-8605-48f6-823f-c20a5133ae8d / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=4480-184B /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0

mount and grep for "boot" gives me
root@8RZ1PL3:~# mount | grep "boot"
/dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

So /efi/boot is there and mounted

Background info: the devices were installed with a "minimal" installation, created an OEM, captured and distributed using fog. They only contain one disk. I don't change any disk / boot settings I'm aware of.

I would be very happy to check any other possible problems to find the root of this problem and avoid it happening in the future.