Can you describe your ipc setup a bit more? Did you do the baremetal install, or does the IPC run a host OS and is UMH running in VM's?

It is a bare metal install. Flash a USB stick with the correct image, and put it into the IPC. That's it 😄

In my setup the IPC runs proxmox and i have a VM for UMH..

or go for this, might be probably better for developing playing around with

Makes sense. During the bare metal install I ran into issues with the drive selection step. Followed the troubleshooting guidance, but the problem was unresolved. https://umh.docs.umh.app/docs/production-guide/installation/flatcar-installation-bare-metal/#drive It seemed like no matter what, the OS would install over the .iso on the USB stick, or if I tried to avoid this by unplugging the USB drive after setup began, I would get a "no bootable devices found" error after the install finished. Tried UEFI and BIOS, still ran into the same problem. Also tried attaching a temporary drive using an onboard SD card reader and an external SD card reader, no joy. Even tried RAIDing my two onboard NVME drives into a RAID0 array, no joy with this approach either. I've pivoted back to trying to install on a VM.

During iPXE and the Initial Installation you can select the drive where you want to install it on. Seems you have nvme, so you should be able to select there nvme0

From my notes, I believed the target drive should have been "nvme0n1". There were other items in the lsblk result that I did not write down. I'll be back in the office tomorrow and I will reproduce from the beginning to provide more information about the lsblk result.\

Does your IPC have secure boot ? If so, try to disable it, because our ipxe image is not signed.

Secure boot exists in the BIOS, but it has been disabled. Sorry this is taking me so long to get the lsblk info. Long story, but I still plan to get it done today.

And selecting in the installer nvme0n1 did not work?

The installer presents these options: nvm0n1 nvm1n1 nvm2n1 these did not work. Selecting the "Custom Token" option and entering nvme0n1 did not work either.

ok, let us double check it with a device with nvme here, and maybe we are able to reproduce

That would be great. No rush, I'm working around this issue by running the lab environment on a windows machine for now.