The reason output is useful is it can tell what’s going wrong. It may say, not correct format which would tell us to use a newer or different file. Maybe it’s just not reaching the tftpserver for some reason, in which case it may be saying timeout or cannot load file.

Either way, outout is always useful, even if it isn’t helpful.

That being said, one resource to look at for efi pxe booting could be:
[url]https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-netboot-pxe-config-efi.html[/url]

While I don’t know all the possible methods that will get your system actually working, it’s one place to start.

the code tom’s posted is what i actively use to handle Win7/8/8.1 (mutli-partition) and i build my image in vm and have the disk only a few GB’s bigger than the image (20-25GB) and expand if the image gets bigger that way you never have to worry about putting it onto a “smaller hard drive” and extend partition in the unattend handles the rest 🙂

[quote=“Matthew Hood, post: 10086, member: 353”]The fix that I have found is to run a startup repair with the windows 7 cd then try reimaging.[/quote]

Just wanted to add that this fixed the problem for me. The log from the repair stated ‘Corrupted MBR’. I think this means the HD had itself confused with a toaster.

[quote=“mpmackenna, post: 893, member: 373”]
[LEFT][COLOR=#333333]I have the below error over and over again in my FOG log viewer. I checked to see if my /var/www/fog/commons/config.php file had the correct settings and it does. I also was able to log in to the mysql db on the fog box without trouble. The db is on the same local machine as the FOG installation. Can someone please tell me how I can further troubleshoot this error?[/COLOR][/LEFT]
[LEFT][COLOR=#333333]I am running FOG 0.32 on Debian 5.[/COLOR][/LEFT]
[LEFT][COLOR=#333333]Thanks,[/COLOR][/LEFT]
[LEFT][COLOR=#333333]Mike[/COLOR][/LEFT]
[LEFT][COLOR=#333333][01-30-12 1:12:13 pm] Failed to connect to database server, will try again in next iteration.[/COLOR][/LEFT]
[LEFT][COLOR=#333333][01-30-12 1:12:23 pm] Failed to connect to database server, will try again in next iteration.[/COLOR][/LEFT]
[/quote]
My problems with task hanging and getting [COLOR=#333333]“Failed to connect to database server” messages, [/COLOR]were solved by changing “WOL_INTERFACE”, “eth0” from 0 to “eth1” in both config files
/var/www/fog/commons/config.php
and
/opt/fog/service/etc/config.php

I solved it this morning and now, I found the same problem that yesterday “Unable to move /images/dev/00XX… to /images/…”.
I’m testing many solutions found on Internet…

<begin rant>
I run into that problem as well, cisco has been SO KIND to provide me with the software to manage them [B](COMPLETE AND TOTAL SARCASM!!!)[/B]

I’ve been in the run around with them for months, I keep getting those emails saying “this ticket will close in 4 days because there is no response” so I blast them with “I still need software and I still need these switches added to my account so I can service them” and good ol Mark Long will hit me with his “Our apologies, your product WS-C2960S-48LPD-L serial number EXPUNGED is not covered by a service contract. In order for you to receive support today you will need to purchase a service contract from your local partner / reseller.”

Such bullshit, I can buy a cheap DLink switch (I have a couple already) and have FREE software to manage them, spend a crap load on Cisco Switches, get no software to manage them. What a joke! I don’t see why a “service contract” isn’t provided with the switches, you pay an arm and a leg for these damn things!</end rant>

I tested with:
//10…
\10…
10…
None works.

Ideas ???

Hi,

I know this is an old thread, but I just discovered this exact error today. I can’t remember that it’s ever done this before, but can’t be sure. Using FOG 0.32.

Well I am okay with that. I am glad they did not purchase 2tb drives at this point then.

I am derailing this thread, I will start another.

I’m sure this information is flowing in the other forums. That said the instructions are:

Log in to the FOG Server. (Preferrably as root)

Open a terminal or console.

Type these commands
[code]cd /tftpboot/fog/kernel
mv bzImage bzImage.orig
wget --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage[/code]

That should get you my kernel.

I remarked files w7opt620 in /images and 00XXXX… in /images/dev I have created disappear when I try a reboot !
If it can help you …

Correct,

It may, but it may not as well. I don’t know for sure.

Well, sometimes that’s all it takes. It sounds to me like the tftp-hpa server may not have been running properly though.

Factory Image may not determine if the system is gpt or mbr. Make sure Uefi is disabled on the Client and make sure things are set on the legacy subset as much as you can. Again as I don’t have these systems I have guess where the problem is so if I’m wrong I’m sorry.

worked perfectly, thank you good sir!

What kernel are you using?

I’ve made one, but I don’t know if it works. Try mine though:

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]