Capture is only 2.5MB
-
@KeithDib I want you to post the output of these commands.
ls -la /images/WindowsXPVMv1and
cat /images/WindowsXPVMv1/d1.partitionsHint: if you connect to the FOG server over ssh (by using putty), you can copy and paste commands easier.
-
-
@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.
-
Yeah tried chkdsk etc, also as I say it seems to work if a RAW image is extracted
-
would you recommend starting again and rebuild the Ubuntu and reinstall FOG?
-
No. I don’t think your installation is the problem. I’m siding with @george1421 that the disk this was captured from is having some kind of issue. Can you try capturing from another system?
-
I have tried from 2 different XP and 1 Win 7 machines, and the same machines seem to extract fine if i use RAW image
-
Have you "watched’ the screens during the capture process?
It seems incredibly odd that you are the only person reporting this problem. A TON of work went into 1.3.5 in regards to resizable images. That said 1.4.0-RC-1 found another issue in regards to aligning the disks, but I’m 99% sure this isn’t the problem you’re seeing either.
Can you watch the system during it’s capture process please? Maybe even capture it in a “debug” mode?
Try to see where, if any, there’s an error?
-
I will try again when I get home from the day job, but the actual imaging part of the process is over before you really get to see much on the screen, the progress bar seems to go from 1% to 100% instantly, then the process continues and the machine restarts/shutsdown depending on the settings etc
-
@KeithDib This is why I ask you to create the tasking in debug.
-
I will do that later today
-
I have ran a capture Debug, and although it looks on the capture machine to be running through the tests the server just sees the task as queued, and stays like that
