Thank you for clarifying the situation. That makes sense now that you mention it.
One issue is still puzzling me. When I’m debugging, I notice that the “hd” parameter is always passed as /dev/nvme0n1
even when I’ve configured it as /dev/nvme1n1
in the iPXE menu parameters. I understand that NVMe names might not remain consistent across boots, but shouldn’t the hd
parameter at least reflect the correct path set in the iPXE menu?
Another question is: how difficult is it to create an interactive deployment process where users can choose the disk for image deployment after the boot? Given that PCI naming persists after boot, can FOG simply use the variable set by the user as the target disk? Are there any limitations that would prevent implementing such a feature?