@educapole said in FOG 1.3RC13 TFTP error:

@Tom-Elliott Indeed, i’ve found a second DHCP server on my network. An user has plug a damn wifi acces point…

Bingo!! and those dang wifi access points with built in dhcp will point to them selves as the next hop server so the clients will try to download the boot image from them.

Good find.

This has been added to the wiki here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP#Please_enter_tftp_server:

@jmer129 That’s exactly what this file is used for. It maintains which partitions should be “fixed” or set as it was when the image was originally captured.

@dureal99d Your welcome. I’m glad in the end it was just a simple reboot that finally resolved the issue.

We had a hour or so chat session to work through this issue pulling apart the dhcp/pxe booting process frame by frame.

@TomBagley Thanks for reporting back! Marking this solved then.

My initial reaction is that you don’t have the sata driver for the P 650 G1 in your reference image.

Second reaction is what type of disk is in the 650 G1 (is it a NVMe type disk)? If so you will need to include the OS kbs that add support to NVMe disks. This is outside of what hardware drivers are needed for that model.

@Obsidian reported that replication worked fine after he setup his remote servers as Storage Nodes, as recommended.

Also, this topic has gone off topic, and has been forked to here:
https://forums.fogproject.org/topic/8747/when-restoring-image-disk-not-found

@Wayne-Workman He already did, it’s how I know it was already pushed and is working.

@george1421 ,
Hi,
with Intel I5/I7 processor the system start correct,
j1900 e3826 reboot (it’s not a fog problem but ACHI driver installed ).

Hye,

I 've update to rc14 and now it’s working.

Thanks

In addition to below, on your FOG server please key in showmount -e 127.0.0.1 that will show what is exported (shared via nfs) on your FOG server.

@smazzola said in I am trying to image a lab of Dell Precision 1700's.:

@sudburr

I created the image in UEFI mode. I had to turn on the Legacy Roms in order to get the device to pxe. However, I never took the device out of UEFI mode. I used the same settings on the machine I brought the image down to.

But, the image was captured in UEFI mode. This hasn’t changed. The destination computers must be configured in exactly the way the source computer was configured - before you changed things around - in order for the image to boot as expected on the destination computers.

Please read through my previous post.

@TThax You don’t need to actually download the client. The latest kernel, init, and client gets downloaded automatically when you run the fog installer. You just need to update to the latest FOG release candidate, run that installer, and you should be good to go.

@Sebastian-Roth I agree, after looking at a dhcp booting process all weekend I can read the pcap like code from the matrix.

The requesting system is in BIOS mode so undionly is the proper boot kernel for it. I see the target requested the file size for undionly.0 from the tftp server at 192.168.1.133 with no second response from the fog server or no request for undionly.0 to be downloaded from the tftp server. This tells me the tftp server responded with “file not found” for undionly.0.

Well then… those things happen. Marking it solved. Feel free to ask more questions if it starts happening again.

@Sebastian-Roth I have a feeling the “looping” without reboot actually “was looping with reboot” it was just a matter of “timing” between when it restarted due to failure and starting gathering the data itself.

This particularly so considering nothing in the init’s changed in the time the issue occurred and when the updates happened.

Thank you horse’s mouth!

So what should you do first. I assume today you have the proper line in your current PXE boot menu to forward the client to the FOG server, Right??

Take a test computer and collect its mac address, then get with your networking or admin group and have them insert the line from your current pxe menu into a text file and title that file the mac address of your target computer. I think you create the file name without any punctuation. So the file name should be like: 0018DC234567 Then pxe boot the target computer and see what happens.

Actually read over this page it does a lot better explaining of syslinux pxe booting than I can: http://www.syslinux.org/wiki/index.php?title=PXELINUX Plus I had the search order backwards (go figure)

Everything here works now though - including EXIT where I need it. Thanks again.

-Dustin

@Tom-Elliott from the logs: 10/7/2016 10:32 AM PowerManagement On demand shutdown requested. An on-demand shutdown is always queued and not being cleared. We need a clear on-demand tasks button.