We continue to face hurdles, but 12.04 with FOG 0.32, grub (not grub2) seem to work with DL360e Gen8, although we now have to figure out how to avoid eth0 disappearing after cloning.

Did you install the DHCP form the install script? If so, rebuild your server NOT using fog as the DHCP server. I can only assume that some settings are clashing.

If you want to have FOG dole DHCP that is fine but you won’t need DHCP.

If you want to use DNASMASQ to leave your DHCP setup alone and pxe boot via proxy dhcp, don’t install the dhcp, the two will clash settings.

We would be willing to help you to troubleshoot your issues, but you need top choose a path and stick to it. I would start by commenting out the line
“pxe-service=X86PC, “Boot from network”, undionly” some networks don’t need to be told to boot, and some do.

Are you not able to edit your DHCP settings to include your FOG server and Boot file name?

Hi[URL=‘http://fogproject.org/forum/members/wolfbane8653.3362/’] Wolfbane8653[/URL][I], please disregard. i did a fresh installation in Ubuntu 14.04 and is now working perfectly. [/I]

Sorry, I missed your signature, but I just tried now but sadly I still have the issue. Thanks for your effort; however, I’m going to have to call it a night now.

Cheers.

PS - We didn’t get the issue with 0.32, but sadly it doesn’t support ext4.

I figured out what I was doing wrong. I had the wrong operating system set in the image management portion of the webpage.

Help?

i believe we have found a solution to this problem
[url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/[/url]

Tom’s original suggestion worked for me with my Z230, but I had to change a little typo I guess. I had to capitalize the “I” in bzimage for the destination as well as choose the 32 bit kernel suggested by Jaymes. The following worked for me. Sorry if this has already been resolved in another thread.

[CODE]sudo cp /tftpboot/fog/kernel/bzImage /tftpboot/fog/kernel/bzImage.orig
sudo wget --no-check-certificate -O /tftpboot/fog/kernel/bzImage https://mastacontrola.com/fogboot/kernel/bzImage32[/CODE]

Thanks Guys!

How do you enable legacy mode?

Did you set a password for MySQL on setup? If you did, change the database password setting to match what you set it to in /var/www/fog/commons/config.php

It was from Kernel in new FOG it’s solved this problem.
Thanks!

Glad to know it worked, all I can think is that something was left hanging around from the previous install.

Download the latest fog version from the svn and run the installer again. The installer script will detect your previous installation and upgrade the necessary files.

Thanks for the replies. I started over and re-installed everything. Seems to be working fine now.

fog has a git that is synchronized with the svn [url]https://github.com/mastacontrola/fogproject[/url]

That did the trick!

Thanks Jaymes!

Thank you everyone for your help!!!

[SIZE=3][FONT=Times New Roman][COLOR=#000000] Tom,[/COLOR][/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman][COLOR=#000000]I assume it was Multicast. I did it from Group Management - Basic Tasks - Deploy.[/COLOR][/FONT][/SIZE]

[SIZE=3][FONT=Times New Roman][COLOR=#000000]I did resolve it this morning by putting the computers to be imaged on the same gigabit switch as the ESXi server and its guest servers. I don’t have much control over the network configuration so why there was such a drastic difference when I had the computers to be imaged off another 100 MB switch further down the line is not much of a concern. Most of the time we get a batch of new computers in and image them before deploying them to other sites. The occasional reimage will be OK at the slower speed.[/COLOR][/FONT][/SIZE]

[SIZE=3][FONT=Times New Roman][COLOR=#000000]Love Fog, thanks for your work on it.[/COLOR][/FONT][/SIZE]

[SIZE=3][FONT=Times New Roman][COLOR=#000000]Jeff[/COLOR][/FONT][/SIZE]

[quote=“marten, post: 26948, member: 23678”]Okay it turns out it’s not the server nor my configuration.

but the laptops I used as clients.
They are old Fujitsu esprimo’s they might not be fully supported for image deployment.
How ever I did manage to upload 1 image.

And I deployed the image on a Acer Aspire 5610 which worked fine, even though the bios isn’t supported by fog.
It can obtain a deployed image but it does get errors when trying to upload one.[/quote]

Those BIOS errors don’t mean diddly. FOG has the opportunity to use information from the BIOS for HOST Management and that is about it, that is not to say that there have not been times when a BIOS update has broken FOG or pxe booting capabilities…

Is there some kind of a watchdog setting on these machines? I had some Toshibas that gave me hell when imaging. I was in the similar boat as you my machine kept powering itself off and it turned out to be a BIOS Setting. So look for anything that would shut the machine off due to “inactivity”.