Upgrade to Ubuntu 14.04LTS from 12.4LTS imaging broken everything else good
-
What can I say other than, the imaging feature is broken, it sets up the task then it reboots the PC, then it shows the job in the activity monitor, then BAM, it just clears out as if the job completed successfully. it hasn’t.
the PXE boot menu is working the web page is accessible, the Kernel is functional the TFTP service appear to be working.the imaging process seems to flash by and i cant see the error, what i am looking for is if anyone has seen this before and or where i can look to see a log file that may have recorded the failed process.
-
When you say “image process” are you referring to an Image upload? or an Image download?
What happens if you run a compatibility check from the fog menu?
[FONT=Tahoma]To [/FONT]Run a compatibility test.
[FONT=Tahoma]From the fog PXE boot menu, you will see:[/FONT]
[FONT=Tahoma]Boot from hard disk[/FONT]
[FONT=Tahoma]Run memtest86[/FONT]
[FONT=Tahoma]Quick host registration and Inventroy[/FONT]
[FONT=Tahoma]Perform full host registration and Inventory[/FONT]
[FONT=Tahoma]Quick Image[/FONT]
[FONT=Tahoma]Client system information[/FONT]
[FONT=Tahoma]Debug Mode[/FONT][FONT=Tahoma]A. Choose Client System Information[/FONT]
[FONT=Tahoma]B. Your computer will load another menu and it will look like this:[/FONT]
[FONT=Tahoma]1.) Reboot[/FONT]
[FONT=Tahoma]2.) IP Information[/FONT]
[FONT=Tahoma]3.) Partition Information[/FONT]
[FONT=Tahoma]4.) Check FOG compatability[/FONT]
[FONT=Tahoma]5.) Ping a Host[/FONT]
[FONT=Tahoma]6.) Display MAC Address[/FONT]
[FONT=Tahoma]7.) Show DMI Information[/FONT][FONT=Tahoma]C. Type 4 and press Enter[/FONT]
-
Happens to me when I forget to specify the image to use. Not that it happens alot, but…
-
No I mean when I try to get fog to deploy an image that we have used several times in the past without issue, to have it just in a blink of an eye say the task completed without actually doing anything. its compatible since we have used the exact same model for the last 9 months. now after upgrade to newest version of FOG, this happening.
-
“newest version of FOG” ?
according to your posting title and description, you only updated Ubuntu -
Understood. I’m just saying I had this happen when I created an imaging task for a computer without having an entry in the “Host Image” field. It was an older version of FOG at the time, I don’t know which one you’re using or if this is even possible with the newer versions.
-
You all must remember. I’ve added support for GPT and MBR since the release of 1.0.0. 0.32 and below only allowed MBR style disks to be imaged. Many times, I’ve seen now, that FOG is actually trying to create non-existent image files because the disk is setup in a particular manner but the partition table doesn’t match up. Meaning it’s creating non-existent partition where there really shouldn’t be any partitions. Because of this, fog can’t find the partition or write to it so it skips that partition and continue’s on in the process. In the case of GPT when expecting MBR, the data never has a place to be written to so it just “complete’s” while no information has actually been written. Please verify this by running a debug task and checking your system against fixparts, or in the case you intend to maintain GPT tables, make sure the data is where it is expected to be.