I just noticed I did not see the pro4000 on the hardware list maybe it is a bios error or sorts Ie not supported?

When I have that kind of trouble, it is usually because I forgot to defragment the drive before I image it. Try that and running a check disk.

Another thing that slows down multicasts is actually the performance of the hosts themselves. During a mutlicast the FOG server sends out the image in chunks and waits to get confirmation from each host that they’re ready for the next chunk, so if one host has a bad hard drive or any other issue with receiving and writing the chunk to disk it’ll slow down the entire session.

I should add that I can use putty (ssh) to connect to the server, and log in with ‘fog’ and ‘password’.

Yes running Ubuntu latest just performed the update seems to be a bit better now along with mysql

[quote=“BryceZ, post: 3249, member: 2”]Check the /tftpboot/pxelinux.cfg/ directory on the FOG server for the file 01-<MAC ADDRESS>. Delete it.[/quote]

Bazinga! That did it. Thanks for the help!

I would assume you can move the image file and create a new image that points to it. I haven’t moved images between storage nodes, but this technique has worked when I want to use an old archived image to restore a graduate’s laptop. I just ftp the image up to fog, move it to the images folder, then create the new image pointing to the image file. Create the corresponding host to use it and it always deploys just fine.

Are other machines getting their images OK?
Have you tried rebooting the server?
Do you have a storage node set up?

OK, I haven’t figured out what caused this, but I have found a way around it. I ripped fog out by the roots and reinstalled. I opened the web page to create the database and when I migrated the old database to the new, I only migrated the tables relevant to the systems. That is, I deleted the SQL regarding the table ‘globalSettings’ and reset all the settings by hand on the ‘Fog Settings’ page. Now, everything is working.

I just created a .vfd file the same way I would make one with the NIC specific .dos file but using the UNDI .dos file and added it to our current Symantec PXE server. I have tested four different machines that I know use four different NIC drivers, all four booted into ghost and I was able to connect to a session. So it was as easy as what I hoped, I guess there could be some NIC’s it might not support but everything I have tested seems to work so far.

But thank you for your offer.

Regards

Rob

No worries, glad it worked!

And I was right there with you when that happened to me, beating my head against a wall, trying to figure out what on earth was going on. I think I’d done so much flailing damage to my Fog installation that I just reinstalled after I figured why the dhcp-server wasn’t working.

[quote=“boon, post: 3157, member: 833”]What is the outcome of a multi-partition image?[/quote]
Mutli-partition seems to have worked. I haven’t tried deploying the image, but it spent a decent amount of time imaging. The files look right on the server, d1.mbr and d1p1.img (11.4 GB). I guess I’ll try a single partition image with a different model laptop/computer when I get the chance, see if it works better or not.

Sounds like the location set for /images is pointing to storage on the network but can’t get there.

This post has some similar sounding things which might help:
[url]http://fogproject.org/forum/threads/fog-server-fatal-error-failed-to-mount-nfs-volume.115/[/url]

Answered this one myself.
Install Ubuntu 10.04 & it installed with no problems.

Your best bet is to read the Fog user guide:
[url]http://www.fogproject.org/wiki/index.php?title=FOGUserGuide[/url]
Have to got the server set up correctly so that you can tftpd boot? Do you get the pxe menu up?

I also had to disable selinux and the firewall in addition to the steps provided in the post from sam-white to get it to install properly. After I did all of those steps, everything worked fine and I have been using that server for about a month now.

Had a similar problem. Option 66 is being passed but the next-server in the bootp wasn’t set. Try using the CLI on the fortigate to go in and edit the DHCP settings.

From the CLI:

FORT-310B # config vdom
FORT-310B (vdom) # edit <vdom name>
FORT-310B (<vdom name>) # config system dhcp server
FORT-310B (server) # edit 1 //Replace 1 with the number of the DHCP server id on the fortigate if more than one configured
FORT-310B (1) # [COLOR=#ff0000][B]set next-server 192.168.X.X[/B][/COLOR]
FORT-310B (1) # end

Ok, after changing the label boot parameters to this:
LABEL fog.GParted
kernel fog/kernel/bzImage
append iso initrd=fog/Gparted/gparted.iso raw
MENU LABEL TEST - GParted 11 Disk Partitioning Utility
TEXT HELP
General Disk Partitioning Utility
ENDTEXT

the image boots partially until I get this error message in the picture attached. I feel that I am getting close, just don’t know enough about Linux to do figure this out on my own yet.[ATTACH=full]105[/ATTACH]

[url=“/_imported_xf_attachments/0/105_Error.jpg?:”]Error.jpg[/url]

I am having the exact same issue, did you ever find a solution?