I was actually looking at the official kernel list which has x64 and x 32 bits Archs.
Just had a look under the unofficial list and spotted the x86_64 and x86 Archs. Good to know they are there.

Again, thanks for your help.

Just tested the Tom Elliott 3.0.1 64bit image.
Yep works fine on the Dell 755’s now. I’ll test on the other models shortly and let you all know how it goes.

Cheers,

Please test 1808,

I believe I have narrowed and corrected for this issue.

Thank you all,

Niice!! It works! Thank you very much Tom!! Thank you for this tool!

For future people with these problems - this worked. [URL=‘http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/’][COLOR=#737373]http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/[/COLOR][/URL]

Thank you for the information. I did a 3rd option not realizing that you had responded. I re-copied the image from backup to the server, and it worked ok. I did not verify or check the image path prior to doing this. It could well be that the path got a bit mixed up. Regardless, the test worked.

Now onto doing the upgrade on the production server! I’ll keep your information for any other ‘uh oh’ situations I might have.
Thanks! 🙂

Ya no fog service was running on this new image I created.

SOLVED!

This is a O.S. issue.

Changing advanced plan settings for Energy Options, solved the problem.

If you need help, Convo me (not everybody all at once), but I can try to assist and direct where you may need it.

Issue was simple did not realize that under fog settings tftp server settings. Password had defaulted to series of letters and numbers.
Changed to my password and issue has been fixed. I will try reimaging the Quad cores now that i have downloaded this newer kernel to see if this helps.

Thanks much

Did you assign the image with a storage node or delete the node that that image was attached to originally?

Because you’re running SVN version 1801.

Based on what I’m reading on this, it sounds like the database didn’t get updated properly, maybe due to password not correct?

If you can stand to do so, try re-updating the database.

is this an OEM install, or have you wiped the disk clean and done a fresh install?

I tired upgrading to the new version of the fog. I am now at version 1.1.0. I am still having the same issue. Does any one have any suggestions?

[quote=“Koen, post: 29688, member: 4127”]Hi Tom

Sorry, I overlooked completely that option 67 had to get a different value, my fault.
May be the install script can emphasize that this has to be changed in case of an update?

All the best and thanks,

Koen[/quote]

It um… it does.

[code]
echo " DHCP will NOT be setup but you must setup your";
echo " current DHCP server to use FOG for PXE services.“;
echo ;
echo " On a Linux DHCP server you must set:”;
echo " next-server";
echo ;
echo " On a Windows DHCP server you must set:“;
echo " option 066 & 067”;
echo;
echo " Option 066 is the IP of the FOG Server: (e.g. ${ipaddres}“;
echo " Option 067 is the undionly.kpxe file: (e.g. undionly.kpxe)”;
[/code]

This is a blatant rip from the installfog.sh script that you run to install FOG, for some reason many members fail to read the instructions presented to them.

FIXED!

I truncated the entire tasks table, removed the bad member reference in groupMembers, and anything else related to this 'BAD HOST"…The Invalid OS ID is due to a small bug in r1799.

Issue resolved.

THANKS TOM!!!

before you do that just try change the value of FOG_UPLOADRESIZEPCT to 15
It is in the general settings.

I seem to remember we had the same problem, a couple of years ago.