SOLVED Kernel questions
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?
Sounds a bit like you have two DHCP servers answering clients’ discovery requests in your network. Sometimes they pick up IP and PXE information from FOG and sometimes they pick up whatever the other DHCP server provides (probably only IP without PXE info)??? Just a wild guess…
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.
Wayne Workman last edited by
Screen shots / photos would help out a lot in this particular instance.
Are the laptop’s HDDs blank? Just curious.
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.
Can you explain this? I see a contradiction in your statement. You can’t connect to the fog server at all, but you fixed this in the past with gparted correcting a disk partition assignment?
The first statement is a communication issue and the second is a hard disk partition correction.
Where precisely is this failing? Do you see the ipxe part of the boot load? Can you see the fog ipxe menu? Do you see any error messages?