Hi All, thank you very much for getting back to me.

This issue is now solved. Was a FOG install error. The DHCP was being very hit or miss. Rerunning the install and now the computers are Fogging.

So before we found that we would be able to get DHCP and deploy by FOG but the images would fail at deploy, this is where we found that using gparted before FOG was good.

There has been other times, where DHCP just wouldn’t work. It took a while to find the error, because some of the laptops would connect to FOG by DHCP and others that would not. With no changes except for gparted being run on the machines.

The HDD’s are not blank, they have Win7 on them, and everything is set to legacy.
Sometimes the iPXE would come up, and other times where PXE would just be ignored completely. This was trying 1 laptop at a time connected to FOG.

Hi All,

bit of a unknown question.
We have been using FOG for about 2 years now. We recently got some HP Probook 450 G3 laptops with Msata SSD drives.

We were using Ubuntu 10.04 LTS 32bit desktop version with FOG 0.39. But the laptops were getting stuck in a boot loop when trying to deploy an image. I tried quite a few of the kernels, and none would make a difference.

So we upgraded our FOG server to be Ubuntu 14.04.3 LTS 64bit desktop version and running the newest version of FOG 1.2.0.

The server is a bit slow, but it works for the laptops I test it with, except for the HP Probook 450 G3’s. Since we have done this, the HP ProBook 450 G3 no longer connects to FOG at all. We have seen this before with laptops, but once we run G-parted on them it fixes the problem. We have had no such luck with this model of laptop.

Can anyone point me in the direction of a solution, or suggest options I have to try to get these laptops to FOG?

Sorry, I had left out that part, its an isolated network, so the only machines on it are those waiting to receive the image, and the FOG server.
It is the same setup as our other FOG server, completely isolated.
We had tried it on a different network initially and found this problem, so we isolated that network but FOG didn’t like the switch, so we changed over to our switch which we know works.
Then came back to our Head Office and tested it again, and we had the same issues.

We do think it could be an issue with the network, but are not sure how to resolve this. The laptop has a Gigabit port, and its connecting to a Gigabit switch.
We are using a stock version of Ubuntu desktop 10.4.4, with a stock install of FOG. The only configuration I have made on the server was to set static IP for the lan connection.
Is there anyway to test it against the network? As proof of the network being the issue?

Hi,

we currently have 2 machines working as a FOG server. One machine works for multicast just fine.
The one we are currently having issues with is a Fujitsu A512 laptop with 8GB of RAM ([url]http://www.fujitsu.com/uk/products/computing/pc/notebooks/lifebook-a512/http://www.fujitsu.com/uk/products/computing/pc/notebooks/lifebook-a512/[/url]).
It is running Ubuntu desktop 10.4.4 and FOG 0.32
This FOG machine works fine for deploying an image to 1 or 2 machines, at most 3. But there seems to be an issue when you try to start imaging a new client, where it hangs at “Loading fog/kernel/bzimage…” and it will do this for quite a while. It can take any amount of time from 2 minutes to ten minutes until it progresses onto “Loading fog/images/init.gz…” and it will do this for quite a while too.

This is our second day testing this, the first time we had 9 identical computers, and the most we could get at once was 3. Today we are testing it with random computers. The outcome is the same, we can get 3 to work, and it was difficult to even get that. The only way it seems to work is if all 3 boot at the same time. With our other server, you can jump in another computer without any issue.
The furthest we have gotten is this screen (see photo 10) and if we are very lucky it might get to this screen (see photo 11). But at this screen it just hangs for quite a while, until the computers currently being imaged are done.

I have changed the kernels around from the default kernel, to 2.6.35.3 PS and other PS versions, and it is still the same issue.
I am positive that it is not the switch we are using, as I was able to deploy the image to 8 computers on Friday using our inhouse FOG server. I cant see any difference between the inhouse server and the laptop server except for the laptop hardware being the issue. But that is the only thing I can find to be the blame.

If anyone has any pointers on this that would be great. Or if anyone would have any ideas of other things we could try.

Greatly appreciated,

Vinnie

[url=“/_imported_xf_attachments/1/1013_photo (10).JPG?:”]photo (10).JPG[/url][url=“/_imported_xf_attachments/1/1014_photo (11).JPG?:”]photo (11).JPG[/url]

It is working now, and I have been told it is a cabling issue. I can’t see why, as the cable works fine, but I have been told to stop questioning it and just accept it will work where it is now and not where it used to be.

Thanks again for the help.

[SIZE=3][FONT=arial][COLOR=#222222]Hi Tom,
The tftpboot file is stored on the FOG server, the attached image is the folder structure. I am not sure if there should be the other tftpboot folder inside this folder? It is empty regardless. For the pxelinux.0 file, I can not open it to view it. Even using sudo it says it cannot be opened.

We have nothing running Samba unless Ubuntu 10.04 installs it as default. And we have nothing running VoIP.
We also do not have any other PXE servers running.
This is the shutdown log, all but Thursday were definitely done by me. But I had used the server on Friday and it worked.
$ last -x | grep shutdown | tail -n 10
shutdown system down 2.6.32-56-generi Tue Feb 25 10:57 - 10:59 (00:01)
shutdown system down 2.6.32-56-generi Tue Feb 25 10:35 - 10:36 (00:01)
shutdown system down 2.6.32-56-generi Thu Feb 20 16:22 - 16:24 (00:01)
shutdown system down 2.6.32-56-generi Wed Feb 19 12:07 - 12:09 (00:01)
shutdown system down 2.6.32-56-generi Wed Feb 19 11:36 - 11:37 (00:01)
shutdown system down 2.6.32-56-generi Wed Feb 19 11:28 - 11:29 (00:01)[/COLOR][/FONT][/SIZE]
The tftp service is running.
~$ service tftpd-hpa status
tftpd-hpa start/running, process 2571

I have just tried by changing the port we have been using for the last year, it now seems to work on a different port. I have no idea why. I literally just chanced my arm and moved it across one port. The port that FOG did not like still works perfectly fine, just not with FOG.

But to get to this stage I had removed FOG from the server and re-installed it. Using this code [FONT=monospace][COLOR=#000000] [/COLOR][/FONT][FONT=monospace][COLOR=#000000]sudo mv /opt/fog/.fogsettings /opt/fog/fogsettings-firstInstall [/COLOR][/FONT] did nothing.

Thank you so much for everyone giving me pointers and helping me to try figure this out, from doing so many installs of FOG I thought I had got it down as a skill, I think this shows it as a big no.

[url=“/_imported_xf_attachments/0/562_tftpboot folder.PNG?:”]tftpboot folder.PNG[/url]

Just about a week of FOG working and the issue happened again. I have no idea what is up with it. I am positive that nothing has changed on our network/firewall/hardware configuration. My only guess is it might be a computer in the office that was not powered on last week.

This is some of the strangest happenings. FOG has been used in this office for over a year at this point, and most the computers in the office have been around for that long or longer. I shall try another reinstall of FOG and see what happens.

It was really quite odd, it just stopped working out of the blue and came back out of the blue. Really confusing but I’m glad it had its holiday and everything is back working.

Hi Jaymes,

I have no idea what was the problem, but I was doing a clean install of Ubuntu 10.4.4 just to be starting on a fresh slate after going the dnsmasq route. After the clean install of both Ubuntu and FOG, it is now working perfectly. The only thing that had changed is that it is another clean install.

This is the 3rd clean install from disk in a week to try fix this problem. I have no idea why it is working now, as I followed the same instructions every time. The only difference now is eth1 is now running on an IP address of 192.168.1.133 instead of 192.168.1.138. But eth0 is still running on 10.10.10.1

I have gotten as far as the FOG splash screen, and am currently uploading an image as a test.

Thank you so much for your help

We can’t see how it would be a network problem, We have not changed any of our hardware or configuration. And FOG is isolated, I can get to the web management side of it via IP

But I will try the DNSmasq and see how that goes. I will also give a look into the settings to see they are configured as you have said.

I will report back if I get it to work