@Tom-Elliott Worked Great!!!

@ozraelised I should probably have read more into this thread, Fedora 25 at the moment has issues with rcpbind, it doesn’t even run the installer correctly. It’s an official bug, and I think the Fedora devs are swamped at the moment (think they are secretly working on RHEL 8).

@lesliebright We all do dumb stuff, but only the men among us admit it.

@Wayne-Workman Wayne thank you for the reply. I used the that Junkhacker posted. It worked very.
https://blog.vbonhomme.fr/extend-a-lvm-partition-after-increasing-its-virtual-disk-on-virtualbox/

@Tom-Elliott this fixed the issue!

Thank you very much!

@george1421 Thanks for clarifying. The ftp server was the problem. The “Updating Database” confused me into thinking, the fog database fails to update.

@bmick10 yes. I’ve been working pretty hard on the units lately I’ll try to figure this out tonight.

@butch2861 As the Church Lady once said, “Well isn’t that special…”

Now that we know its a hardware class specific error. I wonder if this hardware is having a problem with the 64 bit kernel. We have seen some specialty hardware that has a 64bit CPU but externally its 32bit. I’m not saying this is specialty hardware, it could be similar in function.

I wonder what the results would be if you went into the host definition (You may have to manually register it if the kernel is panicing) set the kernel to bzImage_32 and the inits to init_32.xz This will force FOG to send the 32bit kernels to the client no matter what it reports to iPXE.

From your other screen shot I see 2011. Is the firmware the latest version available for this hardware. Lenovo has been known to have flaky early release firmware.

I deleted the entire machine and rebuilt the VM and followed centos OS instructions this time which resolved the problem. I’m able to capture now without any issues.

just an fyi for anyone installing this on centos 7 this is the guide I used.
Centos 7 guide

@george1421 I could, but shutdown /p worked just fine for me. I’m a firm believer in the KISS method so the less typing I have to screw up the better.

@p0Ldi Update to rc10 please first, then try again.

@lawrence1997 I know. Did you read what I wrote?

@SBodager That seems to have fixed the issue for the physical machines that were having issues but not the vm’s

@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.