Capture is only 2.5MB
-
I should mention, originally I was using the preconfigured VM I downloaded, this works fine. But I want to test latest version
-
@KeithDib What preconfigured VM? FOG or your reference image? AFAIK, no one with the FOG Project has created a VM FOG server of 1.3.5 for download.
-
@george1421 said in Capture is only 2.5MB:
@KeithDib What preconfigured VM? FOG or your reference image? AFAIK, no one with the FOG Project has created a VM FOG server of 1.3.5 for download.
VM was old version not new. I built new one but as I say image extraction works but seems to gather no data
-
@KeithDib Ok just trying to set the scope here.
So you have a reference (source) image running on virtualbox too?
When you captured that image with FOG did you use single disk resizable?
On the fog server, if you look in /images/<image_name> directory do you see your disk image in there, if you are unsure post a screen shot of the following command
ls -la /images/<image_name>
just replace the <image_name> with the actual name of your image. -
Hi yes, set to capture as 'single disk, resizable ’ and yes when finished I can view the file and see the image in fog
On the xp machine I see it says successfully cloned
-
@KeithDib What I’m referring to is the actual files on the FOG server as viewed by the linux file system.
Also in that directory on the fog server. Can you also post the output of
cat d1.partitions
This file lists the disk structure of the source image. -
hi
yes i can see the images i have ectracted in the images folder
and i have 17.62 GB free space available on the dashboard
-
@KeithDib Can you proceed one step more and change to either one of the image files WindowsXPVMv1 or xptest and post the output of that
ls -la
command as well as the cat command on thed1.partitions
file?Its still not clear if
- Fog did not capture the source image correctly
- Fog did not deploy what it captured correctly
-
@george1421 said in Capture is only 2.5MB:
@KeithDib Can you proceed one step more and change to either one of the image files WindowsXPVMv1 or xptest and post the output of that
ls -la
command as well as the cat command on thed1.partitions
file?Its still not clear if
- Fog did not capture the source image correctly
- Fog did not deploy what it captured correctly
sorry, not sure what you want me to do here
and have not tried deployeing as the capture obviously is not working
-
@KeithDib I want you to post the output of these commands.
ls -la /images/WindowsXPVMv1
and
cat /images/WindowsXPVMv1/d1.partitions
Hint: if you connect to the FOG server over ssh (by using putty), you can copy and paste commands easier.
-
ahh right sorry, im not a Linux guy normaly
-
@KeithDib I would say your capture is bad (or something went wrong with the capture).
The file d1p1.img is the contents of the hard drive on the source system. This file is only 55KB in size. While FOG does compress this image, I suspect this is a bit small.
Does the source VM boot correctly (without FOG touching it)?
what was the original size of the hard disk on the source vm?
-
Yes, the VM’s, a couple XP and a Win 7 all bot and run fine, they range from about 4GB to about 6GB in used space on the systems
HDDs on the VMS are all 25GB
as i say i had an early FOG server, prebult VM and they are the same hosts i was testing on that system
-
So I need some help/clarity.
Your imaging processes work, and the systems boot just fine?
-
This post is deleted! -
The hosts im trying to image work fine. they boot and run as normal
the PXE boot fine to the FOG Server and looking at the screen the image extraction works but reaches 100% almost instantly
images show in FOG but are obvously too small, like no data inside them
-
if i use RAW it works, so the issue seems to be with ‘Single Disk - Resizable’
-
I still need clarification.
Capturing an image only captures “used” data. RAW copies a disk bit for bit.
Does the captured image not work? I don’t expect it would, but we don’t know.
doubt you have a full fledged OS sitting on 55kb of data.
-
Hi
No, the image extraction does not work, it’s alomost like an image with no content
I tried deploying it and it obviously has no OS etc then
-
@KeithDib Have you checked the master image to ensure the disk doesn’t have any defects. I can’t think of a reason why fog would stop imaging at such a small disk size unless its running into an error on the disk. You may have to watch the partclone process closely, if partclone runs into an error it will display the error very quickly then exit.
But I feel your issue is on image capture according to what we see for files that actually are stored in the fog server.