@Pilar Somehow lost track of this. You still run into this issue?

The output you posted seems file so far. What about exportfs -v (please post output here as well)?

Is 111.111.111.111 your FOG server IP?

Is there a firewall on the FOG server or somewhere along the route between host machine and FOG server?

if I change the path of the image in the node it does NOT create a new exports with the current

I am still not sure I understand what you meant here.

@sebastian-roth Thank you. I have not exchanged .efi for .*pxe, it’s what’s in the configuration by default. I’ve only added the “authoritative;” line and changed the UEFI 64 files to intel.efi instead of ipxe.efi. Also, I’ve also used snponly.efi which returns the same result with intel.efi. I decided to use snponly.efi for the meantime while on testing stage.

@handso said in Dell 5090 MFF restores during the capture process. HELP!:

The Linux Kernel is 5.10.71 Tom Elliott arm64.

I am just wondering about the arm64 part. Probably just what you copy & pasted when grabbing the version but I still want to bring this to attention.

So I did the capture through the debug method. Unfortunately no error message outputted on the screen during the capture. It happens around 8% of disk 3 being cloned. It just exited directly and restarted.

As George already said this is hardly ever the case with FOG. So we don’t have a simple step by step guide to debug this issue yet. There is a slight chance that updating to dev-branch can help because we updated the FOS inits to a newer buildroot version just recently. Though the Linux kernel version has not changed much (5.10.86) and I don’t think that’s gonna make the difference. But it’s still worth a try.

If that doesn’t help I suggest you take a video of the screen while capturing. Make sure you setup the camera/smartphone (on a pile of books for example) to get a steady recording. Some cameras even allow for 60 fpm videos. This way we might have a chance to see even a very brief error message flashing the screen just before it reboots.

@jshaver @george1421 Well done!

As far as the upgrade: although it seemed to finish with an error concerning updating the PHP components, the node showed the latest version in the console. Not sure what’s up with that, but it looks like the upgrade fixed this issue.

You might want to post the error log here so we see what went wrong and if it’s worth investigating. You find the log in /root/fogproject/bin/error_logs/...

@cparsons The short answer is you have 2 dhcp servers on your network and one of them are not handing out dhcp option 66 to the pxe booting computer.

Is your FOG server on the same subnet as your target computer?
What device is your dhcp server? (mfg and model)

@Rayco Thanks for letting us know. Though I guess we have updated this long ago. See this commit from 2018: https://github.com/FOGProject/fogproject/commit/b629d5ef15ae52f680fb5c7b99c53ee1da91aa5a#diff-6c19cefd5d36153992eb2ff3ad4873a91680a65ef783d8aa86751fea6f90ef29 (We have changed the URL to standards-oui.ieee.org despite Tom’s comment in that commit.)

I never had problems with mac list update, but in my last update FOG cannot open http://standards.ieee.org/regauth/oui/oui.txt because isen’t a valid link now.

You seem to be mixing up a few things here. First we need to know which version exactly you use and if you’ve manually modified the code already. The very latest dev-branch code is already using the URL you ask about. And this is the same if you’d use latest alpha from working-1.6 branch.

@george1421 I found a device that was running a second DHCP … thanks for your help, the capture and deployment works now

@zaboxmaster said in USB to ethernet adapter:

I know this has been covered multiple times, but I have tried various methods, from the API post-deployment to remove the host to the I.M.I option or the I.M.C option. I cannot seem to get it right.

I am afraid we can’t help you without more details. Please start by telling us the FOG version you use. Then let us know in more detail what exactly you’ve tried and what didn’t work (error messages, pictures, …).

There has been discussion about using a different identifier (other than MAC address) which would help in your case. But there is some major work to be done and no one seems to find the time to do it: https://github.com/FOGProject/fogproject/issues/198

@sebastian-roth when George says this

mkdir -p /opt/fog/secureboot/hwkeys
cd /opt/fog/secureboot/

sudo efi-readvar -v PK -o /opt/fog/secureboot/hwkeys/hw_PK.esl
sudo efi-readvar -v KEK -o /opt/fog/secureboot/hwkeys/hw_KEK.esl
sudo efi-readvar -v db -o /opt/fog/secureboot/hwkeys/hw_db.esl
sudo efi-readvar -v dbx -o /opt/fog/secureboot/hwkeys/hw_dbx.esl
sudo chmod 666 /opt/fog/secureboot/hwkeys/*

He says he got the certs above on a debian instance running on a hardware pc,

What about if this a Ubuntu vm?

@chaonatic said in Lenovo x1 Carbon Gen 7, 8 & 9 USB NIC Issues:

Okay, I changed the boot file name and it did do the 10 second delay, but it’s still not PXE booting off of a USB-C NIC or the dock. Any other ideas I could try?

OK then I may ask you to hit the s key on your keyboard when asked to do so. Wait for another 30 seconds and then key in the following commands, take a picture and post here:

ifstat dhcp net0

@inger Well we really need to isolate just the fog server and target computer on the same network switch. Right now we don’t know where the problem is. It sounds like a network issue. I assume both the fog server and target computer nics are in working order, so we need to look at what is in between. So my recommendation is to start small and see if it works. If yes then start expanding the scope of devices.

At this point I don’t think its the fog server at fault, but something in the infrastructure. I’m not trying to point blame some place other than fog, it just seems like an intermittent network issue.

@dawnofsoap Thanks for bringing this up again. I should really push out a new release when I find the time over X-mas.

@cul3r0 said in Fog Server CA Download:

How do you recompile your own client binaries? Is there documentation on that?

You can find information on all the tools and stuff you need in our github project readme though it’s kind of dated (older versions).

I have been quiet because I am looking into re-designing the whole thing to make it a lot easier. Please be patient a little longer.

I’m managed to resolve this.

It was the “Hide Menu” option in fog config.

I don’t seem to be able to interrupt when using uefi.

651651615.JPG

@ombreit I think one of use is confused. I will raise my hand here.

The normal process is to:

Create an image definition in the FOG Web UI. PXE boot a source computer and register the computer with FOG. The source computer will be used as your golden or master image. You will then in the web ui connect the new computer with the imaged definition. In the web ui you will then schedule a capture task. You will pxe boot the target computer and capture or upload the golden image to the FOG server.

When you do step 5, in the picture you last show, the image size on client value will be set. The picture tells me you have not uploaded an image yet to the FOG server.

Also from the picture you gave us with lsblk the source computer does not have an image on the disk. So there is nothing to upload to the FOG server.

So I don’t understand where is your golden or master image coming from?

Thanks it saved my day.

@jonathan-cool Fun fact … : if i check this option, the speed deploy is “normal” BUT the post deploy result of a beautiful BSOD … “INACESSIBLE BOOT DEVICE”.

If i go back to the BIOS and uncheck this feature, the SYSPREP works …
So … slow speed or BSOD ? The choice is hard … !

@renanrenan Well now start the debug capture by hitting ENTER twice, then run the command fog to start off and go ahead confirming every step via ENTER.

@dejv said in cannot find disk on system (getHardDisk):

we still need to change to ahci?

Yes this is an Intel and Linux kernel developer issue. There is no resolution at this time.

@Pilar Well the issue this topic is about was solved. May I ask you to open a new topic for this new question. We try to keep things sorted so other people will find information and help more easily.

In that new topic post a picture of the settings you changed to move the image storage location as well as a picture of the error when capturing an image. We’ll tell you what’s missing.