[fog] FOG 0.32

[LukeC]

Hi im new to Linux and FOG, i currently have FOG 0.32 server setup on ubuntu machine 10.4, however i have attempted to pull an image from a Dell vostro 3550 (win 7) but it fails with this error

"buffer i/o error on device sda3"

I have tried the kernal switch in the gui "acpi=off" but then it hangs at

Kernal_thread_help+0x6/0x10

 

Has any oen got any suggestions on how to troubleshoot or resolve this, i have read other forums which has suggested to update the kernal but i am unsure how to do this

 

Thanks

[teky]

From the look of the error it is something to do with the hard drive or a storage device attached to it. You can update the kernel through the settings menu on the web interface, I can't tell you where exactly as I haven't played with FOG in a while

[LukeC]

I have had a look at updating the Kernel through GUI but we are behind a proxy and it seems to hang.

[teky]

Have you put the proxy settings in the settings of FOG? Also try entering the settings in the network proxy settings on the box it is sat on.

If the OS is ubuntu have a look here: How to Configure Ubuntu desktop to use your proxy server*|*Ubuntu Geek

[LukeC]

Tried differenent Kernels now, still no luck. I have noticed when it fails it fails on Error read FPDMA queued, i hope this is a bit more of a clue.

[teky]

Having a quick look in FOG's wiki the dell vostro 3500 works with this kernel "Kernel - 2.6.39 Core FOG ID: 1045 Date: May 27, 2011 Version: 2.6.39 FOG Type: Core". Try that kernel and see if it works, or try and switch the Sata mode in BIOS to compatible and see if it creates the image then.

[JJonas]

Ive gone to the other information Kernel updates menu and it just sits there.

I can get updates with sudo apt-get update so I know my proxy is working.

 

What else could be wrong?

[LukeC]

SOLVED: It was a faulty HDD i ran dell diagnostics and turn out it was faulty. Tried another one and it worked fine.

[teky]

@LukeC good ok, I was going to ask if the laptop had a JMicron or Marvell sata controller as there are kernel issues with those controllers but glad your working.

@JJonas have you put the proxy settings in the FOG settings page on the GUI?

[dhicks]

I have tried the kernal switch in the gui "acpi=off" but then it hangs at

Kernal_thread_help+0x6/0x10

 

I have the exact same problem - I'm trying to boot the FOG client as a XenServer virtual machine, and it's hanging at the "kernal_thread_helper+0x6/0x10" line. I've tried a bunch of different kernels, most of which don't even get that far. I've also tried the SystemRescueCD kernel with the FOG client's init.gz, which actually booted but didn't recongnise any network interfaces (SystemRescueCD boots fine under XenServer normally). Anyone any ideas / suggestions? If I compile my own FOG kernel from the available sources, what bist do I need to add or leave out to make it boot?

[dhicks]

Ive gone to the other information Kernel updates menu and it just sits there.

 

You can simply download the kernel to your server with wget and copy it over the current live kernel in /tftpboot/fog/kernel/bzImage (taking a backup first, obviously).

[JJonas]

@JJonas have you put the proxy settings in the FOG settings page on the GUI?

 

I have now

 

Which one of these Kernels should I use with an DELL Optiplex 745 (Having the freeze when re-imaging problem)?

[teky]

Having a look on the FOG wiki: WorkingDevices - FOGProject Wiki the 745's should work fine, try the May 2011 one as I'm sure that kernel was working fine with our 745's before the switch to SCCM.

[dhicks]

it's hanging at the "kernal_thread_helper+0x6/0x10" line.

 

Well, after downloading the latest Linux kernel source, compiling and installing as the FOG client kernel, it's now hanging on the line "kernal_thread_helper+0x6/0xd". Progress, I guess...

[JJonas]

also having a similar problem with a PARS G31M machine. has a Gigabyte GA-G31M-ES2L motherboard. Weird thing is that will image from an older Fog server (0.29) but not the new one (0.32)

[teky]

One thing you could try is copy the init file from 0.29 over the init from 0.32. In the 0.30 update they re-writ the init file to bring in faster uploads, and a few people on here found that imaging on older machines slowed down a lot. This could be at least partly contributing to your issue Edited February 27, 2012 by teky

[JJonas]

if the path is tftpboot/fog/images, I already have the 0.29 init.gz in there

[teky]

That would be it. Have you tried playing with the image partition settings? I did have a few that wouldn't image unless the setting was multiple partition, single disk, or vise visa.

[JJonas]

Using Single Partition (NTFS Only Re-sizable) which is what worked for FOG 0.29

 

Now doing a restore from my 0.29 Server

 

going to copy the Kernel across from 0.29 to 0.32

 

and then upload it to my FOG 0.32 server

 

wondering if the init.gz/kernel changes had corrupted the image I took with 0.32