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

HELP: I cannot mark answer as solving the problem!

I worked with the OP over DM for quite a while and then setup a TV session. The root cause here is that ubuntu is the enemy of fog (bug). Then during the execution of the ALTER USER step in the link I provided below the password for the mysql root user became confused. We ran through the mysql root user password reset process to reset the password which worked. But the upgrade still failed to backup the current database. Long story short, there was a second background mysql process running causing the process the fog installer was managing to fail causing the backup of the database to fail. Once we found this back ground mysql process running we killed it and then restarted mysql. This time the install succeeded as designed.

Case closed.

@labanh This is strange indeed. You might want to take a look at the apache error logs. Might shed a light on what was wrong. See my signature on where to find the logs on your FOG server.

EDIT: Tom just suggested that this might have been caused by Ubuntu’s unattended upgrades! Good point. Keep that in mind.

@jim-graczyk said in FOG installed on small VM. Possible to drag and drop images when needed for deployments?:

Wayne is an expert, so maybe my approach is more work.

My suggestions take into consideration the present skill level of the person doing the operation. Adding a virtual disk would certainly work.

Fair enough.

Thank you for the response.

@thelostarc The error message sounds kind of weird. Although you have fixed it by using Chrome, could you please upload a picture of the error message here?

@sebastian-roth I finally got around to trying this out the other day and after running a check disk and recapturing the image it is now resizing the partitions correctly upon deployment. I didn’t have to modify the ‘d1.fixed_size_partitions’ again so I’m assuming that the capture process either worked correctly after running check disk, or else it just continued to use my modified version of that file.

Thanks for your help in resolving this issue everyone, much appreciated!

Repulled 1.5.0 RC 7 per Tom’s instructions and the fixes were applied (repush was done to RC 7 after I had already pulled it)