Fog image size too big (500 GB/takes around 2hours to capture and deploy)
My fog server is in centOs vm on win 7 host. And the image i copy is from a physical PC win7-64 bit with 1TB hdd.
However, the memory used is around 100GB only.
I cant capture image with Single Disk - Resizable : Image Type but when i choose other option it takes really long time to capture and deploy image.
How to resize the image?
@azra What kind of hardware is this?? We see two disks in the output, same model, same size. Is this a RAID setup? Most probably a RAID 0 setup where two 500 GB disks are used to build a whole 1 TB disk chunk.
Interesting things in the picture:
... invalid ...?! Do you remember what the full message was?
- File system column is empty which means Linux is not able to detect the filesystem used within that partition. My guess is this is caused by the RAID setup. Possibly this is some kind of fancy software RAID controller where that adds a layer which Linux is not able to decrypt and therefore FOG is only able to capture it raw.
- Small partition seems to be at the beginning of the disk as Linux sees it
- Big partition is at the end and is full 1000 GB - different to what we saw in the Windows disk management screenshot
- No partitions in second disk -> pretty sure this is a RAID 0 setup with the partition table only being populated on the first disk
Would have been good if you’d told us this is not a normal 1 TB disk way earlier.
I am wondering if you ever deployed the image to another machine successfully?!
@azra The command not
parted -l(lower case l like lion!)
@Sebastian-Roth last week i try to capture and deploy fog using 500 SSD Win Server 2016 os. It works well
It only happens when im using RAIDED hard drive both 500GB.
@azra So what does
manage-bde -status C:show now on this system?
As well, please schedule a debug capture task (just as you would normally schedule a task but before you actually click “create task” there is a check box for debug). Boot up the machine and hit ENTER a couple times to get to the command prompt. Here run
parted -l, take a picture of the output and post here.
EDIT: Tom just had a great idea. Maybe it’s not
C:that captures as RAW anymore but one of the other partitions?! Please pay attention to the partition numbers (sda1, sda2, sda3) on the blue partclone window.
@azra Do you still see C: as 931 GB when Windows is booted??! This doesn’t make sense to me!!!
@azra Interesting, not sure why it still tries to capture in raw.
Though I do recommend moving the 300MB partition to be the first one (as that will give trouble with resizing), we should probably hold off on that until the first partition is seen as NTFS by partclone.
There’s something strange going on here, you C: drive is 900GB yet partclone only reports 500GB?
It also says /dev/sda1, though on windows 7 we’d expect /dev/sda1 to be a partition called “System Reserved”
Can you post a screenshot of disk management here?
@Sebastian-Roth i have tried multiple times to capture the image after decryption. I even encrypt the whole HD then wait for it to decrypt again yet, still the same issue happens. The Image file is still raw
This post is deleted!
@azra Ok, when it’s done with decryption you should be able to properly capture the image in FOG!
@Sebastian-Roth ok i can see the encryption percentage rising to 19%
manage-bde -off C:in that same admin command prompt and then
manage-bde -status C:again.
source master machine
here it is
@azra See in the blue partclone capture window we have “File system: raw”. This means partclone is not able to detect the filesystem on this partition. Please boot up your source master machine to Windows and run
manage-bde -status C:in an administrator command prompt. Post output here.