Have you tried running a quick inventory on the 9 hosts that did not show up? Running a quick inventory or doing a “Full host integration” will load the host into inventory. Quick joins will not.

This isn’t a kernel issue at all, as the Services (GreenFOG, TaskReboot, etc…) don’t do anything with the kernel/linux layer of the FOG system.

The only one that, might possibly, have anything to do with the kernel is the Task scheduling shutdown, but even that I’d be hard pressed to believe.

I think this issue is more related to the way the shutdown command for the task cycle is read. I don’t know much about 0.32’s init.gz file but it may be trying to see shutdown as either 0 or 1, but the shutdown sent when creating a task is set as shutdown=on. I could be wrong and will take a look for you.

Delete the 01-xx-xx-xx-xx-xx-xx file from the /tftpboot/pxelinux.cfg/ folder. The x’s will be replaced with that system’s MAC adddress.

definately, that’s the easy setup if you can tell dhcp to just point to a different TFTP server for the PXE part.

try setting the image type to “windows xp”.

Dual boot upload has worked in the past.

If this fails, use the RAW disk type.

Agreed, worse comes to worse, also check the apache error logs during startup as it is referencing php files.

It is a good idea to create master images on “tiny” drives and have either a script resize the final (or OOBE in windows do it). I always create my golden images in a VM with jsust enough HDD space to do what I want (I expand the drive if the image gets bigger). That way you can use whatever size final drive you like.

You can always script extra partition creation too. I have a script that resizes and creates an extra partition and moves a folder into that partition for my W7 images. That way I can use smaller drives as appropriate.

It seems my old kk20 account was deleted for being a “spammer”. Great as I had quite a few fixes posted under that username (from when I installed fog) and had never spammed in my life… oh well.

anyway I am revisiting this as I have moved my FOG to a new server and came up with the same error, luckily someone had “quoted” my original fix so I could look in the post_stage2.php file for changes I made (and I had commented them! yey!). Here is the change I made to post_stage2.php

this line:

[B]$dest = $noderoot . $_GET[“to”];[/B]

I changed to

[B] $dest = “/raid6/data/FOG/” . $_GET[“to”];[/B]

It seemed that the $noderoot was somehow incorrect for me. No idea why as it was only the final FTP that failed for me. Anyway, after hard coding my FTP location (not ideal but I needed a quick fix rather than a debug) this works fine for me and has done for years.

for information, /raid6/data/FOG is my listed NFS share in FOG (which also has FTP share enabled in openfiler). I have no idea why the $noderoot does not work yet everything else does. Anyway, that single change in post_stage2.php fixed my final FTP issue (so no more manual image moving necessary!)

Well, went back to the drawing board. Created a new VirtualBox server running Ubuntu 10.04 and installed Fog 0.32. Having run the install again, I realized that I had to have deviated from the standard installation instructions at least twice over username/password instances. Noting this, I did a trial run and was able to successfully do everything PXE-related (Memtest, Register, etc.). I followed the instructions for Uploading an image and was able to do so on the 1st try.

With this success in hand, I went back to the physical server and removed Fog following the instructions here:
[url]http://www.fogproject.org/wiki/index.php/Uninstall_FOG[/url]

Reinstalled Fog on physical server and voila! Happy image uploading. 🙂

well, without LVM, no, if you have a separate dir… it’s gonna get annoying for NFS… and using a storage node is probably not a good idea.
But copying data over to the LV, then umounting /images, remounting the LV on /images, then lvextending, that’s less than a minute of downtime if done properly… 🙂

I can now register and uploading an image seems to be working but it’s going very slowly. After about an hour, it’s only 5% uploaded where normally we would be close to half way.

When will .33 be available for upgrade?

Yep,

I’ll bet it’s in GPT as I stated before.

sorted it thanks guys, Stopped the WDS service for a starting. Then realised I had the DNS server setting in fog set incorrectly. Rebuilt Linux and reinstalled Fog correctly (

This is a known issue with tftp-hpa service and Ubuntu 12.04.

Horray! It works perfect.

Thanks!

Found some software on the master for making recovery discs. Sorry for not looking for this sooner, I’m looking over the mountain instead of at the base.

If these work, I may remake the image quickly on the second to have an image.
Still wondering what Panasonic has on these causing fog to think the File Table is corrupt.

Thank you Tom.

Also, almost relevant for how I feel:
Quote from Simpsons, Ned Flander’s Mother:
[QUOTE]You gotta help us, Doc. We’ve tried nothin’ and we’re all out of ideas.[/QUOTE]

That is correct Tom. Will try redownloading

Alright, now I have my own switch A Netgear prosafe GS108E. I’m hooked up to it, but when I try now to start the isc-dhcp-server, it gives me the error:
[CODE]Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. … failed!
failed![/CODE]
And in /var/log/syslog I have
[CODE]No subnet declaration for wlan0 (10.247.57.50).
** Ignoring requests on wlan0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface wlan0 is attached. **[/CODE]
I don’t want wlan0 at all. I want it to use eth0.
In my dhcpd.conf file, I have:
[CODE]GNU nano 2.2.6 File: dhcpd.conf

DHCP Server Configuration file. see /usr/share/doc/dhcp*/dhcpd.conf.sample This file was created by FOG

use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 10.126.6.26;
subnet 10.126.6.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.126.6.10 10.126.6.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 10.98.1.1;
option routers 10.126.0.1;
filename “pxelinux.0”;
}[/CODE]
I’m not quite sure what to do from here.