Gentlemen we have lift OFFFFFFFFFF.
I have finally booted to my fog server successfully. In the end it was the line: dhcp-range=10.0.0.10,proxy which I had to change to the ip address of my server.

Soooooo to help others
here is a quick breakdown of my set up and by no means perfect but hey it works
Ububtu 1204 LTS
Fog 1.1.0
Cisco WAG120N switch with DHCP enabled to provide IP address in the same subnet as your server(just in case)
DNSMASQ installed and configured as per link (DNSMASQ doesn’t provided DHCP it inform the client’s computer where to find the fog server)
[url]http://fogproject.org/wiki/index.ph...with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

I had to change the following in the /etc/dnsmasq/ltsp.conf
dhcp-boot=undionly.kpxe,fog,IP.Add.of.yurserver
and
dhcp-range=IP.ADD.OF.yurserver,proxy

Thanks to LifeHacker, Jaymes and Tom Elliott

Do you see the iPXE setup screen appear? It should, since you were able to deploy an image earlier, but can you confirm that you see it saying something like (N.B. This is for a system without a task scheduled)
[CODE]
net0: 52:54:00:27:7a:dd using virtio-net on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 52:54:00:27:7a:dd)… ok
net0: 192.168.222.102/255.255.255.0 gw 192.168.222.1
Next server: 192.168.222.100
Filename: undionly.kpxe
tftp://192.168.222.100/undionly.kpxe… ok
PXE->EB: !PXE at 9C3B:06D0, entry point at 9C3B:030C
UNDI code segment 9C3B:076C, data segment 9CB2:2CD8 (624-638kB)
UNDI device is PCI 00:03.0, type DIX+802.3
624kB free base memory after PXE unload
iPXE initialising devices…ok

iPXE 1.0.0+ (8a380) – Open Source Network Boot Firmware – http://ipxe.org
Menures: NFS FTP HTTP HTTPS iSCSI DNS TFTP VLAN AoE bzImage ELF MBOOT PXE PXEXT
Configuring (net0 52:54:00:27:7a:dd)… ok
/default.ipxe… ok
http://192.168.222.100/fog/service/ipxe/boot.php… ok

http://192.168.222.100/fog/service/ipxe/bg.png… ok
[/CODE]
Depending on how much or little of this you see we might be able to narrow down where the problem is.

That was it! .mntcheck was missing from /images/dev. Thank you!

[quote=“cr31, post: 33511, member: 25150”]Was this a New HDD?
I came accross this when we purchased a pallet full of refurbished machines, and got the same message…because the HD wasn’t initialised.
I removed the drive, put it into an external caddy, used disk management to initialise the disk, put disk back into PC, re-tried with Fog, and it worked!
Alternatively you can use Diskpart or similar

i may be off the mark here, but just check[/quote]

it is definitely initialized - it’s currently got XP on it. Also, it imaged fine with the 0.32 fog server when I spun it back up. The issue is somewhere in the update, unfortunately 😕

I ran [FONT=Consolas]sudo service tftpd-hpa restart. Worked like a charm. Thanks a bunch everyone. That one sure had me going. [/FONT]

Just what I thought. Thank you and the rest of the forum staff for your awesome support!

Thanks for the information. I’ll check the settings in the BIOS and then test.

Okay, I’ll give that a try as a final attempt of using fog. I have a server ready to go with Server 2008r2 on it to get WDS setup since I’ve had nothing but problems with FOG/Linux since the day I started using it. All of everyone’s help is deeply appreciated.

Ok I was able to delete them when I use Google Chrome but not IE! I still have the issue that some status are Queued and some say N/A!

sorted it… user error… haha 🙂

Hi Sparky, Operating systems are now associated with images not hosts. If you look under images you should be able to see the OS.

Not yet, thanks for the reply, I will have a go with that when I get back to the office tomorrow and see if it cures it.

I’ve solved this. I hadn’t configured dhcpd.conf correctly in my pfSense router.

Apparently, [CODE]option tftp-server-name “ipaddressofserver”;[/CODE] doesn’t do anything, which I find weird. Only the [CODE]next-server[/CODE] seems to work.

Thanks for your help everybody.

Sounds like a “firmware” issue in the NIC that the “latest” driver fixed.

thanks for the bug report. that was caused by a typo has been fixed in the current svn, but it won’t effect you anyway. it is only there for a planned future feature.

…btw; the disk from the xp notebook was damage! fog gave me the the answer! nice! 🙂

As an update, I have taken a video to capture the error message and tom has been answering on [url]http://fogproject.org/forum/threads/hardware-currently-working-with-fog-v1-x-x.10685/[/url]

From IANABC
[QUOTE]If it is just being slow then I would agree that it is probably a driver issue, but in one of your other threads you mentioned that you fixed it…
[INDENT=1]I got the problem fixed that made the fog boot menu take forever to load by setting permissions to the tftpboot folder to 777 and the owner is fog and the restarting the xinetd service.[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Now when I try to upload/deploy an image, bzimage will not go past 0%.[/INDENT]
Does that workaround no longer work? I mean does it EVER complete or is it just slow?[/QUOTE]

I’m in process to see if I can disable but They have it bios locked.

Hi,
Upgrading to 2074 fixed it, thank you for your assistance, and for the link!

Now I can and will check the SVN’s and code/bug history before posting anything, which is great.

FOG FTW!

Thank you again,
D.L.