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

I have a Stupid question. Is there a newer version of the KitchenSink Kernel that has the latest drivers in it?

Paul, have you tried a different kernel? Sounds like the driver for your Lenovo might not be in the kernel you are using.

I am still having issues with my original problem.

When I try to upload an image with a new Acer V5-121 I get an error:
“Fatal Error: Disk device not found!”
I have also seen:
“Unable to copy /images/dev/mac to /images/mac”

It does not seem to be a permissions issue since I have been uploading and deploying images since this issue occurred.

Sorry for late answer but I was away on holiday.

[quote=“HIBY144, post: 12854, member: 6881”]under images\list all images(your image)\ ----- did you ever change the image file name? if you did then you need to change it back. i did this once and it sounds like the same problem i had. you can change the image name (the one at the top) but not the (image file) ex(/images/windows7)…[/quote]

Nope never, have tried creating new images and still it didn’t work.

[quote=“Jay_S_FogUser, post: 12862, member: 6972”]Why do you want to change?? You must be crazy. Fog has lot of issues. If you’re bored and want to spend time exploring something new, watch a movie or learn to play a new game etc, :)[/quote]

Why I want to change? GSS2.5 hasn’t been updated in years and FOG has potential and it seems to be working for many others.

[quote=“Jay_S_FogUser, post: 12863, member: 6972”]@Ethyr, if it matters at all. I do pity. But none of the stuff you’re attempting to do is supported by Fog. Please read through the forum and you will find out for sure :). Hope this helps.[/quote]

How is pulling an image from Windows 7 not supported?

You can register those machines manually, when you know their MACs. So there is no need to switch any kernels. Just put in the MAC, name the host (any name will be fine), and include the path to the working kernel.

The specified hostname is the name we specified for the computer. It is using our naming convention.

For other people who might have gunzip problems, I discovered that gunzip called /bin/bash but only sh was installed in the init file (see the link above to edit the init file)
simply open /usr/bin/gunzip with a text editor and replace the top “#!/bin/bash” with “#!/bin/sh”
save the file and pack the init file according to the above link