[quote=“Blackbook, post: 14121, member: 2681”]Just revisited this - I set up a brand new ubuntu desktop and installed nothing but Fog on it - I reformatted the problem laptop and did nothing but put 1 txt document on desktop. I also reset the toshiba bios.

To check fog was working, I took a working laptop and did a quick host, an upload, and a deploy all successfully.

I then took the problem laptop, managed to get the PXE to boot to fog menu, did a ‘quick host’ first time, completed an upload (to a new image file) first time also, went to deploy it - and it got stuck at the same place as the video. Just dispays a ‘#’ when it should go to the blue screen.

I’m about to throw it all out the window.[/quote]

we had a problem child machine we just chose an older kernel for fog and magicly it worked… Our problem child was a Brand New Dell Vostro 2420 brand new out of box one Deployed fine the other we had to change to an older kernel to get to it deploy… Same Bios versions and Ethernet Firmware versions. Identical hardware. Go figure. we stepped back all the way to the 2637 kernel. Hope that helps?

Leroy check this thread out: [B][url]http://fogproject.org/forum/threads/ftp-connection-to-storage-server-has-failed.556/[/url] [/B]

if you upgraded to a recent revision of Ubuntu, you may need to manually start the service after a reboot.

The ESXi hosts that the virtual FOG server resides on are connected to a storage unit (15k disks with SSD cache) via multiple 10gbit iSCSI. The hosts connect back to the user network via multiple gigabit paths each. It is only FOG that has a problem with speeds, as other servers (Windows) are crazy quick. I’ve also used VMXnet3 as the adapter on the FOG server, enabling theoretical 10gig networking. There is no problem with downloading an image from the FOG server to a physical machine, only uploading from an ESXi virtual machine to the FOG server. Random.

Like James-Driver says, it is something to do with the drivers in the FOG kernel.

It’s still there, maybe someone with some expertise can help, I imagine a setting got wonked somewhere.

I just wanted to make sure you had the client installed and set up on the server for the actions 🙂

Coloumb - I had the same issue as you but I was able to get it to work. I had only 1 task in taskstate which was the one I was trying to deploy. I set the taskstate to 2 in the database which it removed it from my dashboard so I remade the task for the same computer and rebooted it and the deploy kicked off.

Hi Bryce,

Thanks for the response. I spoke with the programmer and he did not make any updates to the database. We are going to look into what tables and fields need to be updated.

Thanks.

Is this a windows 7 machine that is freshly reformatted? or one that you cleaned up to pull the image for?

Just in my personal experiences I have never had to set up the DNS and as far as the address for the dhcp server, I always set mine to match the fog address, it works for me. As far as having your fog server on a laptop, you are going to have to run a couple of different commands in the terminal every time you turn on the laptop…

[CODE]sudo stop tftpd-hpa
sudo start tftpd-hpa[/CODE]

this is all going off of my head, try it and see if you have any luck

did you run sysprep as administrator before you tried to pull the image? (first pic)

I had this issue on a new build and realized just now that I had put my server address into the gateway field in the network connection setup. When I put in the proper gateway and restarted it works like a charm.

Believe i followed the instructions to a “T” but it still boots to the default bzImage, i made the default the latest core kernel, and the specific kernel i wanted to set, to the kitchen sink, so there would be a visual difference. Each time i schedule a task it boots to the bzImage and you can see that it is not the same kernel. Added a few screen shots to hopefully show whatever stupid mistake it is I’m making.

[ATTACH]355[/ATTACH]
[ATTACH]356[/ATTACH]

[url=“/_imported_xf_attachments/0/355_Screenshot.png?:”]Screenshot.png[/url][url=“/_imported_xf_attachments/0/356_Screenshot-1.png?:”]Screenshot-1.png[/url]

Have you searched the forums yet? I believe there are several well written posts about exporting the database and backing up the images so you can move them to a new server.

I think this has been answered or is in the process of being answer in another forum/post @ [url]http://fogproject.org/forum/threads/no-job-found-for-mac-address.3969/[/url]

If so, please do not cross-post, it splits/duplicates the efforts of those forum users that are willing to help.

I wiped and reloaded with Unbuntu 13.04 and have not had any issues at all

I actually tried with 3 different sets of hardware - the computer that the drive was initially in, another computer that was untested with FOG (the same issue occurred) and then finally with the computer that was known-working with FOG (initially I didn’t want to open up the working computer to try it in there, but did it anyway out of desperation).

All three computers were working fine before I began the exercise (i.e. able to boot into their respective operating systems), but only one (the third one) was tested (and was working) with FOG.

The hardware is very diverse (see below), but all three are 64bit machines.

Computer 1:
(has since stopped working for a different reason - coincidental psu failure)
Gigabyte GA-G41M ES2L mobo
[B][SIZE=14px][FONT=trebuchet MS][COLOR=#1155cc][FONT=trebuchet MS][COLOR=#1155cc][SIZE=14px][B]INTEL CORE i5 - 2400 3.1GHz QUAD CORE [/B][/SIZE][/COLOR][/FONT][B][SIZE=14px][FONT=trebuchet MS][COLOR=#222222]PROCESSOR[/COLOR][/FONT][/SIZE][/B][/COLOR][/FONT][/SIZE][/B]
On-board graphics

Computer 2:
[SIZE=12px][FONT=arial][COLOR=#1155cc]MSI 990FXA-GD80 AMD 990FX Socket AM3+ ATX Motherboard[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=arial][COLOR=#1155cc]AMD Athlon II X2 260 3.2GHz[/COLOR][/FONT][/SIZE] processor
[SIZE=12px][FONT=arial][COLOR=#1155cc]SAPPHIRE Radeon HD 7970[/COLOR][/FONT][/SIZE] pcie graphics card x2

Computer 3: (known working with FOG)
[SIZE=12px][FONT=Helvetica Neue][COLOR=#000000] Zotac NM10-F-E Intel Atom D525 CPU (1.8GHz) Motherboard (including built-in processor and graphics)[/COLOR][/FONT][/SIZE]

In any of these machines, inserting the proxmox hard drive caused FOG to fail with the error described above. The drive was originally in computer 1.

Any thoughts as to what might be causing this?

Thanks!

James

Same here