Topics created by Cire3

Ok, as I hate people that don’t come back. I try my best not to be that guy.

FOG problem = Nope… As usual.

Problem with dropouts, scrambled data. Proxmox 8 is very angry with my onboard nic. It uploads without issue (and very fast I may say) But deployment it just crapped out. Every time it re-connected, Fog just tried to do it’s job over and over. The blast of data just shut the nic down.

Finally found this looking in the Proxmox log. Found ethernet adapter hang detected, then reset.

Also a great excuse to finally order that dual 10Gb card. She’s happy now running full speed. Hopefully faster when the 10Gb switch shows up 🙂

Thanks to all that looked over this, and even more for the reply. !

@Cire3 said in Chainloading Simple Next Server ?:

server:ipv4 10.22.24.8
set newbootfile netboot.xyz.efi
set net0.dhcp/next-server ${newserver}

You are missing the word set in the first line.

So I looked at the autoexec.ipxe file and this is what is in it :

OK then it looks like netboot.xyz uses ipxe (because of your autoexec.ipxe script)

So you might not need all of those set commands. Because FOG used iPXE as its boot loader AND netboot.xyz also uses iPXE, AND iPXE is already running in memory, all you should need to do is call that autoexec.ipxe script.

This is all that should be needed in the parameter block of the fog menu.

chain tftp://192.168.1.1/autoexec.ipxe || goto Menu

Where 192.168.1.1 is the ip address of your netboot.xyz boot server. There is a 50/50% chance of this not working because if they compiled custom stuff in iPXE that might be dependent.

@Cire3 said in Not a Fog problem, but solution ?:

Carbon X1 Gen 7 just returns to boot menu after Downloading NBP file

Check secure boot is off and if the proper boot loader is being sent to the target computer.

You might use a witness computer on same subnet as the pxe booting computer. Use a capture mask of port 67 or port 68 or display filter of bootp Start the capture, pxe boot to error and then stop the capture. You will see the DORA process (discover, offer, request, ack/nack). Look at the offer packet this is coming from the dhcp server to the target computer. Look to see if both the ethernet header (bootp part) has next-server of IP address of fog server and boot-file as the proper boot loader name. Now confirm that dhcp options 66 and 67 are set properly. Its up to the pxe boot firmware vendor to decide to use bootp fields or dhcp option fields to locate the boot information. If you grab the pcap I can look at it for you if you get lost or not sure.

@Cire3 Lets start with what version of FOG are you running

What does the image definition look like for the one that doesn’t deploy? Is everything stored on the root partition or did you add a new disk (originally) to contain your images? What does the output of df -h and lsblk look like?

@Cire3 Hey I’m glad you have it worked out. You found one of the gotchas with naming (No special characters as the first character in the names).

@Cire3 said in Can't see Images in menu after manually uploading.:

The compression scale also must match huh ?

Sorry, I didn’t mean the compression scale but the compression format…

@Cire3 said:

What I was shocked at was the speed… I would have done this a long time ago if I knew how freakishly fast this was going to be !

I hit on this point all the time. People never believe just how large of an improvement there is.

I’m happy that you got it going, and pleased that I helped make that happen. 🙂

-----OP reported success - thread solved.