I am having a similar issue but I know it has to do with the BIOS. Although there has been some weird anomalies that have been happening. For some reason the GRUB boot isn’t an option and I’m stuck in a boot loop with SANBOOT and Exit. How can I get the GRUB boot back?

Thank you for that link Wayne. After looking through it I found that my problem was in the .fogsettings file. That password did not match any passwords that I had set. Once I changed the password it took my test image without issue. I did have one question though, when I looked at the vsftpd.conf file I noticed that I didn’t have the seccomp_sandbox. I added it but I’m curious, what exactly does that command/function do?

Thanks again everyone!

Hello everybody,

I’m having an issue here with my FOG server and I have been checking the forums for people experiencing similar issues. I have checked all passwords, both GUI and server side as directed on previous posts and still having the issue. I checked the Storage management password, TFTP password, Storage FTP password and still no luck. Every time I uploaded an image it would state, “task complete” and after about 5-10 seconds it would display Error: ftp_login() failed and it keeps repeating itself. Not sure what is wrong exactly but there is one thing I did notice. Under my define (‘DATABASE_PASSWORD’) server side, it remains blank but I can still access the GUI without issue but once I input a password (server side) and try loading the GUI I get an error saying “Unable to connect to database” and once I delete the password I am able to log in. I feel this may be causing the issue because once I add a password the current system that was being uploaded than goes from the error to a repeating " *." What am I missing? Currently running it on Ubuntu Server with FOG 1.0.

Thank you

You rock Tom!!! That did the trick! You’re right, not so pretty but as long as it works I’m just fine with it.

UPDATE:

Ran into an issue when trying to perform a full host registration.

New error:
Loglevel=4: command not found
Could not boot: Exec format error ([url]http://ipxe.org/2e022001[/url])
Could not boot: Exec format error ([url]http://ipxe.org/2e022001[/url])
PXE-M0F: Exiting HP PXE ROM.

Thank you for your response Tom. I tried every possible pxe file and with .kkpxe I get an error that states,

“Could not configure console: Input/output error ([url]http://ipxe.org/1d8c2139[/url])
Could not boot : Input/output error ([url]http://ipxe.org/1d8c2139[/url])
Could not boot : Input/output error ([url]http://ipxe.org/1d8c2139[/url])
PXE-M0F: Exiting HP PXE ROM.”

Hey everybody,

I have been racking my brain on this one. So to start off let me give you some background information. I am currently working on getting a FOG server going for our production plant’s machines. Those machines in production are HP DX5150 with AMD Athlon 64 processors. Currently I have two separate FOG servers running Ubuntu Server, one based off 14.04 and the other is 12.04 but both with FOG 1.2.0. Both servers are on our UCS system and are accessible through vSphere Client

Now here’s the kicker, I have DHCP setup correctly with 066 point to FOG and 067 to undionly.kpxe. I am doing some tests with three separate machines, one is a HP Elitebook Folio 9470 with an Intel i5, the HP DX5150 as mentioned earlier, and a HP Z220 Workstation with a Xeon. So far with the undionly.kpxe I am able to fully register both the Elitebook and Z220 without issue, however, the HP DX5150, the one that matters the most, will not boot to the FOG menu. So since the other two machines were able to fully access the menu that rules out the DHCP being an issue. I have tried every possible .pxe and all errored out. With undionly.kpxe it goes through an initializes the iPXE (1.0.0+) devices and then immediatly fails with a message that reads “Press a key to reboot”. I have searched and searched for a solution but everything is circling back to the same issue. I have updated the BIOS to the latest (7050) and still having issues. Also tried kernal 3.14.2 and 3.6.9 just for the hell of it and still the same issue. I also checked the boot settings and tried SANBOOT, GRUB, and EXIT all resulting the same.

What am I missing? Is it not possible for this machine to reach FOG due to hardware restrictions being such an old machine? Should I try reverting to FOG 0.32?

Thanks again for any help