Awesome, glad you got it working!

I’ve never personally had any luck using the NTFS Resizable with my image but I’m glad it worked for you!

I agree with Tom. You need to expand the init.gz and mount it so you can look into the fog.clamav script and see if you can edit it to skip over non-NTFS partitions instead of throwing an error.

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

Would you like to join us @ [url]http://fogproject.org/forum/threads/pxe-booting-a-dell-latitude-10-tablet-problem.5558/[/url]

ProxyDHCP and dhcp-relay for your router if you have separate subsets that need dhcp services. We have a central fiber switch that routes for our subnets and two dhcp-relay entries in for each vlan interface, one for standard dhcp services and one to forward dhcp broadcasts to the fog server.

Yes, our storage node is set to allow 15 clients as well as the other two places specified, but it still doesn’t work in our setup. It’s not a huge deal for us though, as our images are fairly small and everything is gig-e.

I noticed on about 5 of the last 15 computers I imaged, the time/date were incorrect. Verify the time is matched with the server and try joining again

I know this worked for me:

[IMG]http://i.imgur.com/B2jfsfJ.png[/IMG]

Sorry all,

I forgot to read that you guys were having the issue with FOG 0.33b. I posted all of this information on FOG 0.33 Bugs forum as well.

I don’t know of a method of confirming the actual svn revision. Maybe somebody else can be of more help in this regard.

[quote=“jdd49, post: 1803, member: 623”]Navigate to /tftpboot/pxelinux.cfg
Delete the file with the name as the mac address of your host[/quote]

tis worked fo me!

fogclient.localdomain is just the name the PXE file system is using. The Reason your fqdn isn’t working is probably due to DNSMASQing is not configured for domain name distribution. I could be wrong, but I think you have to use IP for the imaging process. Using hostname is easier to remember, but it also requires DNS lookups to be accurate and updated quite regularly. Remember that the loading of FOG during pxe boot is a very minimal OS and it doesn’t mean that all components work as you expect. I’d stick with setting the IP for your <yourfogserver> section.

I know this thread is a little stale by now but for the sake of posterity, I was having the same issue after rebooting my FOG server (running Ubuntu 12.04 64-bit). I found that issuing:
[CODE]sudo service tftpd-hpa stop
sudo service tftpd-hpa start[/CODE]
brought everything back to life

I also found that adding
[CODE]/bin/sleep 30 && /etc/init.d/tftpd-hpa restart[/CODE]
to rc.local didn’t help (in fact, I already had that in my rc.local), however
[CODE]/bin/sleep 30 && /etc/init.d/tftpd-hpa stop
/bin/sleep 30 && /etc/init.d/tftpd-hpa start[/CODE]
did help. Don’t know why restart didn’t (maybe my server is too quick and needs some more time before it tries to restart the service - [FONT=Consolas]/bin/sleep 60[/FONT] perhaps?)

For the record (and to help anyone who doesn’t really understand Linux very well), my /etc/rc.local file contents are as follows:
[CODE]#!/bin/sh -e

rc.local This script is executed at the end of each multiuser runlevel. Make sure that the script will “exit 0” on success or any other value on error. In order to enable or disable this script just change the execution bits. By default this script does nothing.

/bin/sleep 30 && /etc/init.d/tftpd-hpa stop
/bin/sleep 30 && /etc/init.d/tftpd-hpa start

exit 0[/CODE]

I guess that would do it as well. Awesome man. Maybe try posting your findings into the tutorial section so others can troubleshoot their issues a little quicker as I’m sure this isn’t the only one to have happened.

The systems would come back with an error. Unfortunately I didn’t document what it was…I assumed the problem was that I removed the original images. The server only has 1tb of space and I still have several computers I want to have imaged before the inevitable happens.

check the sata mode in the bios - try using ata /ahci - swapping them around maybe the machine that was imaged from had a different setting to what you are imaging too in conjuntion with the chainloading link as above.

if it’s on a separate box - make sure mysqld listens on a physical interface rather than 127.0.0.1

Never mind! I figured it out finally!

I was changing the global scope options on my DHCP server but each individual scope still have option 67 going to our old imaging server’s PXE boot file.