@george1421 Thanks! I just upgraded FOG, and it works perfectly

We have a separate DHCP server, the fog server only provide PXE boot. I can try disable firewall. But because I don’t want to affect the lab usage, I have already roll back to the 1.4.0 version, which works fine with our current settings.

@wayne-workman Here are the httpd error log:

[Mon May 14 14:00:51 2018] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon May 14 14:00:51 2018] [notice] Digest: generating secret for digest authentication …
[Mon May 14 14:00:51 2018] [notice] Digest: done
[Mon May 14 14:00:51 2018] [notice] Apache/2.2.15 (Unix) DAV/2 mod_auth_tkt/2.1.3 (Opsview) mod_ssl/2.2.15 OpenSSL/1.0.1e-fips mod_wsgi/3.2 Python/2.6.6 mod_perl/2.0.4 Perl/v5.10.1 configured – resuming normal operations
[Mon May 14 14:00:51 2018] [error] avahi_entry_group_add_service_strlst(“142.103.243.243”) failed: Invalid host name
BFD: /var/www/html/fog//service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss

No, all the systems. We have computers with only Linux or dual boot.

I upgrade our FOG server to the 1.5.2 version today, but after the upgrade, PXE boot halt, and won’t pass to start the computer.

Attached image is what I see on the client screen.

Here is the message log on the server:
May 14 14:02:21 foggy kernel: FWALL: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:70:71:bc:1f:ff:b6:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=20 ID=1 PROTO=UDP SPT=68 DPT=67 LEN=556
May 14 14:02:23 foggy kernel: FWALL: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:70:71:bc:1f:ff:b6:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=20 ID=2 PROTO=UDP SPT=68 DPT=67 LEN=556
May 14 14:02:23 foggy xinetd[1919]: START: tftp pid=6474 from=142.103.243.44
May 14 14:02:23 foggy in.tftpd[6475]: tftp: client does not accept options
May 14 14:02:23 foggy in.tftpd[6476]: Client 142.103.243.44 finished undionly.kpxe
May 14 14:02:28 foggy kernel: FWALL: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:70:71:bc:1f:ff:b6:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=437 TOS=0x00 PREC=0x00 TTL=64 ID=256 PROTO=UDP SPT=68 DPT=67 LEN=417
May 14 14:02:29 foggy kernel: FWALL: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:70:71:bc:1f:ff:b6:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=437 TOS=0x00 PREC=0x00 TTL=64 ID=549 PROTO=UDP SPT=68 DPT=67 LEN=417
May 14 14:02:35 foggy kernel: FWALL: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:70:71:bc:1f:ff:b6:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=449 TOS=0x00 PREC=0x00 TTL=64 ID=2018 PROTO=UDP SPT=68 DPT=67 LEN=429
May 14 14:02:35 foggy in.tftpd[6485]: Client 142.103.243.44 finished default.ipxe

Does anyone know what might be the problem? This is affecting all our lab computers now, if I reboot any of them it will stop on this screen .

Thanks,
Hongyun

@Tom-Elliott OK, I just downloaded the image to another computer, and it works. Thanks!

@Tom-Elliott I reinstalled FOG, and then uploaded an image, but it looks like the d1.partitions and d1.minimum partitions are still the same:

[root@foggy henn205u16win7]# more d1.partitions
label: dos
label-id: 0x242a986c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 466823168, type=7
/dev/sda3 : start= 467030016, size= 491393024, type=83
/dev/sda4 : start= 958423040, size= 18350080, type=82

[root@foggy henn205u16win7]# more d1.minimum.partitions
label: dos
label-id: 0x242a986c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 466823168, type=7
/dev/sda3 : start= 467030016, size= 49760206, type=83
/dev/sda4 : start= 958423040, size= 18350080, type=82

@Tom-Elliott You are right, the two files are identical. I will try again. but will let you know the result tomorrow, I’m afraid I don’t have enough time to finish both upload and download before I leave for today. Thanks!

@Tom-Elliott Yes, I already did this. Updated FOG, then changed the image from non-resizable to resizable, then upload the image, and downloaded to another computer. All works perfectly. Thanks again!

@Tom-Elliott Yeah! It’s resized properly this time. Thank you so much for your quick response and quick fix!!!

@Tom-Elliott No, I didn’t change any partition settings, I only installed some updates, and then started the upload process. And this is a newly created image, I might have changed it to non-resizable, and then changed back to resizable, but these changes are on FOG WebGUI, before I issue the upload task.