We are a rental company, so just have a small isolated network been the switch to image machines back to a standard image before going out to the next client. So not trying to deploy over a School IT network or anything like that.

Fog server network card 82540EM Intel Gigabyte controller, into 24 port switch in which all the clients are plugged into. This switch and setup hasnt changed from the last setup which worked fine. Changed the cables, still the same. Would it be worth doing a read / write test on the VDI thats on the raid?

Unicast, by ipxe booting first laptop then selecting “quick image” then selecting the image, then repeating until 10 clients are “quick imaging”

also to add the clients are dell m4800 / m4700 laptops with SSDs.

Its FOG trunk, svn 4363. avg speed to deploy with 8 clients is 750mbpm. The network shows the network cards as been 1GB cards, I/O of the raid seems to be fine, our switch is fine and tested. So much slower than our last build, but can’t figure out why?

Tested today, sent an image up to FOG compressed at level 6, Image is 40GB C Drive and 40GB Recovery Partition. Starts off at 4.5GBpm then steadys to 2.5GBpm. For deployment of this image back down to a client again starts around 4GBpm then slows to around 2.5GBpm, added 3 more clients and still around 2.5GBpm, im not at work at the moment so trying to get my colleagues to test and send me the figures over. Does this speed seem normal?

So I have finally rebuilt our FOG Server as follows.
i7 processor, 24GB Ram, 60GB SSD (Operating systems), 2TB drives in Raid5 =6TB, 2 Intel based Ethernet cards, 1 for internet and the other goes to our 1Gig 24port switch

System is Ubuntu 14.4 LTS running VirtualBox, Fog is running as VM, Ubuntu 12.4 LTS the virtual machine has 4 processors, 12GB Ram, 30GB VDI for operating system (Saved on SSD) and 2TB VDI for /images (Saved on the raid) Network is setup as 1 card = Internet through NAT and the other is FOG which is a bridged adapter.

2TB VDI is mounted successfully as /images, Network setting for FOG in the VM is set to static IP 10.10.3.49, 255.255.255.0 and 10.10.3.1 as Gateway. FOG SVN installed “successfully” with the static IP address, DHCP router address as 10.10.3.1 and DHCP service =yes DNS=no.

FOG works and we have sent a 3 partition image up (Around 80GB in total size) compression set to level 9, this took around 2.5 hours avg 2.5GB a min (started a lot faster) However deployment back down to 10 Dell laptops is much slower than before the rebuild, taking nearly 4 hours avg 500mb a min. Trying to understand why its much slower than our previous build (made by someone else no longer contactable “work related”) I am not sure where to start to fault find. Before it used to take around 1.5 hours to deploy 10 laptops with this kind of sized image. Any tips/help/save myself going greyer

Thanks

Matt

I have had to rebuild our FOG server at work, We have all the images saved on a VDI which is saved on a Raid5. Operating system is Ubuntu running VM with Ubuntu thats running Fog this is on a SSD. The VDI for images is mounted to /images and saved in the fstab to mount on boot up. I have changed the storage node to point to /images. However when taking an image of a pc it says its saving to /tmp/pigz1. In the end it fills the SSD up and we get an error about disk space is full on SSD. I can see that somehow the image has been saved onto the SSD, but not sure where, we now have a Snapshot of the VM which is 10.8GB when the Ubuntu VM VDI was only set to 10GB.

Sorry I am quite new to VM and FOG and have taken over this role from someone else.

Thanks in advance

Matt

I have also got this issue, updated to 4240 today and now when I click on “Create New Image” I just get a white page with bold front top left saying “Add new image definition”