@Sebastian-Roth I removed the .size files from the image directory. The host then accepted the image without the error but the Ubuntu image (on the SSD) was not deployed.

Thanks for the reply. I am currently running off the 1.5.4 fog server but when i get a chance i’ll spin up the 1.5.7 server and try deploying the image with the .size files removed.
Regards
Paul

@george1421 The sda drive is a 120GB SSD.

I have double checked and the image definition is the same on both old and new fog servers.

The source system has an Integral 120GB SSD

Following further tests, target systems with the same Integral 120GB SSD accept the image without an error.

I have a batch of systems with a Western Digital 120GB SSD. These are all throwing the error.

Windows reports that the Integral drive is 111.79GB and the Western Digital drive is 111.80GB, so there is a discrepancy.

The image is captured from the smaller Integral drive.

Another thing to note is that Windows recognises the Integral drive as Disk 1 and the WD drive as Disk 0.

All target systems are the same hardware and the two SSD variants are plugged into the same SATA ports.

As a test, i have spun up an old fog server running 1.5.4 on Ubuntu 16.04.

I captured the same image from the same machine and deployed with no errors.

Unfortunately the old server doesn’t have enough space, hence the upgrade, so any help regarding a fix would be most appreciated.

thanks

Thanks for the quick response, this is the result of the command


Hi

Can anyone advise on this error.

The image is a multi disk/multi partition image

I’m running fog 1.5.7 on centOS 7

I have captured the image but getting this error when attempting to deploy.

Any help much appreciated.

thanks

@Sebastian-Roth Many thanks for this. I should be able to request that the labs can sit common VLANS with no port restrictions between them. I guess this might cause problems with multi-casting but worst case I can have a FOG server on each subnet. I’m going to start testing! thanks

Hi All

I’m a Tech at a school and I use FOG to capture and deploy images to over 300 PC’s in various labs.

FOG works great for me as I manage a number of complex software packages along with dual boot Windows/Linux setups. I have FOG client running on the images and, using multicast, I can re image all of my labs with a click of a button in a short space of time.

I currently have control of the network in the labs as all PC’s sit behind a pfsense firewall that I manage.

However, in the future this is likely to change, so all PC’s (and the FOG server) will be on different subnets, getting address from a DHCP server on a network that I have no control over.

My question is, can I still run FOG without control over DHCP/PXE boot? and, if not, are there any similar alternatives?

My thoughts are that, without PXE boot, I will need to boot from USB media and point the PC to the FOG server but I’m not sure if this is possible.

Any thoughts or advice on this would be greatly appreciated.

Thanks

@george1421 This has resolved the issue. Many thanks for your help.

I am experiencing an issue when multicasting to a number of PC’s.

The image deploys successfully but stalls at ‘Updating Database’ and eventually fails.

All PC’s are attempting to do this simultaneously so i’m guessing there is an issue with load on the web or mysql server??

The web interface becomes unresponsive and i have to shutdown the server and manually reboot the clients to resolve.

I have checked max_connections on the mysql server and that is set to 151. I am getting this error when multicasting to 20ish or more PC’s. I tested a group of 5 and had no issues.

FOG Version: 1.5.4
Ubuntu 16.04

Any help would be appreciated
Thanks