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

@george1421 Thanks everyone.

Great work, thanks 🙂

@DarkStorm007 This is a very old post you opened up again. FOG was very different and has changed a lot. Please open your own topic and leave this old one alone.

Start the new one by telling us what version of FOG you are running and maybe the names of the fields you ask about (I guess it’s about printers but why should I have to guess, just tell us!!). Maybe even post a picture if you don’t want to spend words on it.

@tom-elliott

Tom,

We’re good on the cancellation issue, but I’m still seeing a series of packets with the same start time and ever increasing durations times for each subsequent snapin.
0_1502401559812_8e8425e1-fa40-46a0-a798-24addf32556d-image.png

I didn’t get that you made a change. I doubt I can be of any help with the code, but I’ll look.

The screenshot above is a single deployment of an image with several snapins. There’s a reboot after 0-W7PostImageCleanup and another after 1-UACDisable. So there are 3 “series” of snapins in this deployment.

2017-08-10 12:24:36 (2 snapins)

2017-08-10 12:25:28 (1 snapin)

2017-08-10 12:26:14 (6 snapins)

All scheduled as part of the image deployment and all separated only by reboots implemented by FOG as part of a snapin.

Jim

@themcv

OK - so yeah, maybe it was a DNS issue on the client side after all. One of the snapins I’m working on dorked the DNS search list.

I determined this by examining the spanins deployed to the host - 100% alignment with snapin that dorks the DNS searchlist.

Go Figure…

Thanks and sorry for the trouble…

Jim

Trying using noapic as a kernel argument.

Fixed, we appear to be uploading now.

@tom-elliott
I just tested Host registration and deploying image. So I confirm. It works.