Alright,

What errors is it giving you when you try to manually install mysql, if any?

The images are pigz’d as they’re uploaded. I don’t know of fog writing to /tmp, it’s to /tmp/pigz1 during the upload process, but that’s a pigz process which is writing to /images which is the mount of the nfs share.

If I’m wrong let me know, but you’re saying you’re having problems with the system actually picking up an IP Address when it goes thru PXE boot, or is it after this point that’s the problem?

It sounds like an issue with drivers. I’ve heard of some having success with different kernels. I have a very small kernel that might just fit the bill. It can be downloaded at: [url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]

I don’t know if it has all the drivers for your particular system, and if it doesn’t just let me know and I’ll build a specialized kernel for you. Just tell me what hardware (driver types) you need and I’ll make it happen.

On the server, how much memory do you have? If the loads are taking that long, it seems that something is eating the RAM and php is taking forever. Are you running php thru fcgi?

Try manually installing mysql with yum -y install mysql-server, it should install the package. Check that mysql is installed then, and you should find /var/lib/mysql folder. Another way to find out if it’s installed is to run:
chkconfig mysqld on; service mysqld start
Then, try your install. I’ll need to check the install folder for redhat to see that it’s pointing to the right package for mysql.

Though its slightly aged have you gotten this figured out? I suppose a little research could be done but I think you could do:
apt-get build-dep build root
But don’t quote me as I don’t use Debian based OS.
If you need help I’ll try where I can.

If you know what kernel driver you need for your USB nic I can build the kernel but I don’t know that pxe will actually run from it as that’s typically an onboard option. Though, again I don’t have one of those tablets either.

Lol if only. Glad to be of help.

As I now know what version of FOG you’re using I’ll take a look at the fog script that moves this file.

In the meantime, I’d manually move the directory on the Server so your stuff will work properly. Hopefully this works for you.

Has this happened often or just on this one system?

When entering your website, go to:

[url]http://<FOGIPADDRESS>/fog[/url]

Then you should be redirected to FOG Management

Make sure your configuration file in:
/var/www/fog/commons/config.php (UBUNTU BASED)
/var/www/html/fog/commons/config.php (REDHAT BASED)

Have your SQL information pointing to the right area. From the sounds of it though, you’re database hasn’t been created yet as you haven’t initialized yet because you haven’t been pointing to the right website.

This information would be found under FOG Configuration->FOG Settings

What I’m seeing is the ftp server is pointing at 192.168.86.105 But the fog storage server is at 192.168.86.12

Maybe I’m missing something?

The only thing I can think of is that it’s not communicating with the gateway properly.

It’s, seemingly, is passing information through a loop. If you have a crossover cable, try one computer connected directly to the FOG Server’s network interface and try doing it that way. This will let you know if it’s the DHCP & DNS issue. I’d recommend, though, instead of a 5 port switch, if you have a router such as a linksys or netgear, you shouldn’t see the problem you’re describing now.

I don’t know what else to check. I understand you’re trying to make the server the “router” in this case, but that loop around seems to be causing the issue itself. Does your fedora system have named/bind installed as well?

Found out that, the problem I’m seeing with the image upload process (as much as I can tell) is halting (resizable) because it’s referencing as kB. This in and of itself isn’t necessarily wrong, but when I try to manual create the disk partitions using parted, it tells me that 105905 (one byte behind part2start) is not valid for the partition. If I leave the end alone, it completes, but it isn’t the right size. It’s much smaller (part 1 that is) when it’s created using this particular method of parted. However, it successfully recreates the partition if I call the sectors: specifically, the sectors referenced are 206847 (partition one end) and 206848 is the start sector on the drive.

This method I can get rid of the need for the sleep commands, and all runs as expected. This is really weird to me, but it’s working as far as I can tell.

So I’ve, seemingly, made progress on getting the upload to work. It seems that my builds just ran thru way too quickly for pigz to keep up with writing to the NFS. The only issue is that my VM is extremely slow on the upload and download process. It only pushes speeds as high as 758 MiB/min and as slow as 100 MiB/min, but this sounds likely to just be a driver issue in my kernel.

I found that by adding a sleep command to the partimage save of the 2 partition section seems to work. I’m tinkering now with stepping up the intervals for the sleep timer to find out which one works best, at least for my setup. I don’t know if it’s simply because I am making an image off of a VM or if this would be a common issue seen by all. Though I don’t know that many people are using this particular setup.

My init.gz size is 9.7MB versus the 12-13 MB of the original one. I don’t know what I changed, but it’s probably the busybox config more than anything.

I’m taking down the tarball for now as it will probably be a couple of days until I get the sleep timer just right. Hopefully this is okay for everybody.

Sorry,

There were a few components missing from this. I didn’t build my own busybox configuration or use the one that FOG graciously provides for us. I’m trying to limit size a little, so hopefully after this run, fdisk and all the bobs and bits from the filesystem for partclone is all available. The file will still be named the same once uploaded.

Thanks all,

So here’s the buildroot that I use:

[url]https://mastacontrola.com/fogboot/buildroot-2013.08-rc2_FOG.tar.bz2[/url]

If you’re to wget the file, as always, use:
wget --no-check-certificate [url]http://mastacontrola.com/fogboot/buildroot-2013.08-rc2_FOG.tar.bz2[/url]

It’s rather large, I know, but it’s preconfigured with everything we need including the buildroot .config and it builds on Centos 6.4 with no issues. I haven’t built it on other OS’s. You will need the normal development information for building this thing, but a couple things that I needed to add were glibc-static and perl-ExtUtils-ParseXS and all dependencies needed there.

The file is about 300MB in size, and it will take a while to download as I’m only sporting 5MB upload speeds, sorry guys, but it’s better than nothing right?

Maybe others can look at what I’m doing wrong to find out the partitioning issues?

You do the normal building with:

make ARCH=i386

If you want to edit the packages to install, that’s up to you, but you will need to download it. When you setup for this you do the normal:
make ARCH=i386 menuconfig

Hopefully people find this useful.

Also, my buildroot actually builds partclone and partimage natively so I’ve modified the fog package and rather than using customize within the package directory, I just placed the FOG components in the package directory.

Thanks guys,

A quick search of the error comes up with a MS article:[url]http://support.microsoft.com/kb/2466753[/url]

This could be your setup as well. Make sure to try SP1 versus non sp1 win 7.

It almost sounds like a 64 bit vs. 32 bit problem. I don’t have experience with nComputing. But I’ve seen similar issues trying to install 64 bit win 7 on netbooks.