Sorry for the late response on this guys.
The issue with this turned out to be with the OEM recovery partition that came with our dell machines. For whatever reason fog didn’t like it. Removing this partition fixed the issue and we now have the new fog server, and all the new hardware synchronizing and imaging correctly.
Thank you guys again for all your assistance in this thread (and the others). This forum has been extremely helpful
Moving the host means physically moving it and plugging it into the switch that is managed by the other storage node. Both storage nodes are acting as dhcp servers and assigning ips, but they are connected to separate switches. I added a diagram that may help
SERVER
FOG Version: 1.4.3
OS: Ubuntu 16.04 Server LTS
CLIENT
Service Version:
OS: Windows 10
DESCRIPTION
My current setup is the following:
The first storage node works perfectly and images it’s hosts as expected, but hosts on the second storage node cannot get past the iPxe boot step. They fail with a “Connection timed out, Chainloading failed”
I have spent quite a bit of time trying to figure out what the difference is between these two nodes and I am at a bit of a loss. The default.ipxe files are the same between the two, as is /etc/network/interfaces
I also compared the the contents of /etc/dhcp/dhcpd.conf and the contents of /etc/default/isc-dhcp-server. No issues here either. Also, I moved one of the hosts from node 2 and connected it to node 1. The host no longer had any issues so this seems to be a problem with the storage node and not the clients.
I have attached two images, one is the error from a host on node 2, and the other is from a host on the working node.
Any ideas what I could be missing here?
Thanks @george1421
I went ahead and moved the php — but I am now getting http 500. I rebooted the fog server to see if that would resolve it but it doesn’t look like it did
SERVER
FOG Version: 1.4.3
OS: Ubuntu 16.04 Server LTS
CLIENT
Service Version:
OS: Windows 10
I have a new .php module I want to install — I have put it next to the others in packages/web/service, but I don’t want to re-install fog in order to load this. Is there a better way to install this?
Sorry for the late response on this guys.
The issue with this turned out to be with the OEM recovery partition that came with our dell machines. For whatever reason fog didn’t like it. Removing this partition fixed the issue and we now have the new fog server, and all the new hardware synchronizing and imaging correctly.
Thank you guys again for all your assistance in this thread (and the others). This forum has been extremely helpful
@george1421 Awesome, thanks again for all of the help with this.
Our 7040’s are set up with SATA drives
I am going to try a manual install like you suggested and see what happens — but while I do that I do have a few updates
All of the hosts are Dell Optiplex 7040’s, and I was able to verify that the BIOS settings are the same.
Some details of what I have configured in the BIOS:
Also, I tried testing out the different exit options, and I got different behavior when selecting GRUB - ‘First Found Windows’
With this option, I get the following message: BOOTMGR image is corrupt. The system cannot boot.
The original host from the capture boots just fine, so it seems that maybe the image is getting corrupt somewhere in the capture and deploy process??
I will follow up again once I test a fresh install of windows 10 and see if the FOG PXE Boot works afterwards.
@Sebastian-Roth Alrighty so switching it from SANBOOT exit to GRUB allowed the original host from the capture operation to boot in correctly.
However, now when I try to deploy and boot into one of the other hosts, the process gets stuck with only the following three lines visible
Launching GRUB…
begin PXE scan…
Starting cmain()…
I double checked the bios on these hosts as well and everything seems to match up. Any ideas?
@Sebastian-Roth. I tried a deploy as well, and the machine I deployed to is experiencing the same issue it seems.
After completing an upload task on a host with windows 10, the machine becomes unbootable via fog. The fog system attempts to boot from hard disk but ends up stalling on a blank screen with a single blinking line.
I verified that the image / hard drive is fine by skipping the network boot and manually booting into the hard drive. So it seems like something is wrong on the fog end.
I was wondering if you guys had any ideas?