I did get that error and, on a whim, checked permissions on the /images folder. As it turns out, only root had write permissions there. Once I corrected the permissions, all is well. Thanks for the post. Everyone here is great.

I tried that and it still didn’t fix it, very wierd I though

you may be able to chroot/fakeroot with the fog kernel and init.gz, but I am not experienced with that enough to tell you how.

looking at the ubuntu install, it only has language packs for IT, EN, ES, and ZH-HANS. There is a wiki article on [url]http://fogproject.org/wiki/index.php/How_to_translate_FOG[/url]

[quote=“chad-bisd, post: 5103, member: 18”]Download the kernel from the sourceforge page you linked above. Backup your current kernel and then copy this one to the /tftpboot/fog/kernel directory. Rename it bzImage and chown to fog:root.

Try to boot up one of the new laptops and see how it works for you.[/quote]

Thanks for your help. Updated kernel and it’s working, using a custom kernel from fellow user.

Have you tried getting a later kernel from the “Other Information” > “Kernel Updates” page?

Update on this,

If you modify your pxe boot menu passwords after doing this, it will overwrite /tftpboot/pxelinux.cfg/default which breaks the chainloading.

To fix it just replace

LABEL fog.local
[COLOR=#339966]localboot 0[/COLOR]
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive
If you are unsure, select this option.
ENDTEXT

with

LABEL fog.local
[COLOR=#339966]kernel chain.c32[/COLOR]
[COLOR=#339966]append hd0[/COLOR]
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive
If you are unsure, select this option.
ENDTEXT

In /tftpboot/pxelinux.cfg/default
To re-fix it.

🙂

You set the IP or FQDN of the FOG server when you install the FOG client. That is stored in a config file inside the FOG client install directory. I can’t remember the path off the top of my head but it’s something like C:\Program Files (x86)\FOG\etc\config.ini …or something like that.

Chad, sorry for the delayed response, and to answer your question yes I had. I ended up doing a DBAN wipe and fresh installing which resolved my issues.

Thanks for all your help,

Jeff

quote=“Gorosoki, post: 4981, member: 1248”]I deployed an image with the bzimage34 kernel and it finished after about 4 hours. The Windows 7 image didn’t deploy right. Window repair tried to fix it, but it couldn’t. Any suggestions?[/quote]

How do you have the rest of your image definition set up? Try setting the image type to “Multiple partiton - single disk(not resizable)”, even if it is only 1 partition.

Is this a clean install of Win 7 or an OEM install? I’d take one of the spares and install windows 7 from scratch (removing the 100 MB partition). No apps or patches. Just try to upload and deploy. If it works, you can be sure that FOG is working with your hardware and you can focus on your partition/filesystem.

Sounds like this is unlikely to help, but here is a 3.4.5 kernel. I used it the other day and it works fine on my systems:
[SIZE=2][COLOR=#0060e0][url]http://www.filedropper.com/bzimage34_1[/url][/COLOR][/SIZE]

astrouga

Thanks chad-bisd!

I was able to add manually. Thank you

Have you using a custom kernel for that system?

astrouga

I found the issue! We had a small managed switch between the fog server and the station that we had missed during the network change over. I through a fog vm on a test box and ran the standard install with dhcp server just to to see and I ran into the same issue, which pointed me to a network not server issue. As soon as I biased the switch, voila mounted the volume. I just imaged one of our high school labs this morning across the subent. Thank you for your help, I appreciate your responses.

Sorry, I got swamped then forgot. I just created this one using the 3.4.5 kernel. I haven’t tested it, so I can’t guarantee it will work. I’ll try to take a look later to make sure I didn’t miss anything. Let me know if it works at all.

[url]http://www.filedropper.com/bzimage34_1[/url]

astrouga

Oh yeah, I see it.
(ie - my first image includes “imageid=1” at the end of the URL)

If you look at the article I linked in post #3 and that doesn’t help, I suggest you try the Ubuntu help forums. I am not familiar with 12.04 yet, and this issue is not specific to Fog servers. Your chances of getting it resolved may be greatly enhanced at the ubuntu forums.