Posts made by fre2709

Hi Jaymes,

have checked the manufacturers web-site and the BIOS on the machines is already the latest. As far as the switches go though, because I am having to remove the HDD to image it in another chassis, I have been doing them one at a time. All on the same switch, same port. I still don’t understand why every other unit could be imaged on this LAN cable except the T5760 Acer.

Also it doesn’t explain why one out the twenty works fine and can be imaged in its own chassis, the other nineteen won’t…

Kind Regards,

Frank

Its looking like a possibility that there is some issue with the Acers getting an IP at iPXE handover.

[COLOR=#ff0000]Tom Elliott said: System will only reboot, if it can’t pick up DHCP. 0x040ee119 or something like that.[/COLOR]

It is strange though that I have one unit which PXE’s fine and 19 that will not. They are all on the same BIOS revision, same version of PXE Rom. Only thing I noticed during boot was all the others come up with what appears to be a valid GUID during DHCP. The one that works shows a GUID of all FF’s.

Could this be the reason? Can’t really see how, but it is the only difference between them.

Hi Robin,

the issue I have is with Acers. However, EUFI boot is disabled and has always been disabled because we were working with an older version of FOG. AHCI mode has been set to IDE (equivalent to LEGACY in other BIOS’s). Something in iPXE is not compatible with these laptops for some reason…

Kind Regards,

Frank

Thx Ch3i,

i am not completely surprised HP do something non-standard. We have some Elite series ones which luckily work OK.

This is something different. These laptops used to work with the old FOG 0.29 server fine. It is definitely an issue with the way FOG now uses iPXE. Hopefully Tom et al, will come up with a solution. If secure boot is starting to be an issue also, then something will need to be done about fixing FOG to work with it. More and more newer PC’s and laptops are using this EUFI boot which appears to be hit and miss whether FOG will work or not.

Newer BIOS’s will not even let you “Legacy” boot now which was a workaround to getting an image put onto a computer with FOG.

Hi All,

Have trunked the TFTP files and copied them as suggested by Tom and Robin. This has not changed the situation though. These darn Acer laptops will still not iPXE correctly…

Any further ideas about this issue? Having to remove the hard drives and image them in a chassis that does iPXE.

Hi All,

Thx for the SVN info Robin. So the only way to try out the new trunk KPXE files is to upgrade our fog server?

Tom, I tried ipxe.pxe and seem to be still getting the "Error {some sort of hex error code} {some further text I cannot catch}, so I swapped back to undionly.kpxe, so is trunk the only way to go now?..

Thanks Tom,

I’ll try ipxe.pxe as a bootfile for DHCP.

I am a bit of a noob with Linux. How do obtain and use the files in trunk.

Hi Tom,

No, as I said it only seems to be this particular model of laptop. I took the hard drive out of it, installed in in a different model ACER (P255M) and downloaded an image to it (turned 255 off after imaging complete). I swapped it back to its original chassis booted it and am in the process of updating it ready to capture. Which I am unable to do at the moment and will have to juggle HDD’s to get it uploaded.

Coincidentally we had the issue with infinity loop on everything until we turned on PORTFAST.

The Atheros bootrom seems to pick up an IP because some addresses appear on the screen (again too quick to catch) until it hands over to iPXE. The error message seems a lot faster to disappear when using undionly.kpxe because I only managed to catch it when i switched to undionly.kkpxe so was it because undionly.kkpxe doesn’t exist? Did I use the wrong bootfile name?

Hi All,

I’ve been looking around the forum for answers to this but none that I found fix the problem for me.

It is strange, other hosts work fine. Just seems to be this particular model of laptop. I have tried using undionly.kkpxe as the bootloader in DHCP but get same issue. A long row of dots accumulate after the “Configuring (net0 {MAC Address})” then an error flashes on the screen too quick to read and the laptop reboots. The error message tags itself to the end of the dots. It seems to be "Error {some sort of hex error code} {some further text I cannot catch}. I have tried many times to pause the screen just as it appears but have been unsuccessful. I could try videoing it if you think it may be important to know what the message says.

Originally I thought it may be a dodgy kernel as our old fog server 0.29 used to image these with pxelinux.0 fine. But I downloaded an old “kitchensink” kernel and pointed the host to it but nothing changed. It isn’t getting as far as downloading the kernel files.

I am currently using FOG 1.2.0 on Ubuntu 12.0.4 LTS.

Any ideas or did I miss a post which sorted this?

Hi DoubleD,

I don’t know if there is a broken distro of Apache out there. When you run installfog.sh it runs apt-get to fetche all the bits it needs. It seems to be downloading an apache which does not have the mods enabled or are incomplete for some reason.

Maybe it will get fixed at some point, but at least we have a workaround…

I can confirm that everything appears normal apart from the “in front of me” count, as per Michael Shocklee’s post…

Hi Tom,

Just in case I was going mad, I watched the deployment of another room to see if had been a one-off. But no, exactly as I described in my previous post.

After all queued hosts reached the 9 minute marker the last one, which said “13 PCs in front of me” started counting down. As soon as I noticed this I checked all the others and they were doing the same until all hosts said “0 PCs in front of me”. The time in queue continued to count up by the minute.

When the first batch of 10 hosts started to finish, the next in line started to deploy until I was left with three still queued. They all still said “0 PCs in front of me” and the time in queue continued to count up. I took pictures of the three host screens but couldn’t attach them to the post - kept getting errors even as a ZIP.

Are there any logs or other files you need to see from my FOG server to diagnose the problem? However, as Michael Shocklee is getting the same it must be a coding error in version 1.1.0 to 1.2.0…

Sorry Tom,

no, the information (counter) remained at zero after the initial 10 minutes of queuing. As the deploying ones finished and cleared from the task list the next one in line started deployment until all 24 were deployed.

It’s almost as if the deployment engine either at the host or server end lost communication after 10 minutes then without any fresh information to go on, used zero as a “best guess”.

I know that’s not very technical, but from an end-users perspective, that what seemed to happen…

Hi Tom,

No they just continued to wait and deploy as normal. Originally I thought someone may have forced the deployment of the remaining hosts on the task list, but no.

Strange…

Hi there,

I had a similar issue and after searching around for an answer, I found the below on an Ubuntu Server forum.

I tried: sudo apt-get install libapache2-mod-php5

It installed a module (libphp5.so has appeared) uninstalled another (libphp5filter.so seems to have gone). Re-installed FOG 1.2.0 and hey presto “it works”. Updated the schema and I am back in and working.

Hi All,

I don’t know if this is a bug or normal activity - doesn’t seem “normal”.

Today I deployed a room of 24 PC’s and PXE booted all of them. FOG started deploying the first ten on its list. The remaining fourteen displayed a message like “Waiting for a slot: there are 0 to 13 PC’s in front of me” depending on where it was in the queue.

After these fourteen had been in the queue for about nine minutes, the position in the queue for all the remaining PC’s slowly changed so that by ten minutes in the queue they all reported “0 PC’s in front of me”.

I know you guys are extremely busy fixing more important issues than this. As it doesn’t stop FOG working, maybe it is a fix to be put on the wish list for the next version?

TIA

Hi Kronkas,

what version of FOG did you upgrade from?
where there any error messages within the fog installer script?
sounds like the installer didnt run correctly if the file doesn’t exist.

the actual file you should edit is /var/www/fog/lib/fog/Config.class.php (it is case sensitive)

Sorry All,

forgot to mention my version of Ubuntu is 12.04LTS.

Having dug a little deeper, the /etc/apache2/mods-enabled/php5.load file points to /usr/lib/apache2/modules/libphp5.so" which isn’t there. The only file beginning with “l” is “libphp5filter.so”

As suggested on an Ubuntu server forum I tried: sudo apt-get install libapache2-mod-php5

It installed a module (libphp5.so has appeared) uninstalled another (libphp5filter.so seems to have gone). Re-installed FOG 1.2.0 and hey presto “it works”. Updated the schema and I am back in and working.

Did I see on the download page that there is a SVN 2094 for FOG 1.2.0 already. What does that fix?

Hi All,

Not sure where to post this as it is an Apache2 issue rather than FOG. But Apache was working until I tried to upgrade…

fog installer script all ran fine until the setting up of services. MySQL worked fine, but when it tried to start Apache it failed. Attempts to restart it “sudo service start apache2” quickly gives an error message relating to syntax in “/etc/apache2/apache2.conf line:210” There are a couple more errors following this but I suspect they are all related.

I have looked at line: 210 and it appears to be a line in the “Includes modules section” it reads…

Include mods-enabled/*.load

Being a relative Linux newbie, I’m unable to say if the line has a syntax error or not. I have seen some suggestions to “sudo apt-get purge apache2” and “sudo apt-get install apache2” which I tried. The package re-installed without error, but the service still will not start.

Please help, my FOG server is broken and I have much work to do…

Hi Junkhacker,

basic install 1.1.2 patched with SVN to 2052