Hi everybody,

so far I think FOG is amazing, but I’m having a bit of trouble deploying an image.

I’m using FOG to bare-metal backup all of our workstations. They are mostly different hardware so I’m looking for a way to deploy the backed-up image to a new machine if needed (eg. the old hardware dies and cannot be replaced). The problem I’m having is that the image will deploy fine, but the system reboots at the Windows 7 startup screen and I cannot get it to boot.

Now, I’ve seen this before and I’ve never had a way to get around it. If the drivers configured in the original image don’t jive with the new hardware, I can’t get the system to boot.

Is there any way of imaging the workstations such that their images can be deployed to any type of hardware? Or am I looking for something that’s impossible?

thanks for any help.

Thanks for the info. That’s useful.

Hi Everybody,

I’m posting this as a problem and a solution. I hope it helps somebody:

I now have FOG working really well with most of my clients; however, I have one client that simply refuses to get an IP address from the DHCP server. It exits out with a PXE-E51 “No DHCP or DHCP Proxy Offers received” error.

I found this weird because the rest of the clients get an IP from the DHCP server no problem. The solution I found was something I knew nothing about before I researched it.

[URL=‘http://h30499.www3.hp.com/t5/ITRC-ProLiant-Deployment/PXE-E51-quot-No-DHCP-or-DHCP-Proxy-Offers-received-quot-error/td-p/3057862#.UgKOmqLktz8’]The answer was HERE[/URL]

If you have manageable switch and you have Spanning-Tree enabled on it. You’ll need to enable Port-Fast (Cisco lingo) or Fast-Link (Netgear lingo) on each port that’s giving you trouble. It may be called something else on your switch, so it’s worth looking at your manual.

YMMV with this. I have no idea if it breaks anything else in the network but I haven’t noticed anything yet.

okay, I solved this.

The issue was in my apache settings. This server was being used to serve other webpages using VirtualHost containers. I had “deny from all” set on my VirtualHost and that was causing some issues. I also had a permanent https redirect that might have been causing issues too.

Once I fixed that I got the hosts to register and now I can image them.

I hope this helps somebody.

Okay, so I can boot to the debug mode command line just fine. I get an IP address and everything, so the NIC is working with the latest kernel but I simply cannot register the host.

When I type in the “fog” command I get:

[QUOTE]Error detected.
Cannot determine Operating System type[/QUOTE]

The fog.man.reg command gives the same ioctl error as above.

PLEASE somebody help me debug this.

I’ve tried this with three other computers: A Dell Dimension C521 circa 2004, a Shuttle XH61V which is fairly new and an ANCIENT HP Pavilion a1106n.
They all give the same errors. I have a hard time believing that not one of these computers is compatible.

Is there another reason why this could be happening?

Thanks for the quick reply. I tried the bzImage file that you point to but it immediately gives me a “flags mismatch” error and then the same thing happens.

How can I tell what driver isn’t working? There has to be an easier way than this, no?
Also, those fixes seem to be for an Atheros NIC but these computers are all Broadcom.

Hi Everybody,

I think I’m going to love FOG if I can ever get it set up correctly.

I cannot seem to register any hosts onto the server. Most of the computers are Vostro 230s which are compatible as per the [URL=‘http://www.fogproject.org/wiki/index.php/WorkingDevices’]working devices page[/URL]. I can get to the FOG boot page, but that’s it.

I have tried multiple different kernels, editing /tftpboot/pxelinux.cfg/default and making sure the ip address is correct but nothing works.

I consistently get an “inappropriate ioctl” error.

What am I doing wrong?