Posts made by variable205

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?

Hello!

Long time FOG veteran and just newly upgraded to the newest version 1.0.1.

My FOG setup consists of three connections:

10.10.240.10 that enables me to contact the web server from my computer.
192.168.2.1 Is the bread and butter interface that holds the DHCP server (192.168.2.5) that was builtin with fog
172.16.2.1 Is the separate connection I have that’s attached to a NAS drive for storing images (this works just fine)

The laptop I’m using to test with does manage to grab an IP address from the DHCP server, but once it goes to a couple of other steps, I’m given the iPXE error “Exec format error” and I haven’t a clue what that means.

Any ideas anyone?

I’ve had personal experience with this issue and I can confirm the fact that you HAVE to switch your HD mode from AHCI to IDE in order for your computer to boot properly

You Rock Tom! Keep it coming man! I can’t wait for the first stable release of 0.33!!

Hey Tom! Thanks for taking the passed torch of FOG! I love this system, and I’m glad its still being updated

Don’t get me wrong, I’m glad you got your FOG installation up and running, but it still urked me that the errors weren’t logged there. I wonder where the logs would be located…

Forgive me, but I’m not terribly familiar with TFTP, but let’s see if we can break it down at least!

First off, lets see if we can find a more detailed error than what you received from the client. According to my research the error logs are in the “[SIZE=11px][FONT=verdana][COLOR=#000000]/var/log/messages” directory. Can you recreate the problem so that you get the error message again? (in that way, the error will be logged again)[/COLOR][/FONT][/SIZE]

Hello!

With the existing menu options when you boot into PxE the third option is the “Full Inventory Registration” option (which you all already know).

However, I would like to request that the option would also find and store the wireless MAC address from wireless nodes like laptops and netbooks. Otherwise, I would either have to go into the FOG host options of a given host and either type in the wireless MAC manually, or click the checkmark. I have about 650 netbooks, and going through each would be incredibly time consuming.

From what I can see, the full inventory registration just stores the current MAC address that the node is using, which is always the LAN ethernet.

Thanks!

My my, that was incredibly easy. Sorry for bothering you guys, that was more of a “herp derp” moment of mine. Thanks!

Alright, seems to be simple enough, I’ll give it a go when I’m back in office! Thanks

Hello,

We’re currently doing a migration from XP to 7, and we currently have all of the clients on the Windows XP OS type and I would like to move them all to the Windows 7 OS type. Is there a quick fix for this? Or do I need to go to each host individually, one at a time and change them?

Thanks!