@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?
@george1421 @Sebastian-Roth I downloaded those files and rebooted the server and still experiencing the same error. Forgot to mention that after doing this update this error now occurs on all models.
https://photos.app.goo.gl/KYX9kzcnMzE9trS88
@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.
@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.
@george1421 When I go to hit install for that Kernel it does not load anything.
@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.
https://photos.app.goo.gl/svncs4TSVPo69Zii7
We verified the interface and dhcp is up. Any ideas?
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.
https://photos.google.com/share/AF1QipPQ7bzuLaoUnO8yzEW76HH2KpoCUi5YeEAQidmqmCnqezi2UKk3DJfwNKZ32a24DQ?key=c2o3UzAzcmJHOTYtcVgyOUR2bFZZRFFEQ0VHelNB
The image is set to Single Disk - Resizable, Partition Everything, Compression 10, Partclone Gzip. We are running FOG version 1.5.6.5.
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?
@Sebastian-Roth Machine was working fine after re-image and then started having performance issues mainly with Office and did Office repair. We are probably going to pull machine back and do another RAM test along with Lenovo diagnostics. Maybe just even replace RAM.
We do want to upgrade but we have been pretty swamped withe people working from home, so hopefully we can do this when things settle down 
@Sebastian-Roth The machine has 4G of Ram. I hit memtest on the FOS drive and it then started imaging and it looks like it is working mysteriously. Probably would not be a bad idea to update our version.
I have a Lenovo 13 laptop that I am trying to image and it give the error message below. It is a machine that does not have an Ethernet port so I am using a Ethernet to USB adapter with the FOG FOS USB. At the end of imaging is when it gives this error. I am currently running version 1.5.6.5.
I did try to look at the /var/log/partclone.log and could not find it in the system. Any ideas on how to fix this? This only seems to be an issue with machines using the USB-Ethernet adapter with the FOS drive. All other machines with straight Ethernet image just fine.
@Daniel-Miller I looked into the speeds, auto-negotiating was set however the speed was messed up. It seems the port on the switch went bad. Plugged into another port and got the correct speed. Imaging seems to be back to normal now.
@Sebastian-Roth No we did not update any of the BIOS.
We are all the sudden experiencing image deployment slowness on all our images. This just started today. We did not make any changes to any of our images or FOG server recently. We are currently running version 1.5.6.5. I did try rebooting the server and the switch and still the same result.
I made sure all the BIOS settings were correct and also did a factory reset. I have a Lenovo T470 and Lenovo E490 that are taking about 30 minutes to an hour to deploy an image. I tried several images we had on the server and all them took a extremely long time. Usually we are able to deploy within 5 to 10 minutes, now it is 30 to 60 minutes.
Any suggestions as how to resolve this?
@Sebastian-Roth We have imaged 20 computers of different models without the issue. So far so good.
@Sebastian-Roth
That error is fixed. We are imaging a large batch of computers now, I will let you know how the disk space is on them after we image and check them.
@Sebastian-Roth @Tom-Elliott
Ok I did that and rebooted the FOG server and got this error message on a T440 and T490:
Would it be worth updating to 1.5.7?
@Tom-Elliott @Sebastian-Roth @Quazz
I tried imaging a machine on our FOG Mobile server that has 1.5.6.4 that has the same hit or miss issue with incorrect partition/full C:. Here is the debug:
@Quazz @Sebastian-Roth I actually ended up reading that post this morning. We do have two FOG servers on the same version. Our main one is stationed at our office which is the one I’ve been getting the info off of.
The other one is our mobile version (we like to call it that) simply installed on a laptop, it does have the same issue however it is on version 1.5.6.4, whereas our main one is on 1.5.6.5. I will run a debug task on our mobile one also while it is on 1.5.6.4 sometime this afternoon hopefully.