Just verify your IPCOP setup is issuing the next-server and filename options. I believe option 66 and 67 are windows DHCP specific option numbers. the rest of the world uses next-server-name and filename options.

Hi,

this problem still exists, lindsay S explained the problem the exact same way i feel that issue.
I have exactly the same situation as lindsay so there must be still a bug in the scripts.

chad-bisd if i can help you with testing or something iam your man, iam hardly interested to
get that fixed. We like to use fog in our company but i need scheduling.

If i can speedup things with a donation let me know it then i will talk to my boss.

Iam just one step ahead from buying a 6TB Raid 5 System to have enough space for images
from about ~250 Computers.

Greetz X23

There is a small edit you can make to the task status screen to show progress for imaging. Out of the box, FOG only shows status for Single Partition - Resizable image type tasks. If you search the forums, you can find the thread that shows how to add the progress bar for other types of image tasks (Multiple Partition - Single Disk). I think it’s in the tutorials forums.

As for error messages while booting the FOG kernel, it’s pretty normal to get quite a few warnings about drivers, chipsets, etc. The FOG kernel tries to load a wide variety of device drivers in order to work on as many devices as possible. It may try to load drivers for things you don’t have in your systems, and you get errors or warnings. The acerhdf is the most commonly asked about because it’s only for a small subset of acer laptops.

Have you tried a different kernel available through the FOG web interface? Sometimes older kernels work better, sometimes newer ones do. If you can’t easily find a kernel that works for you, it’s not that hard to compile your own if you know what you need in it.

What version of FOG on which OS? Also, have you tried different browsers to make sure it isn’t a browser rendering/ajax type error? I have 19 images and all show up on the list screen for me. (FOG 0.32, Ubuntu 10.04 LTS, Chrome on Mountain Lion)

[quote=“Raff, post: 11706, member: 298”]Make sure the only computers that are in the Multicast group are the 2 computers you wish to deploy too. If there are additional computers in the group, they will sit at the please wait screen for a while until all computers are switch on or the timeout is reached.[/quote]

It was that Raff!

The Mac address was declared twice, so the fog server was wainting for the second host with the same Mac address.

Thank you!

Finally got it working!

My FTP settings on my FreeNAS box were not correct. I had to add a user to the FTP service called fog with the password used for the management console.

Of course, when I say working, I mean the upload portion. I now get a permission denied error when trying to send an image to a system.

So if I run it with Capone, it says [code]mount: <ipaddress>:/images/ failed, reason given by server: permission denied

mount: mounting <ipaddress>:/images/ on /images failed :Bad file descriptor[/code]

I have two storage nodes setup like suggested, following the instructions listed in this thread by icarus.

When I deploy an image, it tries to load the image off of defaultmember, which fails, then it tries to load off of my second storage node, which works fine, loads as it should.

Why does Capone fail, but host deploying work?

EDIT:

When typing [code]sudo exportfs -a[/code]

I get the following:

[code]exportfs: Warning: /images/dev does not support NFS export.
exportfs: Warning: /images does not support NFS export.[/code]

My /etc/exports looks like
[code]/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,no_subtree_check)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure,no_subtree_check)[/code]

Sorry if it feels like I am hijacking this thread, not trying to, just didn’t think my issue deserved a whole new thread.

I too have performed said fix for tasks… and the results are good.

I think you’ll probably find that most of that is cached. Linux has a habit of using loads of ram for caching and then giving it back in chunks as needed. Perhaps someone with more of a grasp could explain it to you a little better… but I’m guessing that your RAM is probably not going to cause you and issues.

If you want to test that out though do some benchmarking with your images etc before and after dumping the cached memory… Try this simple little script I use on some of my servers for ejecting it…

#! /bin/bash
clear
echo MEM before cache clear up:
echo
free && sync && echo 3 > /proc/sys/vm/drop_caches
echo
echo MEM after cache clear up:
echo
free

Write the above into a text file with vi/nano/whatever and chmod +x the file then run. Sorry if that’s patronising in any way, I just dont know what level of experience you have.

Ok fixed it. I just re-ran the installer over the install. Then went back and made sure my Database passwords were in the config file. It seems to work fine now. I am having severe throughput problems with this though. Looks to me though it is a ubuntu running as a VM thing though not part of FOG.

Thank you for your help.

[quote=“Jaymes Driver, post: 11647, member: 3582”]bjennings, can we start a new thread for you? Lets start with what the problem is, if it’s this PXE-E32 Time out issue, what linux version you are running and the fog version you have installed, then we can start troubleshooting your issue directly, so we don’t confuse topics or information expressed here.[/quote]
Yes, sorry, I will start a new thread.

I fixed my issue by upgrading to Ubuntu 11.10. After that the Fog installer was able to finish without the php-gettext holding up the process. Thank you to those who responded.

oops, nevermind…I changed the subnet mask under eth0 because I had a typo, but it didn’t accept the change…stupid Ubuntu haha…got it going now!

Nevermind…I made a wrong change in the dhcpd.conf.

Check your windows network configuration on the clients. If you use DHCP, make sure they are set for that. If not, check with your network administrator to make sure your TCP/IP settings are correct.

Thanks! I had done the mysql pwd change, and rebooted the computer, but maybe the password was still cached somewhere. After another reboot I was able to get back in. Everything’s copacetic now.

Hmm, I guess everything’s forwarded correctly considering I was able to mount it using a random fedora live-cd:
[LEFT][IMG]http://i.imgur.com/RgdIyzp.png[/IMG][/LEFT]

Maybe an issue with the kernel? with the debug option when pxebooting, can you manually mount NFS for testing?