There are a few things here.

Upgrade to 1.5.2 because it addresses a few issues. The 780s did have an issue with pxe booting and picking up an IP address. I don’t feel that is the issue here, but just be aware. Can you post a clean picture of the actual error so we can see the context of the error? When pxe booting happens and then we see random issues with dhcp, that is typically related to having a network switch with spanning tree enabled (a good thing), but the switch is not using one of the fast spanning tree protocols (not such a good thing). As Wayne said, put an unmanaged (dumb) switch between the building switch and the pxe booting computer. If the computer boots and runs through FOG OK, then your building switch does have STP enabled instead of RSTP or what ever your switch vendor calls it.

@sebastian-roth It’s possible, but that can be done right in the gui.

@joe-schmitt said in FOG 1.5.1 ~ Unable to create image:

@Sadowsky80 1.5.2 was just released due to the list of bugs in 1.5.1.

https://fogproject.org/download has been updated with the 1.5.2 instructions.

Awesome! Thanks for the quick fix

@flareimp It should not. I’m about to release 1.5.2 (considering the bugs listed) which means you’ll have to edit the file again on install.

You can help simplify this by doing:

mv /var/www/fog{,_back} ln -s /var/www/html/fog /var/www/fog

@mz3bel said in Can't add new hosts:

PS: What i’m trying to do is to implimenting 4 Laptops with same image pré installed softwares. Is there any way that i can do that with rj45 cables no network? so that i can just deploy the machine when i need to ? and take them off, so the students could use them

FOG needs certain network resources to work. You must have DHCP setup to supply the network booting configurations to the pxe target computers. You can have FOG do this for you, or you can use an existing network infrastructure. You can setup fog on an isolated imaging network, or you can setup fog on your existing business network. You must have some kind of network, even a 5 port small switch will work. It is technically possible to setup FOG to image a single computer at a time by just using a cross over network cable, I’m not sure you really want to go that path.

@kmstuartjackson Hey, just letting you know that 1.5.1 was released overnight. If you used the git method to download the FOG installer all you need to do is change to the fogproject folder and download the latest installer by issuing a sudo git pull request then change to the bin directory and issue a sudo installfog.sh command again to rerun the installer. Your fog install will be updated to 1.5.1.

@Taspharel Client version 0.11.16 (included in the FOG 1.5.1 release) features the new Snapin messages (currently only for English, other translations will follow in future releases).

Thanks for suggesting this change!

@george1421 Thank you for all the info I am going to start working on this.

@george1421 Didn’t see any packets except for a single UDP packet every 2 seconds or so after the client checked in and loaded up into partclone. Turned out there’s some hardware issue with the server I had been using. Thanks for your help!

Hi,

for all the surface cramp i always used this one with success without any special settings:
https://www.amazon.com/Microsoft-3U4-00001-Surface-Ethernet-Adapter/dp/B00N3JHBFM
There is also another one, but i can just talk for the one with the skewed usb sheating. I don’t know if the other one has the same interiority:
https://www.amazon.com/Surface-USB-Gigabit-Ethernet-Adapter/dp/B06ZZNPHQX

Regards X23

Fixed! thanks for the prompt responses, love this forum, you guys are always so helpful!

There is a bug in 1.5.0 with the new UI that is causing this slowness. The issue is fixed in 1.5.1 (due to be released soon).

Went back to Fog Node’s instead of Windows and it’s working as expected now. You can resolve this.

@george1421 Thank you very much! I was able to modify the script to fit our setup. Everything is working smoothly now.

Thanks again!

@george1421 Thank you so much! This has resolved my issue.

@jon-fuentes The disk space error message is an incorrect one. The issue is partclone is not passing enough information back to FOG on why it aborted. The answer is probably sprawled across the partclone screen just above the screen shot you provided. The fog service only can tell that partclone aborted for some reason and the “guess” was the hard disk on the fog server is full. Rerun your imaging again and watch what message partclone displays.

Also you might consider upgrading your version of FOG sooner or later. FOG 1.5.1 is waiting for release so you might want to hold off for a bit to upgrade, but you should upgrade once 1.5.1 there are quite a few disk imaging fixes in 1.4.4 with a handful more in 1.5.1. So you should consider upgrading to make your imaging a bit smoother.

nevermind

With a quick teamviewer session this issue has been resolved. The issue was just the sequence of install and ensuring eth0 was up before installing FOG.

@amadrigal Just want to bring up my initial thought about maybe OpenVZ not being able to properly handle multicast in the first place. Can you try setting up another test FOG server as KVM instance just to rule out that possible issue!?

@george1421 Oke! Say it when you found something.