[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.

Tom, have no idea what the “symbolic link” thing is, but I ran the above code lines you sent to me. I now get:
TFTP.
PXE-T01: File not found
DASH-E3B: TFTP Error - File not found
DASH-M0F: Exiting Option ROM

I also tried restarting the TFTP daemon. Still nothing. Now NO stations will acquire the iPXE. What happened? How can I fix?

this is normal. that is the svn revision number, and technically you are no longer running the latest official version of fog. you are running a developer’s pre-release version.

Well, is tftpd-hpa service running when you reboot the machine?

If so then the fix won’t help you. If the service is not starting there is a way to make the service wait until the machine is booted and then it starts the service.

Incase it is the later of the two, the resolve is:

Change the line
[code]
start on runlevel [2345][/code]
in /etc/init/tftpd-hpa.conf to

[code]
start on (local-filesystems and net-device-up IFACE!=lo)
[/code]
And it is not a fault of FOG, this is a known issue with Ubuntu 12.04, and 14.04

You could try re-installing the tftpd-hpa service and see if that solves the issue:

[code]
sudo apt-get remove --purge tftpd-hpa
sudo apt-get update
sudo apt-get install tftpd-hpa
[/code]