@george1421 Yes it is. Both, the fog server and the host device, are in VirtualBox - and i get the error message.
But tbh if the problem doesn’t show up when deploying the whole system in my network, i can live with the error occurring in VB.

If it’s true that this only happens in VB and not on the actual network (and then Toms solution works), then this issue is resolved for me.

iPXE itself is pretty powerful when it comes to menus and booting options, obviously your results may vary from distro to distro or application to application etc. etc.

This example is using the Advanced menu, with subcategories etc.
I haven’t had much need for this in a while due to my work changing the way the boot system here works breaking things out of my control, but this is a post from a few years back that should still work but you would need you to look up specific settings per distro based on what you are trying to do.

https://forums.fogproject.org/topic/7329/sub-menu-within-fog-advanced-menu

This guy has some impressive examples: https://gist.github.com/robinsmidsrod/2234639

Additional information DHCP Options:
https://gist.github.com/robinsmidsrod/4008017

Example for Sysrescue:
https://gist.github.com/robinsmidsrod/1c7bbd4a058f0e6892df

Results may vary. ¯\_(ツ)_/¯

Just figured this has been added already thanks to @Piotr86PL’s pull request in August (which I had obviously forgotten about, nevermind).

@Eruthon Thanks for the quick feedback. Should be all fine now I think. No need to post partition files as long as it works for you now.

@wmw509 Disabling CSM makes sense. I’ve seen a lot of bioses that if CSM is enabled it only lets you use the legacy/bios pxe boot. I’ve had that disabled on all my hardware for so long I forgot it was a thing.

@mckayj said in iPXE won't find network cards:

some super new network cards iPXE can’t talk to

I’m more suspicious of 10G nics than super new cards. I don’t know off the top of my head if iPXE supports 10G cards. Or it may be a combination of super new and 10G. ??

As long as you have a path forward then use it.

@Tom-Elliott said in Could not boot:

ing your storage node IP to

I had the same problem starting from 1.4.0-RC-2 . Added another storage node with the fog-server ip and some fantasy user/password -> works

@sebastian-roth

Hi sorry, I couldn’t answer any sooner.
“Nevertheless we ought to try out using the SNP binary (debug enabled - DEBUG=snp:3,nii:3 to start with). So find 01_snp.efi here. Just give it a try and post pictures or video. Make sure when you take those to place the camera or phone on a stack of books in front of the screen so we have a good picture.”

Here you go, not much to say from my side but here goes: video

Thanks!

Bonjour @Sebastian-Roth

Mon problème était bien la version du kernel mais pour mettre à jour le kernel il fallait que je rentre le proxy donc oui tu avais raison.

Maintenant j’ai un nouveau problème voici le message d’erreur

---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

############
Hello @Sebastian-Roth

My problem was indeed the version of the kernel but to update the kernel I had returned the proxy so yes you were right.

Now I have a new problem here is the error message

---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)