Posts made by totalimpact

@sebastian-roth In the back of my mind I was knowing that its something at a lower layer … I am the only admin on this network so I dont know how it self destructed from 1 day to the next, might consider a windows update, but moving dhcp off windows would rule that out. Will try a pcap.

Everything was working excellent and then I am unaware of any changes it just started taking 2+ minutes to boot PXE to the Fog menu and fail. The initial process of getting a DHCP address is super slow, finally after ~2 minutes the fog menu appears, I select full host registration, and it launches that and tries to get a new DHCP lease, which it times out after 20~30 seconds and gives up.

I can get tftp files from the fog server very fast using tftpd32. Booting windows normally I get dhcp leases instantly. I am on a gig switch directly connected to the windows dhcp server and fog server, I moved dhcp to the router on the same switch, same behavior… Ping times are 1ms on all devices, tried another downstream switch.

Fog server: Debian 10.8, Fog 1.59. The ipxe.efi file is dated 03/16/21 - I am pretty sure I have imaged some machines just fine around 04/05/21 just fine. Nothing has changed in my switching and routing environment, I rebooted all switches, router, servers. At a total loss, gonna try loading a fresh install of fog.

@george1421
It is Zstd, max 22 compression. Client has 8GB RAM.

Yes, sorry, mis-type, it is 5.10.x

Running Fog 1.5.9, latest kernel 5.6.19 in uefi mode, client has a nvme drive, the first partition captures, then 2nd is in progress and it crashes after sending 3.3gb, just says “An error has been detected”… And “Out of memory: Killed process”. The drive is a fresh Win10, about 20gb, image store has 66gb free. I have seen in another post 5.6.18 works on this hardware, tried it same results. Server is Debian 10.9, latest apt updates, kernel 4.19.0-16, has 6GB RAM free when it crashes. Not sure if it is the client or server that is causing the crash.

Well, that url is exactly what I needed!! however I gave up and made a new vm with Fog 1.5, it was able to image the 7040 with no issue… I just didnt want to deal with the partimage vs partclone thing, but it is looking good now.

Is there a way to manually download kernels from this site:
https://fogproject.org/kernels/kernelupdate_bootstrap.php

I have ready the wiki on manual upgrades, and did all that, but I think my kernels are still old. I am trying to get a Dell Optiplex 7040 to image, and it crashes during registration, or scheduled imaging. Hoping a newer kernel will solve it for my old 1.1 install.

The developers know that Windows 7 will always have a 100mb boot partition (many people dont even see it), and then some partition of random size, so this means there is only 1 partition FOG needs to manipulate, but if you add a 3rd partition in to the mix - how will Fog make the decision as to which needs resizing?? - this is why multi partitions cant be resized - and Win7 has 2 parts, but only 1 needing resizing - this is why Win 7 works as a “resizable single partition” scenario - the term doesnt fit, but it works.

I havent tried the scenario yet - but I know multi-partition to the same drive size works fine - hopefully development can chime in.

If its just a single failed system, Clonezilla would definitely work. In the future you might try changing your platform to single partition - it has saved me a ton of time and space.

Have you tried imaging the source drive as Single Drive / Single Partition?

FOG will create or delete partitions as it sees fit, you should not need to do any partitioning - but in multi partition scenarios, it will not resize the partitions on your new drive, only in single partition mode can it resize.

Yes - it will, not sure what instructions show that, but its mentioned all over the forum - use Single Disk/Single Partition for best performance - even on Win 7.

If it is the 2 partitions from Windows 7 (boot and C), it will still resize - its only when it gets beyond the base partitioning scheme of Win 7 (you used 3 partitions?) that resize will fail.