It had stopped there, upgrading the BIOS helped, but now it gets to 99% and has an error stating
“unable to move /images/dev/f04da2867522.000 to /images/HSLMCC (our image name)” any ideas would be great!

Thank you!

been a while since I asked this question, but I just thought i would let everyone know that cloning a blank computer with no OS works perfectly, just get the MAC from the BIOS and make sure that the imaged computer has the client to make future cloning easy and it should work without flaw. I am continually impressed by this program!!

Thank you Kevin. Can you help me

Found a solution! I needed to create a second partition, not just have one partition with everything loaded on it (Boot,Primary, etc…) then it deployed just fine.

That did it, thanks! Once I switched to Legacy Mode, made my image from that and sent it to a computer on Legacy Mode, everything worked perfectly.

Thanks for the help!

Ok got it, recompiled the kernel bzImage with highmem64G instead of highmem4G option. Now it works fine. I can read the full amount of ram. Tnx for the fast response.

Solved, it was a Proxy problem. They have recently changed the Proxy settings in my enterprise and there may be some kind of problem. If I disable the Proxy configuration it works fine.

[quote=“Martin T, post: 10917, member: 3420”]Thank you Fernando Gietz and chad-bisd for input.

I have rebuilt the complete fog server with Ubuntu 12.04.2 LTS 64bit and fog .32 and I am back to the same error that I started with (clamaverror.jpg Monday 2:41PM). I did this because I have tried so many changes that I wanted to make sure that I got back to a safe starting point. So a few questions, if you please.
Do I go back and make all the changes 1-9, yesterday at 11:34 AM or try the rebuild/resize of init.gz?[B] - both[/B]
The server does have 0.97.6 and I see the client does say 0.97.1. Are the definitions truly incompatible?[B] - Fernando Gietz[/B]
Where is the FOG_PXE_IMAGE_DNSADDRESS at? [B]- Fernando Gietz[/B]
I can only find main, daily, and bytecode CVD files. No CLD files. Do I just make the symbolic links to what I have? [B]- chad-bisd[/B]
I have asked other questions above but let’s see how this goes.
I am willing to try almost anything and can rebuild the server when I know exactly the steps to make it work. Hopefully I can create a complete posting that outlines the exact steps to make this work for everyone who wants this task to work correctly.[/quote]

Sorry for answer so late.

[I]Where is the FOG_PXE_IMAGE_DNSADDRESS at?[/I]
In webui: About > FOG settings > TFTP Server

[I]The server does have 0.97.6 and I see the client does say 0.97.1. Are the definitions truly incompatible?[/I]
I’m not claAV expert 🙂 but the capture says that [I]Not supported database files founf in /usr/share/clamav. [/I]Seems the database files are incompatibles. This problem/issue desappears if you upgrade the clamAV version[I] to 0.97.6[/I]

I have seen the fog.av script and you don’t must resize the init.gz (sorry, but i’m sure that you have learn a lot of 🙂 ). The database files from the server are copied in /usr/share/clamav. This folder is a ramdisk:

[CODE]mount -t tmpfs none /usr/share/clamav/ -o size=50m;[/CODE]

This ramdisk have 50M size. This size would be little[I], why? [/I]the reason is the database files size grown more and more, daily. For example, in my server those files:

[CODE]-rw-r–r-- 1 clam clam 302K feb 15 03:37 bytecode.cld
-rw-r–r-- 1 clam clam 0 feb 26 20:25 clamd.sock
-rw-r–r-- 1 clam clam 55M mar 12 03:10 daily.cld
-rw-r–r-- 1 clam clam 30M mar 11 14:14 main.cvd
-rw-r–r-- 1 clam clam 572 mar 12 03:10 mirrors.dat[/CODE]

86 MB, and daily increases his size 😞 The size of the ramdisk would be dinamic.

Allright, copying from one computer to another didn’t work, however I tried another approach… we have a disk duplicator from startech, so I plugged in the 80GB into the source and 2TB into destination and let it copy. It made an identical copy successfully, however the partition sizes where the same. So I used GParted to grow the sda1 to ~2TB. (with 3GB for swap) everything booted and is working fine.

I have now jumped from 98% usage down to 8% usage 🙂

Now the only issue this brings up is how to backup fog images if copying them somewhere and reviving them doesn’t work…

Thinking about it more, this isn’t an issue with FOG, at this point of the imaging process, this is an error based on Partimage (if it is actually an error). I’m sure they don’t want you to stop in the middle of an upload/download so you don’t have a corrupt image. FOG may be getting switched to Partclone down the road anyways. So unfortunately, this I think, will be just how it’s going to be.

Hi,

The FOG server has been reinstalled (Ubuntu 12.04 LTS Server 64 bits) without services (LAMP, OpenSSH, etc.), and after that I have installed FOG. The problem is solved.
Now I can’t upload snapins, but I’m going to start a new thread.

Thank you for your help.

Nice, looks like it’s pushing the image back. I got a little worried there for a minute. Right before it started, it said something about an invalid command, but it went away quick and started to work.

I’m doing this and not getting a domain join. Any suggestions?
[IMG]http://i.imgur.com/qlmyESI.jpg[/IMG][IMG]http://i.imgur.com/FhgKBtM.jpg[/IMG]
In the pic above that’s:
DOMAIN.local &
USERNAME

yes it was ther /images/var

i think a win xp image was right around 25 gig