FOG 1.5.4 - capture win 10 (1903) - issue

[adamkesy]

Hi

I have prepared PC with legacy boot only (UEFI disabled).
Windows 10 is a fresh version (1903) prepared as MBR image.
Fog version: 1.5.4

I updated the kernel manually to bxImage and init.xz based on https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update.

I have a problem with capture windows image.
After the kernel upgrade i have error: XZ-compressed data is corrupt

PC specification:
HP ProDesk 600 G4 Desktop Mini PC 1
2YE33AV Intel Core i5 8500T 2.1 2666MHz 6C 35W CPU 1
2YE91AV 8GB (1x8GB) DDR4 2666 SODIMM Memory 1
2YE96AV 256GB M.2 2280 PCIe NVMe Solid State Drive 1
2YE38AV G4/G5 DM 35W SATA Drive Bracket 1
2YF22AV Intel 9560 ac 2x2 nvP +Bluetooth 5 WW

Can you please advise what I can check/do with this issue?

Also, when i use kernel bzImage Version: 4.16.6, then i have issue with fixparts:

There are details about debug capture:

[fra1771]

Hi,

I have the same problem, with my FOG 1.5.4 after a kernel update

My PC is a HP Probook 600 G4.

The PXE Boot works perfectly before the kernel upgrade (i tried to install the first kernel, but doesn’t works)

[Sebastian Roth]

@adamkesy @fra1771 With newer kernels/ints you need to manually change a settings. Go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000. Then boot the client again and IT should not throw the error anymore.

[adamkesy]

@Sebastian-Roth said in FOG 1.5.4 - capture win 10 (1903) - issue:

275000

Seems like now it is ok.
Thank you!

This new value in kernel ramdisk size can be impacted for previous images/hosts somehow?

[Sebastian Roth]

@adamkesy said in FOG 1.5.4 - capture win 10 (1903) - issue:

This new value in kernel ramdisk size can be impacted for previous images/hosts somehow?

No, this should Not cause an trouble unless you have machines with less that 512 MB RAM which is very unlikely these days…