Again, I would still be checking the permissions of the folder, because once we get the kernel working you’re going to need the permissions set properly to upload your image.

Also I forgot to ask, what Operating System are you imaging with?

The Kitchen Sink kernel includes extra drivers that may be necessary for your machine hardware, the stock kernel doesn’t include all of the extra drivers as it adds to the load time of the pxe boot menu and such. But when you are stuck it’s a great starting point.

It’s good that you are using the default folder, and that you are on a fresh server, if these applications do not work it would be a good idea to re-configure your fog server, there may be a setting somewhere that got nerfed.

Are the ONLY pieces of hardware you are working with the HP100b and the Optiplex? Do you have other hardware you can try?

The HP problem is a driver problem,
The Optiplex problem is a permissions problem.

There is an AMAZING guide written by Ozzy and posted in tutorials, it explains the process of creating a custom kernel. ->[url]http://fogproject.org/forum/threads/request-for-kernel-compiling-info-please-read.4045/[/url]

[B]How to Build a Custom Kernel for FOG Server using Ubuntu 12.04[/B]

First, make sure you have [B]G++ (GNU C++ compiler) and QT4 (Qt 4 Designer) [/B]installed through the Ubuntu software center.

Next, pick a Linux kernel you want to use to compile the kernel at [URL=‘http://www.kernel.org/’]www.kernel.org[/URL]. (Used linux-3.10-rc2.tar.xz for this document;[url]https://www.kernel.org/pub/linux/kernel/v3.x/testing/linux-3.10-rc2.tar.xz[/url]) Download the file to the ‘home/user/Downloads/’ directory. (default)

Then, download the Fog installation package installer. (Current version 0.32;[url]http://sourceforge.net/projects/freeghost/files/FOG/fog_0.32/fog_0.32.tar.gz/download[/url]) Make sure to download to the ‘home/user/Downloads/’ directory. (default)

Now we will extract the files to their proper locations.

First, extract the FOG installer to the download folder. (see below for command)
[B]sudo [/B][B][FONT=Tahoma]tar -xvf /home/user/Downloads/fog_0.32.tar.gz[/FONT][/B]

Then, we will want to extract the kernel to the ‘/usr/src/kernels/’ directory. If the directory does not exist create it. You will also need to copy the tar.gz file to the kernels directory in order to extract properly. (see below for commands)
[B]sudo mkdir /usr/src/kernels/[/B]
[B]sudo cp /home/user/Downloads/linux-3.10-rc2.tar.xz /usr/src/kernels/[/B]
[B]cd /usr/src/kernels/[/B]
[B]sudo tar –xvf linux-3.10-rc2.tar.xz[/B]

Now we can either use CORE or Kitchen Sink to create the kernel.

To use [B]Core[/B] use the following command:
[B]sudo cp [/B][B][FONT=Tahoma]/home/username/Downloads/fog_0.32/kernel/core.config /usr/src/kernels/linux-3.10-rc2/.config[/FONT][/B]

To use [B]Kitchen Sink[/B] use the following command:
[B]sudo cp [/B][B][FONT=Tahoma]/home/username/Downloads/fog_0.32/kernel/kitchensink.config /usr/src/kernels/linux-3.10-rc2/.config[/FONT][/B]

Once the .config file is copied to /usr/src/kernels/ you can now run the make xconfig command.
[B]cd /usr/src/kernels/linux-3.10-rc2[/B]
[B]sudo make xconfig[/B]

Now the kernel editor should pop-up after a few seconds. Here is where you will locate and select/deselect drivers you want to load to your custom kernel. (see screenshot for example)

[IMG]http://i.imgur.com/a49MUxh.jpg?1[/IMG]

Once you are done with your selections just [B]save and quit[/B].

Now you have to run one final command to write the kernel file.

For 64-bit systems:
[B][FONT=Tahoma]sudo make ARCH=i386 bzImage[/FONT][/B]

[FONT=Tahoma]For 32-bit systems:[/FONT]
[B][FONT=Tahoma]sudo make bzImage[/FONT][/B]

[FONT=Tahoma]You may get a few prompts during the compile, I just used default options (enter). It will take a while (10-30 minutes) to compile the kernel so be patient.[/FONT]

[FONT=Tahoma]Now that you have created a custom kernel you will need to copy/cut the file to your FOG server.[/FONT]
[FONT=Tahoma]Go to the [B]/usr/src/kernels/linux-3.10-rc2/arch/x86/boot/[/B] directory to find the new [B]bzImage[/B] file you created. That is the file you need to import to your FOG server kernels directory in order to use it. (You can rename it or use the new kernel as the default kernel for FOG to use if you leave the name bzImage)[/FONT]

[FONT=Tahoma]The directory where you should paste the new kernel is /tftpboot/fog/kernel/ on the FOG server.[/FONT]

[FONT=Tahoma]Make sure you assign the custom kernel to the proper host in the FOG management GUI and then you should be able to Upload/Deploy. You might need to add the host manually; you’ll just need the MAC address of the NIC for the host.[/FONT]

[B][I][FONT=Tahoma]Written by Ozzy[/FONT][/I][/B]

Well a search and a quick look reveals the solution to the problem in the first picture.

I would try the kitchen sink kernel and see if that helps, it may be a driver issue, you should consider writing your own custom kernel with your specific drivers included.

As per the posting [url]http://fogproject.org/forum/threads/pxe-boot-error-no-chip.4466/#post-13138[/url]

Jason recommends a Kitchen Sink kernel to solve the problem.

I would still recommend taking a look at your permission settings, without the correct settings it won’t matter if you can load the pxe boot screen or not. Without the proper permissions on the folders and files you WILL NOT be able to save them.

[SIZE=4]You also never answered my questions.[/SIZE]

[SIZE=4][B]Is this a new fog server? [/B][/SIZE]
[SIZE=4][B]Have you tried other hardware? [/B][/SIZE]
[SIZE=4][B]Does the other hardware work with fog? [/B][/SIZE]
[SIZE=4][B]Can you try another machine and see if it is driver specific? again if it is you will need a custom kernel.[/B][/SIZE]

[SIZE=4][B]Are you saving to the /images folder or are you saving your images on another server or NAS?[/B][/SIZE]

[SIZE=4][B]If this is NOT a new server are any other hardware affected? [/B][/SIZE]
[SIZE=4][B]When did the problem first arise?[/B][/SIZE]

[SIZE=3]I’d love to help you but I’m not going to try to exhume information from you or try to hold your hand, if you want help you need to pay attention and cooperate.[/SIZE]

The first error you posted shouldn’t be causing you any problems, what it does first is check the bios revision and such so it can get an idea of the manufacturer and the hardware. It’s not desperately important for all of these to succeed, mainly only the video card drivers, nic, and the hard drive have to be detected.

The second image you posted explains exactly what the problem is… You do not have permission to write to the folder.

You will want to check your permission settings for the folder /images/dev/
browse to the folder, right mouse click then select permissions.
Make sure that the root user is set as the owner and that it has create and delete capabilities, and that the root group has create and delete capabilities.

[B]1.)[/B] Is this a fresh install? If so and no images are on the server, just nuke it and try to install again, if not, does this occur on all hardware, or just a specific model? I’m going to say the issue is with the folder permissions and not the hardware for now.

[B]2.)[/B] Are you saving your images to the /images/dev/ folder or are you saving to a NAS?

This information below explains how to change your save space. Don’t follow it to a T, just try to remove your older folder and create a new one with the .mntcheck if the steps above do not resolve the issue,.

[INDENT=1]Ok so for future individuals, here’s my little guide during installation[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Adding a NFS share[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]First, get rid of the old /images directory. Move it somewhere safe[/INDENT]
[INDENT=1][B]sudo mv /images /imagesold[/B][/INDENT]
[INDENT=1][B]sudo mkdir /images[/B][/INDENT]
[INDENT=1][B]sudo chown –R fog:root /images[/B][/INDENT]
[INDENT=1][B]sudo chmod –R 777 /images[/B][/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Next, let’s edit your fstab[/INDENT]
[INDENT=1][B]sudo nano /etc/fstab[/B][/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Add the line in your fstab for the nfs drive[/INDENT]
[INDENT=1][B]IPADDRESS:/sharename /images nfs defaults 0 0[/B][/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Mount the drive[/INDENT]
[INDENT=1][B]sudo mount -a[/B][/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Then reapply the permissions to the folder now that the drive is mounted. Create the dev folder and .mntcheck folders[/INDENT]
[INDENT=1][B]sudo mkdir /images/dev[/B][/INDENT]
[INDENT=1][B]sudo touch /images/dev/.mntcheck[/B][/INDENT]
[INDENT=1][B]sudo touch /images/.mntcheck[/B][/INDENT]
[INDENT=1][FONT=arial][SIZE=3][B]sudo chown –R fog:root /images[/B][/SIZE][/FONT][/INDENT]
[INDENT=1][SIZE=3][FONT=arial][B]sudo chmod –R 755 /images[/B][/FONT][/SIZE][/INDENT]
[INDENT=1][SIZE=3][FONT=arial][B]sudo chmod –R 777 /images/dev[/B][/FONT][/SIZE][/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Then login to the FOG panel, go to storage management, click Add Storage Node and then use these values[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Storage Node Name: Whatever you want[/INDENT]
[INDENT=1]Storage Node Description: Whatever you want[/INDENT]
[INDENT=1]IP Address: IP Address of your NFS share. JUST THE IP ADDRESS[/INDENT]
[INDENT=1]Max Clients: Whatever you want, I generally stick 10 in there[/INDENT]
[INDENT=1]Is Master Node: Yes. Note - if you tick this, it’ll wipe images you’ve already created[/INDENT]
[INDENT=1]Storage group: Default[/INDENT]
[INDENT=1]Image location: Enter the folder on your NAS drive that your images are stored in[/INDENT]
[INDENT=1]Is enabled: Tick it[/INDENT]
[INDENT=1]Management Username: the username you use to login to the FOG control panel[/INDENT]
[INDENT=1]Management Password: the password you use to login to the FOG control panel[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Click update, and you’re done![/INDENT]

icarus - [url]http://fogproject.org/forum/threads/error-mounting-filesystem-images-dev-on-an-nfs.4205/[/url]

wow, sounds like you’re having a tough time

Building a custom kernel is not hard to do, it doesn’t take too long to do either. Ozzy made a nice write up on building a custom kernel, it’s in the second post of the thread -> [url]http://fogproject.org/forum/threads/request-for-kernel-compiling-info-please-read.4045/[/url]

Hopefully this can make some headway, good luck

I would say you are definitely on the right track, it appears to be a Video card driver issue

Check the bios settings and adjust the AHCPI settings and try again.

What type of a hard drive is included in these units? Check BIOS settings first, it obviously has a drive but fog isn’t seeing it, sometimes adjusting the BIOS settings will help. If not, you can try the Kitchen Sink kernel, or build your own with the hardware drivers included.

For something like this you will more than likely need to compile a kernel to accept the controller hardware.

You can start by using the kitchen sink kernel and if that still doesn’t work then try compiling your own. It’s really simple to do and it doesn’t take too terribly long, maybe about 10-15 min.

check the 2nd post in this thread -> [url]http://fogproject.org/forum/threads/request-for-kernel-compiling-info-please-read.4045/[/url]

Your grasp on the broadcast system sounds right to me, I don’t honestly know much about that yet. But from your explanation that is the way that I perceived it, and turning off the devices or disconnecting them form the network had positive results.

I know that during a unicast the image is sent to the host and then decompressed. During a multicast the image is decompressed at the server and sent out to the hosts, so naturally it will be a bit slower.

The way you described imaging your two hosts, I imaged my labs this way. Our network here is in DIRE need of a revamp and I got the best speeds by putting the server on a cart and allowing the DHCP to issues addresses then disconnecting and imaging this way. It still only took ~ 40 min.

As for the ceiling on the graph, I can’t really answer that question, I didn’t pay much attention. I know for a fact that all my equipment is Cat6 and 1gb cards and I get some really good speed on 30-40 hosts at a time. I’ve never really paid much attention to the traffic

Check to see what kind of network appliances are set up, like printers and scanners and such. I’ve found leaving these plugged in while trying to multicast my lab makes my speed increase.

I’ve heard that .33 is a major re-write of code, so good things come to those who wait.

I too am anxious to see what new things 0.33 is going to offer, but this is an opensource project, and you are welcome to tweak things to your liking. I am a software engineer, I know development takes a long time. I think everyone should learn a programming language so you can have a passion for everything you use and an understanding of how to overcome obstacles.

There is still a lot of activity on these forums, I expect development to continue for quite some time. I’m sure if you’d like to donate the devs would really appreciate it!

In my experience, it is best to let the windows create the 100 mb partition and then use the multi partition all disks method to upload my images.

I’ve not tried to make a single partition yet, good luck, I’ll be checking here for notes.

Check to see what kind of other devices are plugged into the switches. I.E. Printers and turn them off, and try to multicast again. I have HORRIBLE speeds if I leave some of the MFD devices turned on while casting.

I see, I use to image that way as well. Just make sure to sysprep before uploading to fog, you shouldn’t have any problems releasing the CMID information for a new client. Each Windows OS has a built in number of “re-arms” for imaging anyway.

I’m uploading a raw image as I type this and so far it has taken 11 min and 14 min remain. Image size 23.24 gb. uploading at ~920 mib/min.

I’d look into a custom kernel or using the “Kitchen Sink” kernel. Have you tried deploying? Does it also take just as long to deploy as upload?

[quote=“The Dealman, post: 12935, member: 53”]When you do a upload or push what does it say for you file system type? mine says raw & it take 9 to 12 hours per computer like this[/quote]

When I set up a Windows 8 Virtual box, for imaging, and I am ready to upload my image, I always choose Windows 7 as the OS type, Multiple Partition, All disks (Non-Resizable) as the type, and I NEVER run fogprep, only sysprep. This will cause it to upload as yes a RAW format which takes a little longer to upload, but it shouldn’t take THAT long to upload.

So far is seems that your set up is fine.

When you said you are pushing an image are you pushing a virtual image? It’s really recommended you use Virtual Box and set your image up for deployment there. After sysprep upload to your FOG server.

Have you used the machines you are currently working with before? Have you imaged them with FOG before?
the reason I ask is because if the drivers aren’t available in the Kernel when it boots then you can get some pretty shotty speeds.

I built my own custom kernel including the drivers necessary and I can upload a ~30gb image in under 20 minutes.

something else to consider, if you have jetdirect cards or any printers on the same network as the machines imaging, un plug the printer until you are done casting, I don’t know if the cards are causing a loop back or what, but I notice a SUBSTANTIAL increase in time (13+ hours) when I leave those damn printers on!

I can’t answer much about the CMID, as I didn’t even activate it was more or less a test to see if the hardware could handle the OS and if the software we were using could handle the OS. The image booted fine, and the software worked well, boss man just decided to stick with 7 this year.

Everything is still in development, Everyone that works on this project does it in their free time.

0.33 is a serious re-write of code so it is taking some time to complete.

I can assure the project is still in development, the developers just have lives

Try to register your host again, look for what the last line displayed is.

After you attempt to register the host, check the log on the server in /var/log/daemon.log

Don’t post the whole thing just what is most recent and include it in code brackets.

Next check /var/log/syslog, again only paste the most recent concurrent event, if you attempted register at 11:35 paste that section for 11:35.

ooo I second this notion!

So you are successful in getting some of your units to speak to and load the fog splash screen, but a particular model of Toshiba minis will not connect?

Where does it fail? Do you receive a PXE error code when it attempts to pull the information, or is it skipping the PXE load all together?

Some machines have to have a specific driver built into the kernel before it can communicate properly. It doesn’t take much time and it is EXTREMELY easy to do. There is a wonderful walkthrough I will look for while I wait for you to answer my questions.

If I am understanding this correctly so far, your Toshiba Mini laptops are not receiving the TFTPboot information and are not displaying the fog splash screen therefore you are unable to register or image them and it continues to boot off the hard drive.

One other quick question. You said you had an Ubuntu server, what Ubuntu version are you using? 10.04? 11.04? 12.10?
Have there been any reboots of the server? there are some versions of Linux that have problems restarting some of the services after a reboot, we’ll cover that if necessary.

Please refrain from posting similar questions in multiple forums, this makes it hard for users to find answers when using the search system, and it makes it harder on those of us dedicating our time to try to help others.
Someone will be happy to assist you when someone with the expertise becomes available.

similar post -> [url]http://fogproject.org/forum/threads/is-flog-able-to-clone-windows-server-2008-with-raid-1-configuration.4470/#post-12886[/url]