FOG Failed Partition Issue
We just all the sudden started receive a failed partition error on all our Lenovo T470 models. It appears to be only with our 2004 Windows 10 images and above, 1909 images work just fine. This is the error we receive.
The image is set to Single Disk - Resizable, Partition Everything, Compression 10, Partclone Gzip. We are running FOG version 22.214.171.124.
Since it only seems to be the newst version of Windows 10 images having this issue could it be that we simply need to update to the latest version of FOG?
@imagingmaster21 IMO you have multiple things wrong here, all of them giving you a different error.
I would nuke the fogproject git repo directory and reclone it from github then rerun the fog installer.
Beyond that you need to confirm the FOG server ip address has not changed since fog was installed. You can do this by viewing the hidden config file
/opt/fog/.fogsettingsif that file contains a different IP address than is currently set you need to fix that too.
Once you have all of that fixed then you need to ensure you have the 5.6.18 FOS Linux kernel installed.
If you still have issues, open a new thread for each issue so we can keep the problems isolated.
Your branch is behind 'origin/master' by **1023** commits.. src/buildroot/package/fog/scripts/bin/fog.download
Those two lines of the output tell us that you haven’t used that git repo for a very long time. That path doesn’t even exist in that repo anymore. While I am not sure what the local change is (you can check via
git diff) I would guess that a
git reset --hardis the way to go forward.
Mind you, this topic is going all over the place, from partition issue to PXE/DHCP issue to git repo questions. We really try hard to help but this is high potential for confusions and I ask you to just open new topics for each question you have. New topics don’t cost you anything and it’s way easier to follow each issue and find a solution more quickly.
@george1421 I am not sure if this is related or not but I went back up through the command line from the update and it looks like there was a error when doing the git pull command
Should I maybe go through the install again with doing a git reset --hard?
@imagingmaster21 I’m not sure how I missed this the first time. But the error message is a bit misleading. DHCP IS working correctly. When we see this error message it typically indicates the client can’t ping the FOG server. So if you changed the IP address of the fog server you need to resync everything. If you have not changed the IP address of the FOG server since it was installed then you need to look into network routing.
Note: This specific issue is not inline with the title of this thread.
Then rename them to match bzImage and bzImage32 exactly. Rename the original files before you download these new ones just in case. You need to sudo or install them as root to write into this directory
The download should work. If your fog server is behind a proxy server then you should set the proxy server settings in the fog configuration page.
Would it be possible to download the kernels from somewhere else and then just copy them over to the directory?
Sure, download from https://fogproject.org/kernels/ and put into
/var/www/html/fog/service/ipxe/(renaming the current
By the way, the output of /var/www and /var/www/html look fine, no duplicate web directory.
yes that is what I went through, and I verified the ramdisk size and didn’t have any luck.
Can you please be more specific. What exactly happened when you used the init mentioned in the other topic? Take a picture of the error on screen and post here. “No luck” could be anything really and we can’t know what you mean.
@george1421 since I am not able to download/install them within FOG. Would it be possible to download the kernels from somewhere else and then just copy them over to the directory?
@sebastian-roth here is the results of that command:
@sebastian-roth yes that is what I went through, and I verified the ramdisk size and didn’t have any luck. I remember having to set the ramdisk to 275000 a year ago because of an issue back then.
We did test with the same computers as used before the update, so it is kinda weird.
I ended up having to do the update, because our ramdisk size was correct and we were still having the issue. We but a computer up to pull an image and after you go through the PXE menu to select a image it gives this error.
Can you please explain in more detail. If ramdisk size was set to 275000 already then you should be able to just follow this: https://forums.fogproject.org/topic/15025/move-partition-in-gpt-layout-need-people-to-test (manually download the init and test)
I can’t imagine why you’d see a DHCP issue now. Are you sure this particular computer was able to fully PXE boot to be captured before. George is right that updating to 1.5.9 will install the default kernel again. But on the other hand we actually see udhcpc do it’s work on eth0 and I can’t imagine this to be an issue of missing a driver in 4.19.x kernel.
@george1421 It does not look like it is downloading. I checked that directory and the downloaded one is not their going off the modify date.
@imagingmaster21 So when you select the download
You don’t get a Download Started message?
You can check the version of the kernel by doing this on the fog server’s linux console
cd /var/www/html/fog/service/ipxe file bzImage file bzImage32
The file command will print out the version of the kernel that is installed.
@george1421 When I go to hit install for that Kernel it does not load anything.
@imagingmaster21 When you update FOG it will roll the kernel back to the last LTS version (4.19.x). Just manually upgrade the FOS Linux kernel to 5.6.18 again and you will be all set.
@sebastian-roth I ended up having to do the update, because our ramdisk size was correct and we were still having the issue. We but a computer up to pull an image and after you go through the PXE menu to select a image it gives this error.
We verified the interface and dhcp is up. Any ideas?
@imagingmaster21 Windows 10 2004 rearanged the partition layout in a way that is making resizing a lot harder because it puts a recovery to the end of the disk.
We have a new FOS init that should be able to capture and deploy those 2004 installes properly but it’s still in kind of a pre-testing stage. You can follow the instructions here to give it a try: https://forums.fogproject.org/topic/15025/move-partition-in-gpt-layout-need-people-to-test
As you are using an older version of FOG you might into an issue using that init. Either you update to 1.5.9 before testing or you might also be able to use it by adjust a setting manually: FOG Configuration -> FOG Settings -> expand all and search for size in the browser. Change the init ramdisk size from 127000 to 275000.