Posts made by imagingmaster21

@tom-elliott No only ones storage node.

@tom-elliott
But nothing gets written to there, even when it gets stuck at 97% nothing is there.

@tom-elliott
Here you go:
https://dl2.pushbulletusercontent.com/4lm814kFRT4PvEEc2SX1RCiV71xqciF1/20180302_143432.jpg

So basically if I pull an image off our main FOG server and then capture it off our mobile FOG (built on a laptop for imaging on the fly) server it will capture up to 97% and will end up rebooting without stating any errors. If you look in FOG Task management it will show it still at 97% but the machine will reboot as if it was captured. If you look in the images directory and look at the folder for the image there is no files in there. I’ve tried clearing the task and restarting the task and still no luck. I also tried a different network switch.

@tom-elliott

Even at 97% nothing gets written to the images/dev directory the folder is blank.

@Tom-Elliott I restarted the server and it is still getting stuck at 97%.

@Tom-Elliott The drive that I am capturing the image off of only has 30.6gb of used space.

@tom-elliott I have 196 GB available.

@tom-elliott Ok. So what would possibly cause it to get stuck at 94%? This image was a known good one that was pulled off another FOG Server. It is being put on a FOG Server that is on a laptop to image on the fly. I verified all the settings in the FOG interface are good and that the fog config files match setting wise, with the exception of different IPs.

I am trying to capture a image and it gets stuck on 94% during the capture process. I noticed that in the images directory it does not create a folder for any image I make. Is FOG supposed to create the specific image folder right when you create the image or is it after it completely captures?

@wayne-workman Running that command fixed the issue.

So I am setting up a FOG server. I got DHCP working properly and is handing out IP addresses. So I changed the IP address of the server from 172.16.10.55 from when I initially installed FOG. After making my changes in both the FOG configuration file and on the FOG web interface for the IP settings.I tried PXE booting a machine and got the following when trying to PXE boot a machine:
tftp://10.10.10.1/default/pxe … ok
http://172.16.10.55/fog/service/ipxe/boot.php… Network unreachable(http://ipxe.org/280a6090)

I then tried running the FOG installer again and got the following result in the terminal:
Version 1.4.4

• Found FOG Settings from previous install at: /opt/fog/.fogsettings

*Perfoming upgrade using thses settings
Sorry, answer not recognized.

Please change the installation directory
Running from here will fail.

Any suggestions???

@Anson-Washington @Wayne-Workman
So I am looking to do the same task here. I didn’t really find a clear cut answer but how much disk space is necessary for just FOG itself? I am planning on using a laptop to do imaging for long distance sites. I would only have two images on there, and on my FOG server those only take up about 35 gb of space. So what is the minimum storage requirement just for the FOG software itself?

@wayne-workman
Add more storage.

So I would like to add another storage node to FOG. So if I would get another SDD drive in my server, what would be the process of adding it to the FOG Server as another storage node?

Is it possible and safe to rename images in FOG? Also any best practices with this?

@quazz
Thanks that fixed the issue!

@sebastian-roth
Below is the error that started all this.

@sebastian-roth
I am in the process of testing that image on the first machine. With those settings UEFI and CSM enabled encryption worked on the image I built from scratch. So I rebuilt it and pulled it on FOG. I am imaging it on a machine right now to test out to see if it will encrypt per GP. And yes secure boot is turned off during the imaging process, while UEFI and CSM is on.

@sebastian-roth
Think I found the issue in the BIOS:
If it’s FAT32 (so UEFI boot) go to BIOS and turn off secure boot but leave in UEFI mode. Enable CSM support. If it’s FAT32 (so UEFI boot) go to BIOS and turn off secure boot but leave in UEFI mode. Enable CSM support.

I am building a image from scratch and will try it and will let you know once I am able to test it.

@sebastian-roth

I tried both resizable and not resizable and no luck.