Well thanks, I’m suppose to be getting some new equipment this summer to set up and I WILL be imaging with FOG, so I’ll remember this in case I run into issues!

First make sure your image is set up for MULTIPLE PARTITIONS aka the WHOLE disk.

Then take a look here: [url]http://fogproject.org/forum/threads/problem-uploading-ext3-ubuntu-image.459/[/url]

I found this from the link above. Others have had success, try this below:

Update: I finally tried manually using PartImage to pull the image with the plan to then copy it manually in to the server. In doing so, I saw that PartImage was erroring out (which FOG was hiding). Googling around found that running an fsck prior to uploading the image fixes the problem. I may dig in to the FOG code to see if I can make it automatically run an fsck prior to pulling any Linux image. For now, though, I just boot my source PC in to a live CD and fsck, then I upload the image. Works a treat.

Again, we nailed it. The solution was to disable the required SSL on the /var/www/fog/ directory. It was always on but since the upgrade it was keeping fog from sending the inventory.

Case closed for now.

Hi,

check this link:
[url]http://[serverip]/fog/client/[/url]
you will find the client service download and a zip with a prep utility you have to execute immediatelly before you do the image
(executing prep, reboot > image.)

AFAI know this part is missing in the wiki but iam not sure 😉

Greetz X23

Thanks for all the help, sorry I took so long to reply, tried several things and nothing seemed to work so just rebuilt the server.

Hi,

i could manage my problem.

Two NFS shares on the Windows NFS Server:
[QUOTE]- /images pointing to E:\images (for the mount on the fog machine (unbuntu)

/dev pointing to E:\images\dev (for the mount for the pxe client)[/QUOTE]
The FTP Server running on the Windows machine:
[QUOTE]- user same as configured under the storage node root directory is E:\images[/QUOTE]
E: looks like:
[QUOTE]E:\images
E:\images.mntcheck
E:\images\dev
E:\images-mntcheck[/QUOTE]
Everything is running fine now 😉

The need of a FTP Server only for moving files is more then a face palm, but i will take a look at the scripts. Maybe iam good enough to fix that for myself and the rest.

Greetz X23

Chad,

Thanks, that took care of it, deleted the old pxe boot file and voila’

Did you run the commands?

What was the outcome?

Awesome work Kamz87! It generally is something simple. I’ve had so many little things like that happen. Just make sure you always try and it never hurts to ask or read the wiki or forums for answers. Have a good one!

Installed 12.04 but ran into the same problem. I had thought that after physical machine restart, restarting tftpd-hpa, portmap and nfs-kernel-server had fixed the problem, but I came in today and ran into the problem again.

Many thanks, Jason, much appreciated. Cheers

Chris

Leon, are you still having issues?

From reading your statement I have gathered that you want to save your images from your FOG server on a network space, is this correct?

I know that FOG is going to need access to this folder with read and write permissions, I would first start with checking there and trying to make a public space where it will not be affected but network policies.

We use a Novell Network here and I run into problems with permissions all the time.

However I am not familiar with adding a space for the FOG server to save an image to, in my FOG server there is a drop down box where I can select “default” and possibly a node if I had installed one. I don’t know what is involved with locating the space on the network and adding it to the drop down list.

I would also install the Samba service of Ubuntu to help alleviate some of the problems your going to run into using a Linux box in Windows environment.

edit your /etc/rc.local

to include
[code]
/bin/sleep 30 && /etc/init.d/tftpd-hpa restart
[/code]

this should tell your linux to restart the service in 30 seconds after it starts this should take care of having to manually enter the command after a reboot.

I second the sysprep test. Sounds like Windows is confused about where the drive is located. Usually on dells, they are all on the same controller in the same slot, using the same hardware revisions. Maybe you have a different hardware setup due to ship dates or model revisions. Sysprep might help this.

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!