@Quazz You’re right! thank you… I forgot to turn off the old DHCP in the lab network with the issue. Problem solved (for me)

@george1421 I’m sorry, it really seemed (to me) that was the same issue (exactly same errors deploying an old image with a >1.3.x)

Now I can confirm that it was an issue copying the /images folder.

Thank you for your suggestion on zstd, I’ll change the compression method at the the next capture.

@sebastian-roth don’t worry, it’s an exception. I’m managing many fog servers and it’s great (and still my first choice).

@imagingmaster21 security chip disabled, usb nic allowed in host config, it’s atom: I don’t think it has virtualization support.

Unfortunately, I don’t have any device available to make further tests.

@sebastian-roth they’re using Windows Deployment Services

Hi.
It takes me some time to negotiate with management (and I suppose that in the meantime we should already solved the issue).
Unfortunately, they’re not allowing me to keep one device for all the time needed.
This morning they confirmed me that another path will be followed.

For your info (maybe it could be useful for others) I tried many efi binary, with those results (after updating to trunk):
i386-7156-efi dhcp failed
intel7156.efi dhcp failed
intel.efi dhcp failed
ipxe7156.efi stops after init.xz
ipxe.efi stops after init.xz
realtek.efi dhcp failed
snp.efi stops after init.xz
snponly7156.efi stops after init.xz

ipxe.efi is the only one that, before updating to trunk, allowed me to access the “iPXE prompt” (ipxe7156.efi didn’t)

@george1421 I tried with dev-branch:
Running Version 1.5.0-RC-9
SVN Revision: 6080
ipxe 9720f (or 7156, with ipxe7156.efi) it gets stuck after
“init.xz… ok”

after switching to working I’ve:
Running Version 65
SVN Revision: 6079
ipxe version now is 1b67a, but it still get stuck after init.xz.
“Features” available are not the same as the 356f version. the new ipxe lacks FTP and NFS (TFTP is still there, and bzimage/init.xz are read, so I don’t think it’s an issue).

I tried to update kernel, but I still have “Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 707, Message: ftp_put(): Could not create file., Host: 192.168.168.91, Username: fog”

I’m installing a new Ubuntu server. In the meantime, any suggestion to troubleshoot this one will be appreciated.

Hi @george1421 ,
first of all, thank you!
My fog server is a virtual machine, so upgrading to last trunk is not an issue for me. I could rollback in seconds.
I’m git-cloning the dev-branch and I’ll update you soon. then I can switch to working (I’ll only need to “git checkout working” or there’s something else I should take care of?)

Hi, I’m trying to capture a new Image, I read many topics on this subject, but I cannot find a solution.
Environment:
FOG Server:
OS = Ubunu 14.4.5 LTS (patched)
FOG Version = 1.4.4
bzImage Version: 4.11.0
bzImage32 Version: 4.11.0

PC is a Lenovo MIIX 320 (2in1 tablet/notebook). It doesn’t support legacy mode. I disabled secure boot.
USB-C Ethernet adapter
boot image: ipxe.efi
enabled “host kernel parameter”: has_usb_nic=1
EFI exit type is “refind EFI”

Issue:
Fog boot menu is loaded correctly, but when I choose any option, it reboots. I manually registered Host and planned a capture task. Now I’m stuck here:

troubleshoot steps already tried:
Change boot image: with all others *.efi images I’ve a “PXE Boot failed” error
Update Fog to Trunk (done yesterday, it was a 1.5 RC release, i did not take note of svn version): with some images I’ve a “dhcp failed” error, with others it stops after loading init.xz

I read somewhere (in this forum) about modified/patched kernels for UEFI, but I didn’t find info on how to obtain it.

I tried to update kernel from fog configuation - kernel update to Kernel - 4.13.4 TomElliott, but I’ve a “Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 707, Message: ftp_put(): Could not create file., Host: 192.168.168.91, Username: fog”. It pretty weird (for me) that it doesn’t say what’s the filename i is not able to update, but I double checked FTP credentials and it should be ok.

Last note: with non-pxe images on other hosts, Fog server works fine. I did no take care of the “legacy/UEFI coexistance” problem at this time, to simplify troubleshooting, I’m working like if I’m goin to have only uefi hosts in the future.

should i contact ipxe team (another issue is that from USB of this device it’s not possible to boot anything that’s not WinPE) or could some of you help me? thank you!

PS: this afternoon I’m going to install a new test server from scratch with newest Ubuntu and I’ll try to update kernel on that one. I’ll keep this post updated.

@george1421 I’m sorry, it really seemed (to me) that was the same issue (exactly same errors deploying an old image with a >1.3.x)

Now I can confirm that it was an issue copying the /images folder.

Thank you for your suggestion on zstd, I’ll change the compression method at the the next capture.

@tom-elliott wait, don’t waste your time with my previous post. It seems that something gone wrong during /images folder copy. I’m checking it. sorry.

@tom-elliott I know that this topic is quite old, but I’ve the same issue on a freshly installed 1.4.4

Images has been captured with 1.2.0 (installed on an ubuntu 12.04)
1.4.4 has been installed on a new ubuntu 16.04 and /images folder copied from the old server to the new one

workaround proposed by @reprised doesn’t work for me (I don’t have rec.img.00 and sys.img.000)

should I deploy from old server and recapture every image or there’s another solution?

thank you!

@Quazz You’re right! thank you… I forgot to turn off the old DHCP in the lab network with the issue. Problem solved (for me)