@Sebastian-Roth …I think something is missing in my configuration…Good thing is we are getting a server soon so that will take care of DHCP…I will update the outcome here asap…many thanks…You guys are great…I have Fog setup (which I manage in out department at a university) and it works there like a charm without an issue…I dont know why its not working here…But I will figure it out…(with your assistance…)

Thank you guys, it seems like you kicked me in to the right direction. I remade whole server to be sure, reinstalled FOG using wiki guide and as far as the startup script go, I just needed to write this:

#!/bin/bash sleep 30 touch /var/lock/subsys/local systemctl start mysql exit 0

I was just dumb enough to not realize, that you need to write this script only in case, when something does not work. Well, sorry about that 🙂

Now everything seems to run fine - I don’t need to do a damn thing even after a reboot. Nice!

As to why I needed to do these timing stuff in the first place - since you all claim that CentOS is otherwise rockstable - I seriously don’t know myself. If you want to look into it, I don’t mind to cooperate with you guys.

Thank you guys!

@Wayne-Workman
Hi,
Ok i understand.
Actually majority off our classroom reboot at the same time for software update in night (same time is residual effect with green fog on old version).
I will adjust power management (good amelioration in this version) for spread out this reboot.

Thanks.

It’s not a “probably” it’s a definite.

The github source code stuff is separate, but the places it uses to download the binary packages attached to release files is directly of aws s3.

@cnkpadobi Thanks for reporting back.

@SOL that should work

@WillB I have asked for this in the past too (via feature request). I used this function back in the 0.29-0.30 era and it worked great because our system names are based on a OU prefix plus the dell asset tag.

There are other ways to get this to work, some manual some using postinstall scripts. It would be better to have that function back in FOG (IMO). But as Tom says, imaging comes first.

OK thanks you. Finaly, I’ve up my VM size and problem solved :P.
My windows server is in prod, I can’t make tests on it.

Thanks you guys 🙂

@Grizzly In the long run, you will not be sorry you upgraded. Plus extended support for 2008 is only for just a few short years.

@Tom-Elliott Thanks, that worked!

Just a quick update. I am not sure why it happened but I am glad it has. I decided to rerun the installer script on my Storage node this morning and low and behold, when I logged into the management interface under the “storage node disk usage” drop down appear the storage node disk stats. I can not explain it may be some can but the problem is resolved.

One might think FOG is pretty close to what you want today. If you go into the quick image menu FOG today displays a list of all images, but the default image assigned to that workstation is selected by default. So FOG knows the defined image for that computer, the trick (solution) is to not have fog show all the other images. After the menu timeout the defined image is started if no one touches the keyboard.

While I’m sure it not as easy as this, but if you could find the sql commands used to display that menu, one might be able to tweak it to only show the assigned image.

This was just an idea, without any basis of fact in the code.

@bootsnspurs said in Trying to add clonezilla to PXE Menu!:

@george1421 This code worked for me. Thank you.

Thanks Tom also.

please mark as solved 🙂

@craigtighe Can/Will you confirm the exact settings of dhcp option 66 and 67?

dhcp option 66 must be the IP address of the new FOG server
dhcp option 67 should be undionly.kpxe (or undionly.kkpxe) Make sure its spelled correctly. Using pxelinux.0 WILL generate a kernel sync error. That is known, fog moved away from syslinux quite a few years ago.

And as Junkhacker said, if you could snap a clear picture with a mobile and place it here we can see the context of the error too.

@george1421 Excellent information! thank you!

What I’m trying to say, is how to appropariately fix the problem in rc-10.

The problem, as you’re seeing it, is NOT a bug, rather a fix of an older bug. The only reason it “didn’t” do this in the past was because it was broken.

@george1421 great thank you! I will continue to work on this 760 and not try to confuse them again! lol

@Junkhacker thx for comment 🙂

@todachuy2406 The sprintf you keep referring two had nothing wrong with it.

It was simply your using pxelinux.0 that was causing the problem with the booting.

@MikeoftheLibrary After reading that, there’s another thing I forgot to mention. Each multicast session only goes as fast as the slowest host. So if one of them has bad RAM or a failing disk or bad patch cable, this would slow down every host in that multicast task. This could be your issue - and most likely is since you’re using business grade network equipment.