Thanks for the quick feedback guys. Sorry I’m so delayed in responding, I’d already returned my test VM’s to snapshots and just hadn’t been able to return to this until yesterday.
1.1 seems to have resolved the issue for me. The nodes now behave as expected with regard to the ‘master’ setting. I’m hoping that this is something that was fixed in 1.1 and I’m not just losing my mind…

One other slight problem I’m seeing now:

The disk information does not display for the SN. It does work correctly for the default member.
If i click just below the ‘Failed to connect to’ text, I’m brought to a hardware info page which does contain the file system information I’d expect to see on the chart.

I’ve changed the FOG_BOOT_EXIT_TYPE to GRUB and the problem was solved!
Thank you very much for the support.

Ok. Well, it’s summertime here (which is when I actually use FOG the most) so it might get moved to an end of summer - after imaging or a middle of winter project. Thanks for the info.

[quote=“Tom Elliott, post: 29976, member: 7271”]What is the OS of the image?

What is the type of the image (raw, single disk, multi-part?)

It looks like the mbr or gpt tables aren’t being written back. At least not properly.[/quote]

I may have found something that fixes this.

I did a deploy-debug on both PC’s.

Then at the debug prompt:
# fdisk /dev/sda and then “w” to write it out
# fog

Both PC’s seems to be loading. Though I don’t know if this is one-time or I will need to manually do this every time I want to load these machines. Any ideas?

(got this from: [url]http://fogproject.org/forum/threads/partition-table-error.1234/#post-10305[/url] )

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?