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.

When I Multicast I See that the Status Percentage makes no sense. Does anyone know how to fix this?

Also, make sure rpcbind and nfs services are running. Through more searching, it sounds like it could be the NFS service isn’t running. Try running:

/etc/init.d/nfs restart

If it fails, check your rpcbind service and make sure it’s running.

Your commands may vary differently based on the OS you’re running the fog server from.

[quote=“darkapec, post: 14184, member: 11250”]Are you saying I should leave [CODE] ltsp/i386/boot/vmlinuz[/CODE] completely out or does that need to be replaced by something else?[/quote]

Yes, I think Your menu option should look like this:

[FONT=Consolas]LABEL LTSP
MENU LABEL LTSP 12.04 x32
KERNEL ltsp/i386/boot/linux.c32
APPEND initrd=ltsp/i386/boot/initrd.img ro quiet splash[/FONT]
[FONT=Consolas] [/FONT]
[FONT=Consolas]If that still doesn’t work, try:[/FONT]
[FONT=Consolas]LABEL LTSP
MENU LABEL LTSP 12.04 x32
KERNEL ltsp/i386/boot/vmlinuz
APPEND initrd=ltsp/i386/boot/initrd.img ro quiet splash[/FONT]

Is fog service running on the system? Double check that the fog client is installed and see if that helps you out.

Do do this go to the webpage:

[url]http://<your-fog-server-ip>/fog/client[/url] and download and install the client on the machine. Then try deploying the snap-in.

So I have been experimenting with limiting the TFTP block size to 1024 but I don’t think it is working. The way I am testing is this: I am observing a normal PXE boot with WireShark and looking at the size.

What I did in an attempt to limit the block size was this:

Edit [FONT=Times New Roman]/etc/default/tftpd-hpa and include [/FONT][FONT=Times New Roman]“-B 1024” under the OPTIONS line so the entire tftpd-hpa file looks like this:[/FONT]

[CODE]# /etc/default/tftpd-hpa

FOG Modified version

TFTP_USERNAME=“root”
TFTP_DIRECTORY=“/tftpboot”
TFTP_ADDRESS=“0.0.0.0:69”
TFTP_OPTIONS=“-s -B 1024”
[/CODE]

What am I missing?

I think it is a hash for the pass instead of displaying the real password.

The wrong pass was the same problem for me but not showing in the error you got.

Nice to know, that the problem is solved now 😉

Also, if it keeps being deployed, check your /tftpboot/pxelinux.cfg folder. If there are no tasks, you should only have the default file. Chances are, and I’m only guessing, you’ve got a file that is representing that system’s mac address in the format of 01-XX-XX-XX-XX-XX-XX where the X’s correspond with your systems mac address. Delete this file and you should no longer have this issue.

Thank you,

I’ve found that any time I’ve had the hdparm: ioctl 0x304 failed: Inappropriate ioctl for device issue, it’s not necessarily a driver issue, though it could very well be one. However, check your PXE file.

Make sure that the web part of the pxe server: does not look like this:
10.0.7.1/fog

Make sure you add the trailing slash otherwise you’ll see this issue.

On the same note, make sure your FOG Settings Page :
FOG Configuration (? Circle Icon) -> FOG Settings -> Web Server section -> Web Root also has the trailing slash as this is used to create the boot file for the hosts when tasks are setup.

Hopefully this helps.
[COLOR=#000000]10.0.7.1/fog/[/COLOR]

SOLVED: Changing the multicast queue size from 10 to an arbitrary number, then back to 10 corrected the issue.

Hi am_vd5,

Make sure that the disk to which you deploy the image is equal or greater in size as the disk from which you upload it.
The ideal situation is to prepare an image in the smallest disk you have so later you can deploy it to bigger disks, because if you prepare the image in a quite large disk you will not be able to deploy it to smaller disks.

Hi, surender!
The reason why you are getting that error is because PXE needs to extract the .iso to the physical memory, so if you don’t have enough memory it won’t work. In this case, you would need 3 Gb RAM to extract 2.7 Gb windows.iso.