Posts made by Just10

I just wanted to chime in - my issue was the target disk was slightly smaller than the original as well (physical to ssd and assuming, without double-checking).

after typing that… I realize the image is probably larger than 40gb. If our techs put 40gb drives in these machines - I have a bigger problem.

ls -al /images/DellAllinOne8GBWIN764 shows:
d1.mbr
d1p1.img
d1p2.img
The image is multiple partition - single disk.

sfdisk -d /dev/sda shows:
/dev/sda1/ : start= 2048, size= 204800, Id= 7, bootable
/dev/sda2/ : start= 206848, size= 976564224, Id= 7
/dev/sda3/ : start= 0, size=0, Id=0
/dev/sda4/ : start= 0, size=0, Id=0

I am now running 2948. Same issue. Running through download debug now. I will report back shortly.

The machines were delivered to us from Dell w/ a french version on Win 7 installed - they have an OS loaded on them already.

I’ve also attempted this using a laptop that I have imaged prior and receive the same outcome.

Tom,

When I noticed I had an issue, I upgraded to the Kernel - 3.14.2. I was then unable to pxe boot to the fog page (to register the client, memtest etc). I installed Kernel - 3.18.4 and resolved that issue.

Here is the video (excuse the auto focus). I have a task set to download. The video ends at the point that the machine restarts back to the fog pxe menu and the tasks shows complete.

[media=youtube]X29p6H78EXw[/media]

I checked that as well - it is pointing to undionly.kpxe

I’ve verified that my TFTP Server settings match the fog server. (instructions via [url]http://www.fogproject.org/wiki/index.php/Unable_to_connect_to_TFTP#For_Versions_.24-.32[/url] )

My tftp username/password match my fog server un/pw. The storage group matched the fog un/pw.

Running tftp -v X.X.X.X -c get undionly.kpxe - reports no issues. I received a reply (103272 bytes in 0.1 seconds) etc.

The firewall is disabled. (sudo ufw disable).

My fog server is not the dhcp server - dhcp is setup on a windows box.

Yes (after updating to the new kernel) I can boot to debug.

Is there a log file somewhere that will tell me what is happening when the device attempts to download an image?

It runs through the process and displays “task complete, restarting” all in a matter of seconds. Fog thinks it has uploaded the image without issue but it never makes it to the progress screen showing the imaging partition.

Sounds like this guy also had my issue:
[url]http://fogproject.org/forum/threads/windows-client-notices-task-reboots-and-boots-into-pxe-but-just-goes-back-to-windows.10139/[/url]

The resolution was: TFTP Server Settings were set incorrectly

Hopefully this helps you point me in the right direction. Thank you for your time.

Well - I will test that as soon as I revert back to an older kernel. The new one will not allow these machines to register. I’ll start fresh Monday.

Also - it is not specific to this image. I have 5 different images, none that will allow the machine to start the process.

Started sometime last week… maybe an Ubuntu update? I did not have an issue imaging prior to whatever happened.

Recently I am having issues deploying an image to clients. I am able to upload the image from the device to the fog server but then deploying to another machine - nothing.

Download task created for [U]machine [/U]with image [U]DellAllinOne8GBWIN764[/U]

The log show the machine ran for a total of 4 seconds.

fog machine 2015-02-04
20:55:04 2015-02-04
20:55:08 00:00:04 DellAllinOne8GBWIN764 Download

I am still able to pxe. The full registration works, but again reboots before the image deployment piece starts. Same outcome when creating a task for the machine.

This is not specific to one device - I’ve tested other devices with the same outcome. Can someone point me in the right direction?

Running [B]1.2.0[/B]
Kernel 3142