So the storage driver is OK, since we’re clearly getting far enough into the boot process for systemd-repart to create the last three partitions. But I don’t see either swap or the root partition active in the lsblk output, which isn’t a good sign. Typically this will occur if something’s wrong with the state of the TPM that IncusOS expects to see. Since this system is trying to run directly from the USB drive, we haven’t yet been able to run the normal IncusOS pre-start checks which include checking the TPM.
I did just verify that IncusOS 202512060041 boots and runs from a virtual USB drive in an Incus VM.
It would be useful if @n00q could try setting an install seed on the USB image and booting that. It will fail because no other drives are present, but if we can get to that message we’ll at least know that IncusOS can boot up and that there’s likely some sort of issue activating the swap and/or root partitions on that system. And if there’s some sort of TPM issue, we’ll get an nice error about that, too.
The only other recent similar issue I’m aware of is IncusOS got stuck while trying to install - #5 by fred-bloggs , which was stuck on the “IncusOS is starting…” screen because of a GPU issue. It looks like this system is using an integrated GPU, so hopefully that’s not the root cause.