This is solved from a FOG point of view.

The problem was that a user replicated several large images overnight and Hyper-V expanded the VM, choking the main servers.

Thank you for all of your help @Sebastian-Roth!

@wayne-workman

Agreed on all counts, plus I don’t have images that need deleting at present to test, nor time to create images just to test deletion (at this point). I’ll check this as the opportunity presents itself.

thanks to all.

Jim

@J-Fog Any news on this? Please post the full fog.log as requested by Wayne.

@thebrennan47 Any news on this? The wrong IP is probably set for the Storage Node in the web UI. Go to “Storage Management” and edit the Storage Node (usually called “DefaultMember”).

@jglessner So is this save to be marked as solved or do you still have that issue? Feel free to open a new thread in case you run into a new issue. Better to open a new one and not mix up things in one case.

This seemed to work! Thanks!

@wayne-workman

Hi,

Finally I was able to install the Fog on Centos7 with little tweaks. Because of Proxy server remiphp56 was not installed so after the fog installation I have to uninstall Php5.4.6 and Install PhP 5.6 for fog 1.4.4 to work.

Thanks
Sudheer

@richard-wise Right that is usually the case when windows is involved. There are a couple of ways to side step the issue.

Not use windows at all. Use Notepad++ on windows Once the file gets to linux unaltered, use the linux command dos2unix to scrub out any remaining Windows bits left behind.

With that said, well done on the debugging!!.

With help From Geroge1421 we discovered that there was a rouge DHCP server connected to the network. It was running from a VM on a regular PC. Network admins were able to locate the port relates to the MAC address of the rouge server.

Now PXE is booting to FOG smoothly

That did it! Thank you guys!

@Brian-Hoehn From the postings of the other users it seems like the new init files Tom provided did help. So I suppose you see a different issue here. Please open a new thread and post all your details there - FOG version, OS version, picture of the error on screen, …

@jblack Great to hear you found and fixed this just by using the hostname. Though I am pretty sure this is something with your kind of special install method using ansible. Something in the apache conf I reckon.

Just open a new post and let us know if you run into another issue with this. Keeping my fingers crossed that things go fine now for you.

@quazz Ah ok I understood.
It’s ok for now, fingers crossed !

@chief I tried with a windows 10 build 1703 install and it booted just fine. Still not sure where things go wrong here but as we seem to have several people with this we should be able to figure this out.

Please edit /var/www/fog/service/ipxe/refind.conf. Change timeout to zero. Save this, change EFI exit type to rEFInd and boot the client. You should see a boot selection menu. Do you see it or does it hang even before that?

There’s also this concept: https://forums.fogproject.org/topic/8821/roll-calling-hosts-to-identify-problems

But instead of gathering a list of non-functional systems, you’d be telling them to copy their fog.log files to the share - and skipping the list building parts.

@sebastian-roth omg, just “Create New Host” and then create a task to deploy the image you want - I was playing with the last week!

Please close/resolve this thread. I foudn the answer on this post: https://forums.fogproject.org/topic/9604/kernel-offset-disabled-end-kernel-panic-not-syncing-vfs-unable-to-mount-root-fs/4 turns out my org must still somehow be pushing out pxelinux.0 even though admins said not. So I renamed a copy of undionly to pxelinux and its working. 🙂

Hey Guys,
Thank you for your replies. The issues I stated here was because of the UEFI being enabled. UEFI Didn’t like the fixed partition sizes. As the FOG Developers stated, changing the images to “Resize partition” fixed the issue for UEFI Machines. Using this method, I was able to make an image on a 500gb HDD and deploy it to a 256 SSD without issue.
In regards to the “not booting after successful restore from UEFI”, that issue was limited to older Dell modals that have never booted to UEFI before. Once i selected the boot device the computer booted fine every time after that. They booted even after subsequent re-images.
I am currently running version 1.5. RCx.

Thanks for all the help.

@george1421

I am now fully operational and up to date to boot! Thank you very much for your time Mr. George1421! It’s much appreciated.