Can not deploy using multicast - read image_hdr block_size error

[george1421]

@rurap The 16.04 version will not dynamiclly support uefi and bios the 18.1 will. Now certain firmware needs an additional kick to get it to boot.

In this section add in the fog server’s IP address.

pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

change it to

pxe-service=X86PC, "Boot to FOG", undionly.kpxe,192.168.25.117
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi,192.168.25.117
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi,192.168.25.117

Then restart dnsmasq

[george1421]

@rurap The more I look at your picture the more I think it should be working. (I can see that its not) but the auto select says “Booting to FOG” so that means its getting and processing this line:

pxe-service=X86PC, "Boot to FOG", undionly.kpxe

We can see in the picture the boot server IP is 192.168.25.117, so we know its processing this line.

dhcp-boot=undionly.kpxe,,192.168.25.117

It should have everything it needs to boot.

We may need to grab a packet capture to see what the client is objecting to.

[rurap]

@george1421
your suggestion did not work. I looked for TFTP troubleshoting like @Sebastian-Roth says and used the command:

tftp -v x.x.x.x -m binary -c get undionly.kpxe

and i have got nothing.
I searched the system a bit and found something like this:
this is my tftp-hpa configuration file

# /etc/default/tftpd-hpa

TFTP_USERNAME="tftp"
TFTP_DIRECTORY="/var/lib/tftpboot"
TFTP_ADDRESS=":69"
TFTP_OPTIONS="--secure"

there are no files in this directory, so where is the undionly.kpxe?

[george1421]

@rurap Please check to see if the files are in /tftpboot directory. It sounds like the tftp service didn’t get configured properly for fog to function.

As I said dnsmasq should have been working, with that final change (which you will probably want to remove now) if it didn’t work then we would have focused on the tftp server. So you did good moving forward to debug.

So if the files are in /tftpboot change the file path in the tftp config file to match then restart the tftpd service.

[rurap]

@george1421

There is no / tftpboot directory.

I install everything again, I have no idea what happened to this catalog. I could have sworn that this catalog was yesterday.

[george1421]

@rurap If you simply rerun the fog installer it will recreate these files in the proper location.

Also you can search the entire disk for these files with sudo find / -name undionly.kpxe

[rurap]

@george1421

YES, It’s works !!! Such a simple misteake, thx for patience and everything

I was looking for this file, it wasn’t there, I reinstalled FOG and magic happend ;]

Now I will be testing multicast !!! Keep your fingers crossed, i will let you know

[rurap]

@george1421

Multicast is working, but …

First I used my old switch TP-LINK TL-SF1024 and it’s faild. Two PCs restored at a rate of 150MB/min,

Second time I used LinkSys LGS308, 8 x 1Gb ports. I start to restore 2 other PC and only one turn on from network, second i turn on by my self but the multicast session starting, and both PC restore at rate of 10GB/mmin. Then I connect third PC to the switch and strat multisession once again one PC turn on but second and third i have to turn on. Again multicast worked very well (10GB/min at each PC)

Do you have an idea why only one PC wake on LAN?
Whether the old switch may not support multicast?

[george1421]

@rurap Some small/older switches don’t have the internal bandwidth capable to send out multicast streams to all switches. On your tp-link switch, if it has a management interface see if it has an option for igmp snooping or anything regarding to multicasting and sparse mode or dense mode. You may just want to shop on ebay for older enterprise switches from HP or Cisco.

As for wake on LAN, that is a feature that needs to be enabled in the computer’s firmware to support WOL. I’m sure the FOG server is sending out the WOL packet, the computer has to be configured to accept it.

[rurap]

@george1421

thank you george, the current switch is unmanaged, it’s a simple switch. There is not much in the specification of the switch, so I bet that switch is the problem.
All PCs are the same and support WOL and on the old switch they all turn on, but I will check it, maybe one of the students has changed something in the BIOS