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”.

Check the partitions on the drive. when you create a drive in virtual box I don’t know that it formats it in any way. You may need to format the drive to a valid type such as ntfs and then try to deploy again.

Usually when you push an image to a client and the fog emu pops up but runs by so fast you can’t catch anything, that is because FOG didn’t find a valid drive or partition type to install the os to!

I made a tutorial on using FOG debug mode to create or delete partitions, I would try setting a partition type and pushing the image again. I know for a fact that Virtual imaging works, I can bot upload and deploy to my virtual machines, but I ALWAYS prepare a disk before I image it!!!

Is javascript enabled on your browser? Did you by chance change screens and received that message? All that means is it was unable to update the information. If you refreshed and still receive the message please let me know, but all seems to be working fine from my side.

I’m not aware of any changes, other than adding a schema change, so my guess is this could be the cause?

Upgrade to 1667 and let me know if you still have issues.

Thank you,

[quote=“Tom Elliott, post: 26911, member: 7271”]That is correct.

Sorry I didn’t get a chance to be of assistance, and I will have to create a WIKI to add these minor changes.

XZ requires a small portion of encryption.[/quote]

This is my procedure for changing that file.

cd /var/www/html/fog/services/ipxe xz --decompress init.xz mount init ./tmp -o loop -rw cd ./tmp/tmp touch resolv.conf echo “nameserver 8.8.8.8” > resolv.conf echo “nameserver 8.8.4.4” >> resolv.conf cd …/… umount ./tmp xz -z -9 -C crc32 init

I then told my test bench to reboot in debug mode through my Fog server. The machine shutdown windows and rebooted me to a Linux command prompt. Although the link for resolv.conf was in /etc, the file I created in /tmp didn’t exist. When I tried to ping google.com I got the response “ping: bad address ‘google.com’”. After I ran though stops 4 to 6 from above while in the debug console my “ping google.com” then ran successfully. Next I tried rebooting the debug console to see if the resolv.conf I created in the debug console was still there… no luck. 😞

-Craig

Is MySQL running? If no password is set my guess would be that MySQL failed to start for some reason.

My guess, as to the particular issue herein, is that php-mysql is not the correct file to be installed. Check the lib/ubuntu/config.sh file and change the references of php5-mysql to php-mysql

I don’t know if this will work then.