Gotcha, okay. I’ll go and do MBR image building then, if that’s the case! Thanks Tom!

It worked!!!

Okay, according to those steps, I had deleted the MBR provided on the HD? What else did I exactly do? (Just in case I run into this, in the future lol)

Hello FOG peeps!

At the very last part of uploading an image to my NFS server, I’ve gotten everything straightened out, and everything is looking good. However, I get hung at the very last part of the initialization of uploading the image (as seen on the thread title).

Has anyone else come across this? And what error logs should I be looking for, in this instance?

Sorry for the late reply, got crazy busy on Friday. Anyway, I think it may be a problem when I try to pxe boot the machine, that’s when the error comes up and not much more information is provided :(.

[quote=“Jaymes Driver, post: 28658, member: 3582”]No, you would do it on the linux installation. What flavor of linux did you use to install FOG on? I will get you some commands to help you on your journey.[/quote]
I’m currently using Ubuntu 10.04

[quote=“Jaymes Driver, post: 28639, member: 3582”]This is stating that the command that is trying to perform is not recognized. To better help us understand, troubleshooting and finding the common cause would be preferable.

You can also try other undionly.kpxe and ipxe.kpxe files that Tom is working on to resolve some of the other issues.

Note the features in your current undionly file, when you pxe boot a client you should see something similar

[code]
iPXE 1.0.0+ – Open Source Network Boot Firmware – http://ipxe.org
Features: HTTP iSCSI DNS TFTP AoE VLAN bzImage COMBOOT ELF MBOOT PXE PXEXT[/code]

Please let me know what features are available and then compare it to the undionly.kpxe files that Tom is currently working with. We need to find the missing piece or the command that is making it fail.

Undi files can be found here: [url]https://mastacontrola.com/ipxe[/url][/quote]

Thanks very much for the reply! And forgive me, I’m a complete PxE noob. How can I “try” the other undionly.kpxe and ipxe.kpxe? Is this done through the fog interface?

I remember this happened to me a long time ago. My co-worker said that we should try putting the DHCP services on another NIC interface to see if that would help alleviate the issue. Unfortunately, I haven’t tried that yet (that was my previous job) but it may help you!

Anyone at all?

I have a feeling that’s what still blocking you then. At the moment, since options 66 and 67 aren’t configured to point back to your FOG server, it won’t relay any information to the client behind that DHCP server.

You may need to get permission or have the guys managing the DHCP server to place in the necessary info here:
[url]http://www.fogproject.org/wiki/index.php/Integrating_FOG_into_an_Existing_Network[/url]

What device/node is providing the DHCP services?