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.

@Tom-Elliott previous numbers I gave you are all the result of fdisk command

$ cat 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= 49330360, type=83
/dev/sda4 : start= 765794304, size= 15626240, type=82

$ cat 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= 48807402, type=83
/dev/sda4 : start= 765794304, size= 15626240, type=82

@Tom-Elliott then in this case, it didn’t reapply the original partition table, I have to use gparted to resize the partition.

@Tom-Elliott The first one is the original, the second one is the original after I upload image, upload shouldn’t make any changes on the partition, right?

@Tom-Elliott There is something wrong. After I reinstalled FOG, uploaded a resizable partition, then downloaded the image to another computer. Both the base image computer and the new computer’s partition table got changed.

Here is the partition table before upload the image:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 765794303 298764288 142.5G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris

Here is the partition table on the base image computer after upload the image:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 516360375 49330360 23.5G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris

Here is the partition table on the new computer:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 383646 381599 186.3M 7 HPFS/NTFS/exFAT
/dev/sda2 383647 870205150 869821504 414.8G 7 HPFS/NTFS/exFAT
/dev/sda3 870205152 961146436 90941285 43.4G 83 Linux
/dev/sda4 961146438 976772677 15626240 7.5G 82 Linux swap / Solaris

When I define the image, I used Linux as the Operating System, but it looks like the partition table changes are only affecting the Linux partitions, should I choose a different Operating System for the image?

Now I feel regret, I should have upload a non-resizable image first, I didn’t expect it will change the partition table when uploading an image…

No, the image is not double captured. I will try to capture a fixed partition image today to see if it will work, since most of my lab computers are using the same size hard drives, but it would be nice to have the resizable partitions work.

Thanks!

Re: Hard drive resize is not expanding##### Server

• FOG Version: 1.3.5 RC 10
• OS: Red Hat Enterprise 6.8

Client

• Service Version:
• OS: Ubuntu 16 & Windows 7 dual boot

Description

Re: Hard drive resize is not expanding

Today I’m trying to download an image created with FOG 1.3.2 to another computer, and then I discovered the resizable partitions are not expanding. So I update the server to the latest dev version. Still get the same problem, then I upload a new image with the FOG 1.3.5, then downloaded it again, still get the same problem, but better, this time Windows partition seems expanded, but the Linux partiton is still only 22GB.

Here are the current partition table on the problem computer:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 519291975 52261960 24.9G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris

Here is the partition table on the computer I’m taking the image (they both have the same size hard drive):
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 765794303 298764288 142.5G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris

Here is the d1.partition (this used to be called d1.original.partitions under FOG 1.3.2) file on the FOG server:

cat 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= 298764288, type=83
/dev/sda4 : start= 765794304, size= 15626240, type=82

Here is the d1.original.partitions file created under FOG 1.3.2 on FOG server:

cat d1.original.partitions

partition table of /dev/sda

unit: sectors

/dev/sda1 : start= 2048, size= 204800, Id= 7, bootable
/dev/sda2 : start= 206848, size=466823168, Id= 7
/dev/sda3 : start=467030016, size=298764288, Id=83
/dev/sda4 : start=765794304, size= 15626240, Id=82

And I’m sure the resizable partition works perfectly under FOG 1.3.2.

Thanks,
Hongyun

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

@george1421 Thanks! I will wait for the stable release then, it’s not super urgent

@Tom-Elliott Can you let me know where to download 1.3.5? I got a version by using git clone command, but the version I downloaded still have the same problem.

git clone https://github.com/fogproject/fogproject.git