Topics created by montesd

@montesd Ok for that old version of FOG, you need to be on FOS Linux version 4.12.x to have the driver for the I219-LM or i219-V network cards. You can manually download the kernels from here: https://fogproject.org/kernels/

You will want to download
Kernel.TomElliott.4.12.3.64 and save it as bzImage
and
Kernel.TomElliott.4.12.3.32 and save it as bzImage32

Watch your case because it is important. These files go into /var/www/heml/fog/service/ipxe directory. Rename the existing files in case you have to back up.

Also you can try the latest kernels with
Kernel.TomElliott.4.19.64.64 and Kernel.TomElliott.4.19.64.21.32 but there is no grantee that they will work with the older inits (YMMV). These would latest kernels would supported the newest hardware with the risk of incompatibility with the inits (FOS Linux virtual hard drive).

Or use sysprep to power off the computer
Or run this command to properly power off the computer for cloning shutdown.exe -s -t 0

You found the issue with Windows 8+ where shutdown isn’t really shutdown but an enhanced sleep mode. Disabling fast boot actually puts the computer in a powered off state too.

@montesd What target OS are you capturing?

What mode are you using to capture the image (single disk resizable, single disk non-resiziable)?
In the partclone screen, is it capturing the image as raw (as if you have bitlocker enabled)?

I’m initially suspecting something wrong with the source disk itself. The error reporting out of partclone is not very good, so FOG makes the assumption that the server is out of disk space.

One way to debug this is to start another capture, but before you hit the submit button tick the debug check box, then submit the capture task.

PXE boot the target computer and then after a few screens of text (where you must press enter to pass) you will be dropped to a FOS Linux command prompt. At the FOS command prompt key in fog and press enter. This mode will allow you to single step through the image capture hopefully you will be able to capture the exact error message displayed in partclone. Also if you reach the error but partclone hasn’t told us what we need, we can look at the partclone error log. But lets start with the single stepping through the capture to see what the true error is.