@Romain-0 I cannot read the Francais, but I have seen this message before.
Have you disabled Secure Boot? Can you boot with a built-in network card as opposed to a USB one?
OK, I’ll update, then report back. Thank you.
@george1421 My driver injection script (which I believe is the “new” one above) works with 21H2 golden images on both Windows 11 and Windows 10.
This feels much better!
Upgraded Fog to 1.4.4, and captured the image, deployed it, and was presented with my AD Login screen! It logged me in, then restarted… Then let me log in properly.
A couple things I need to change on the image, but over all, this is much better than where I was before! Thank you for the advice
@sow20 Are there any error messages that appear when it restarts the capture?
Can you try building your image in a VM so you can take advantage of snapshots? Snapshot before SysPrep, snapshot after SysPrep, reboot the VM and check things work, then revert to the snapshot and try to capture the image.
@Scootframer On your server, navigate to the folder you downloaded fog to, and run
git checkout dev-branch. Then, re-run the
./bin/installfog.sh script to install the latest version.
If you only have 3.9 GB of free space, I’m going to guess that it’s running out of space before it can set the permissions (but someone else would have to verify that for me). The partitions are supposed to be saved into that dev folder until captured, then it gets moved over and renamed.
@limbooface Is this still an issue? If not, I’ll close this issue.
@limbooface So on a fresh Rocky 8.9 (the latest version in the 8.x stream) available, the install goes without a hitch.
Having the same issue on a Dell Latitude 3140. There is no option for RAID, only AHCI and Off. Secure boot is disabled, UEFI security mode set to disabled on PXE/Internal HDD. Updated to the latest FOG dev version, Kernel version 6.1.22.
Clonezilla will recognize the drive, but not the FOG kernel.
@Sebastian-Roth I’ll take a look - haven’t touched Red hat stuff for many many years though! Lol
lvextend -L +398g ubuntu-lv --resizefs
You may need to reboot for it to take effect. This will use all the remaining LVM volume space for your logical volume. You can’t go smaller after the fact, so be sure you want to use it all first.