@adamhyla89 said in 11th Gen Intel Kernel:

it states cannot open ` /var/www/fog/service/bzImage’ (no such file or directory)

Better copy & paste the commands to not miss anything. So again: file /var/www/html/fog/service/ipxe/bzImage* /var/www/fog/service/ipxe/bzImage*

The install on the VM is only command line, no GUI for Ubuntu.

There is no GUI (for Ubuntu) needed as you can access the FOG web UI from another computer. I guess you have used it already because how would you manage FOG or even get past the schema update when you don’t access the FOG web UI.

@sebastian-roth Many thanks Sebastian, I will do that.

@totalimpact See if you can get a good image capture with 11. I’m not saying this is the problem, but the higher the compression with zstd the more memory it requires because it needs to hold larger chunks of the image in ram memory.

The other option it could be is that we need to increase the amount of virtual hard drive space for FOS linux. But first lets see if lowering the compression ratio will help.

@sebastian-roth You correct, I just used the file of that new kernel and it worked.

@george1421

For those wondering who came across this thread like me: If you are using the built in DHCP server in ubuntu fog you need to edit the dhcp.conf file by opening a terminal and typing: sudo nano /etc/dhcp/dhcpd.conf and replacing “ipxe.efi” with “snponly.efi”. Worked fine with the M75s after making those changes.

@dmaret I have done some more reading on topics that show the same error messages (1, 2) and the more I read the more I can imagine the messages from the Realtek driver not to be the cause of the problem but maybe just one of the symptoms of a kernel issue (even a soft crash) just before that.

Do you have more than one of these Lenovo ThinkCentre M70a? Have you tried deploying to different ones? Do all show the same issue? Just trying to rule out this is not a hardware issue on one of the machines.

I am not too sure how to take this further. We don’t see other error messages on screen. Does the partclone screen seem to freeze completely after the error messages come up?

Maybe you can schedule a debug deploy task, boot up the machine, set a root password (command passwd), check the IP address (ip a s) and connect to it via SSH. Now you have two command shells to go ahead. Start the deployment (command fog) on the machine directly and step through it. Meanwhile also issue a command on the SSH shell just to see it’s still up and running. Especially when the blue partclone screen starts you want to stick around in the SSH shell to see if that freezes at some point - e.g. just type random characters to see if they appear on screen or stop at some point.

If partclone stops but your SSH shell still works, then run dmesg | tail -20, take a picture and post that here.

@george1421

Sorry for the late reply,1) and 2) are both correct recompiled ipxe.efi works fine

@greg-plamondon yes.

@detoss Looking back at your original post you mentioned it doesn’t compress the drive. If you watch the blue partclone screen its probably capturing in RAW mode. It will do that if you have bitlocker or any drive encryption system enabled. Since it can’t read the files it just does a RAW sector copy of the disk.

@george1421 here’s where I’m at now.
Laptop: Dell Latitude 7490
FOG: 1.5.8
I was able to change the settings in the BIOS on the client machine allowing the FOG to recognize the clients and registering. I was able to successfully re-image 1 machine. (yay!) Now I have had 3 machines give me an (same) error (unable to locate image store (/bin/fog.download)) in the deploying image process. Any thoughts on what’s causing this? I’ve read everything that looked remotely close to the same issue with no luck. FOG_unable to locate image store.jpg

@tom-elliott

This solution worked for us,

And juste for the information, we also had to disable bitlocker, but we saw that information in another thread , in a command prompt , as admin " manage-bde -off C : "

Thank you !

Thank you everyone. I tried again and I was able to successfully register that computer. I did re-try adding the 32bit and 64bit Kernels via the web gui and when I run the above commands on the server I get a return showing the 5.10.12 kernel.

root@fogsrvr:~# file /var/www/html/fog/service/ipxe/bzImage*
/var/www/html/fog/service/ipxe/bzImage: Linux kernel x86 boot ex ecutable bzImage, version 5.10.12 (buildkite-agent@Tollana)…

root@fogsrvr:~# file /var/www/fog/service/ipxe/bzImage*
/var/www/fog/service/ipxe/bzImage: Linux kernel x86 boot executable bzImage, version 5.10.12 (buildkite-agent@Tollana) …

So again thank you for your help.

@sebastian-roth Well yes I see that now. It just felt like a familiar problem from whenever I change kernels. Should have just restarted and tried again before assuming something was broken though.

@yeet The startech adapter is not supported by your HP firmware.

So that startech adapter is an external usb to ethernet adapter, right?

Since the HP uefi firmware doesn’t show that startech adapter as bootable, the built in PXE roms will not work. So instead of using the onboard PXE roms, we can load FOG’s iPXE from a usb flash drive. Once iPXE is loaded then imaging happens normally.

How the boot order goes is this:
(UEFI) PXE ROM -> downloads and launches iPXE -> downloads and launches bzImage (FOS Linux).

So if the pxe roms don’t work we can just launch iPXE from a usb flash drive and hope that iPXE has the drivers for the nic built in.

If iPXE won’t configure that startech adapter, then you can skip iPXE and just load FOS Linux on the usb stick and not use iPXE.

The reason why I said USB-2 network adapter is that the older the adapter is the better the chance that both iPXE and FOS Linux will have a built in driver for it.

@tom-elliott
Normally I always disable TPM and Secure Boot before Imaging a machine - whether Capture or Deploy.

The fact that TPM wasn’t in the BIOS got me started on this, and disabling TPM worked like normal when the PS commands were run.

The issue with that command - I just ran it on the machine I Deployed to. BitLocker was never enabled - I get this error:

ERROR: An error occurred (code 0x80310008): BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker.

Looked at BitLocker through Control Panel? Turned off.
Right-clicked the <C: > drive in “This PC”? Asks if you want to Enable it.

That’s why I was looking for TPM and not BitLocker.

EDIT:
I know I said “machine I Deployed to”. I didn’t have BitLocker enabled on the machine I Captured - my fix was disabling TPM.

@sebastian-roth

Once I setup a bridged virtual network adapter for the vm within the
KVM Virtual Machine Details, I was able to make everything communicate.

Issue Resolved. 🙂

@sebastian-roth Obviously!
We had a bad factory BIOS setup and didn’t think about looking into more detail … our fault!
Thanks a lot for your help, from the outside the problem is often more quickly identifiable;)

@ewojcik said in Missing QLogic FastlinQ driver:

Thinking long-term sustainment, are there user methods for getting additional firmware (or drivers) built in? I found the wiki instructions for building custom kernels but those don’t cover additional firmware blobs.

Sure, good point. Unfortunately the wiki has several articles on kernel buildung and some are very dated. As well you are right, even the latest one does not include information on how to add binary firmware blobs: https://wiki.fogproject.org/wiki/index.php?title=Build_TomElliott_Kernel#Build_TomElliott_Kernel_for_FOG_0.33b_and_newer

I’ll give you the hints here in the forum and will add this to the wiki soon:

Follow the steps in the wiki article up where it says you should run make menuconfig or make oldconfig. Now either edit that file manually, search for CONFIG_EXTRA_FIRMWARE, simply add the relative path of the firmware blob you want to that line (separated by spaces) and run make oldconfig or run make menuconfig, navigate to Device Drivers -> Generic Driver Options -> Firmware loader and edit the second option starting with (bnx2x/... (a list of files) Save config and build the kernel

We are also working towards updating all the documentation (wiki) and move it to readthedocs. You are very welcome to help if you like.

@george1421Nothing changed, reinstalled 1.5.7. Sorry for the delay.

@redbull007 Understood not fog. But where in the process is it failing.

PXE Rom requests dhcp address
PXE Rom DORA sequence where it gets the boot server and boot file
PXE ROM downloads the boot file from the boot server
iPXE starts up
iPXE Requests dhcp address.

If its in the iPXE then I thought of a test we can do

The tcpdump from the fog server point of view will tell us what the target computer is exactly asking for. That is the logic why to use it there. The test gives the best details if the target computer and fog server are on the same subnet to grab the packet capture.