I have a Stupid question. Is there a newer version of the KitchenSink Kernel that has the latest drivers in it?

Paul, have you tried a different kernel? Sounds like the driver for your Lenovo might not be in the kernel you are using.

I am still having issues with my original problem.

When I try to upload an image with a new Acer V5-121 I get an error:
“Fatal Error: Disk device not found!”
I have also seen:
“Unable to copy /images/dev/mac to /images/mac”

It does not seem to be a permissions issue since I have been uploading and deploying images since this issue occurred.

Sorry for late answer but I was away on holiday.

[quote=“HIBY144, post: 12854, member: 6881”]under images\list all images(your image)\ ----- did you ever change the image file name? if you did then you need to change it back. i did this once and it sounds like the same problem i had. you can change the image name (the one at the top) but not the (image file) ex(/images/windows7)…[/quote]

Nope never, have tried creating new images and still it didn’t work.

[quote=“Jay_S_FogUser, post: 12862, member: 6972”]Why do you want to change?? You must be crazy. Fog has lot of issues. If you’re bored and want to spend time exploring something new, watch a movie or learn to play a new game etc, :)[/quote]

Why I want to change? GSS2.5 hasn’t been updated in years and FOG has potential and it seems to be working for many others.

[quote=“Jay_S_FogUser, post: 12863, member: 6972”]@Ethyr, if it matters at all. I do pity. But none of the stuff you’re attempting to do is supported by Fog. Please read through the forum and you will find out for sure :). Hope this helps.[/quote]

How is pulling an image from Windows 7 not supported?

You can register those machines manually, when you know their MACs. So there is no need to switch any kernels. Just put in the MAC, name the host (any name will be fine), and include the path to the working kernel.

The specified hostname is the name we specified for the computer. It is using our naming convention.

For other people who might have gunzip problems, I discovered that gunzip called /bin/bash but only sh was installed in the init file (see the link above to edit the init file)
simply open /usr/bin/gunzip with a text editor and replace the top “#!/bin/bash” with “#!/bin/sh”
save the file and pack the init file according to the above link

Most likely a smaller hard drive in the units that aren’t working.

I am having this same issue, has anyone figured this out yet? I have setup 3 FOG servers for various places and set up a couple of them multiple times as I was learning the system better. But the latest one is the first I did on a VM and it is the only one that is giving me this issue. The time is off by 4 hrs.

I have checked the time on the server and my local PC. I have even tried adjusting the time on both to see if it would make a difference and it didn’t change anything. It seems to be an error in the way jquery is checking the time. I have doe some research into this but I am not familiar enough with javascript to know where I should be looking.

Please if someone could point me in the right direction I wouldn’t mind looking for a solution if I could get a starting point beyond that it seems to be javascript.

[quote=“jmercer0530, post: 13057, member: 8098”]Hello,
I’m sure that there’s an answer for this somewhere on here but I haven’t been able to find it. But, I’ve been using FOG for over a month and absolutely love it, work in a school district and we are imaging close to 5000 machines. Anyways it’s working great with my Windows 7 machines, but on my XP machines I can’t get the hostname to change. I’ve syspreped the machine, created my answer file (named the computer some junk, knowing FOG would change it afterwards) but there must be a step I’m missing as far as prepping the XP machines opposed to the Windows 7 machines.
Thanks[/quote]
Actually upon deploying my images on the windows 7 machines it isn’t renaming as well! It was working fine the other day it would start up, then almost immediately reboot and update the hostname. Now it doesn’t reboot, I have uninstalled and reinstalled the client, I have stopped and restarted the service, I’m lost! I’m a total newbie to Fog/Linux, but I love the capabilities of the Server.

As I understand it, multicast is a form of broadcast which means that it will be sent to all nodes attached to that switch and on the same vlan.

What has an effect on speed is everything In between. Ie a cat 5 cable that snuck in there by accident, a FUBAR nic on one of the hosts etc etc.

IGMP allows the broadcast traffic to be directed towards those in the multicast session, rather than every device on the vlan.

After a switch upgrade, cabling and patching upgrade to make sure the lab was completely revamped, my multicast speed to 30 computers went from 500MiB/ min to 4.01GiB/Min.

The culprit was a dodgy patch on one of e hosts.

You can spend thousands on switching, but if you have a dodgy $5 patch, or a cat 5 cable in the mix etc, your multicast speeds will suffer.

Alright… I’ll do a little research and see how hard it is to move it to something a little faster

i personally use 100mb partition with os partition as small as possible and let sysprep extend the partition automatically, you should run into issues aslong as your os partition is smaller than your smallest disk.

I’ll have to experiment a bit more. I’ve had the machine start up several times remotely or started up + memtest but it won’t automatically start as part of an imaging task.

Yup, I got it. Thanks!

Sandi, I think that means that their task has been created by the auto-reg process. Did you associate an image to the auto-reg process? Then send it another image task?

[quote=“Blackout, post: 217, member: 1”]It looks like you might already be updated, or maybe in an in between state.

The Schema updater has been updated in 0.33 allowing it to continue if it encounters an error like this.

I have hacked the 0.32 schema updater to allow it to continue even if there are errors. It will then display all errors at the end.

Please replace ‘commons/schemaupdater/index.php’ with the attached file.[/quote]

this fix my problem thanks