This isn’t a problem with the “sanitizing” of the fields, though I assure you they are sanitized.

I’m going to guess, the system that inserted, but with a hostID of 0 was also set to be imaged?

This was a known issue of 1.1.1, and I believe it was fixed in 1.1.2 but for sure was fixed in 1.2.0.

Hi Tom/Wolfbane

thanks for the info and for getting documentation updated which will no doubt help others doing this. In our case the networking team have confirmed that STP is enabled but that portfast is not. We’re looking to roll this out again in a couple weeks but for now have gone back to 0.32.

Our network team have advised tha as well as configuring portfast they will also configure BPDU Guard to avoid network loops which could bring network down as discussed in [URL=‘https://learningnetwork.cisco.com/thread/3160’]this cisco thread[/URL].

I’ll confirm once we have this up and running and include any other gotchas we encounter.

thanks again, Kiweegie

hanging on HP with Realtek card. I have copied the latest undionly.kpxe files into the tftpboot directory but still no joy with this card. Is there any fix for this?

You don’t by chance have GP set up to add this printer as well do you?

Try setting your menu timeout a little higher, i’m betting these machines or a network lagg are causing the timer to expire before you are shown the menu.

Are you using a custom kernel for FOG?

hi see my post
[url]http://fogproject.org/forum/threads/after-deploye-grub-fog-1-2-0.11873/[/url]

Thanks Jbob, here we go.

Thanks K0R, valid point who would have thought that an HP ProBook 4530s has got an ide hdd??? SORTED

Awesome - thanks for the quick response!

All good now.

1.3 didnt seem to work, same errors about nbp being too big.

so followed the chainloading instrcutions from,

[url]http://www.fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0[/url]

Error 0x040ee119 ([url]http://ipxe.org/040ee119[/url])
Waiting for link-up on net1…Down ([url]http://ipxe.org/38086101[/url])

so, that didnt work, so removed the symlink to pxelinux, back to undionly.kpxe and it’s suddenly started to work, have registered the host and am now deploying. fingers crossed…

Did a full reset of the network controller through the BIOS - now imaging 🙂
Thanks for the guidance it was a great help

Keep up the good work, super product 🆒

I know that I disappeared a bit with this issue, but as I wanted to make a reproducable version of this problem I created many virtual box instances to make a closer look on the problem. And now, for reason unknown, I cannot reproduce the issue. Hosts are created as I want them to be, etc. Really, really dont get the problem, what happened. If I again can reproduce the issue maybe I will be aware of the reasons.

What informations do you need?

We have Two raid in our server, 1 for Ubuntu and 1 for the images.

We just create a link between /images and our storage raid.

And it work really fine.

Can you attempt putting it into Bridged mode.

Host-only, as I understand it, makes the device as if it’s going through the host machine. This sound’s like it’d be a good thing, except the VM still has to process the information as if it is its own device. So, when you choose Host-Only, the device suddenly becomes processed by two CPU’s.

It’s just a theory and one that I think deserves a good ol’ college try!

Change out of host-only to Bridged NIC and maybe things will work better?

When I was changing the folder name it was giving me an error. The name was not getting change.

Yes, I have the fog client installed on both images I have. I have the correct server IP address and hostname changer is enabled. I’m not sure what the fog.log has in it. Tomorrow I’ll try to deploy an image to another machine and see what the fog.log file says about joining.

I’m confused.

Have you tried uploading an image?