Not capturing image

[Dee]

@quinniedid yes I do see that. When I look closely it says "failed to complete capture (savePartition) Args Passed: /dev/sda 7 1 /images/f48e38d9d9cd all. Exit code 141. I looked at the server and it appears that /dev/mapper/libraryfog --vg-home is out of space. Not sure what to do now. The highlighted line. Can I save my new images somewhere else since I don’t know what I can safely delete?

[Sebastian Roth]

@Dee Yeah, from the pictures you posted I see that your images reside in /home/images/... and as it seems full you are running into that issue.

First you wanna make sure to clean up images that have only been uploaded half way. Run ls -al /home/images/dev/ and post here.

[Dee]

@quinniedid

[quinniedid]

@Dee Please run the commands that @Sebastian-Roth recommended. Also, please login to the web portal of FOG and taking a screen capture of all of your images so we can compare and see what we can remove to free up space.

[Dee]

@Sebastian-Roth

Looks like there are 12 part images but only 2 showing?

[Dee]

@Dee Some images were deleted from /home/images and I’m wondering if the system is looking for sda7 as in the image_0496 and sda7 doesn’t seem to exist.

[Sebastian Roth]

@Dee I’d suggest removing those half way uploaded images: rm -rf /home/images/dev/f48e38d9d9cd /home/images/dev/f48e38dc5f88 (be careful with this rm -rf command, I am not accountable for anything going wrong with deleting files from your server)

Then again check free disk space df -h, probably we’ll need to delete real images as well.

I’m wondering if the system is looking for sda7 as in the image_0496 and sda7 doesn’t seem to exist.

This is on the client being imaged. Just means your client has seven or possibly more partitions. Or maybe it’s just one primary (sda1) and three extended ones (sda5, sda6, sda7).

[Dee]

@Sebastian-Roth
I ran the command and it freed up a small amount of space. Now instead of 475 GB it’s 450GB. Then I removed some images that are no longer used via the web client and no decrease in size which surprised me.

[Tom Elliott]

@Dee You removed from the GUI or from the physical machine?

If you remove an image definition from the GUI, it doesn’t remove the actual image data automatically. (Imagine if it did and you didn’t intend to lose the actual data the makes the image?)

You would need to go into the FOG Server and physically delete the files you no longer need. This is intentional.

[Sebastian Roth]

@Dee said:

Then I removed some images that are no longer used via the web client and no decrease in size which surprised me.

So you can now delete those images via command line: rm -rf /home/images/IMAGENAME (just put in the name of the image(s) removed in the web UI - again, be careful with this rm -rf command, I am not accountable for anything going wrong with deleting files from your server)

[Dee]

@quinniedid 0_1542217823881_screen shot of all images.pdf

[quinniedid]

@Dee Remove the images that are no longer showing associated in the UI. When creating the images you have to specify the name of the image folder containing the image files. I would go to your image directory and remove images that are not associated. Just follow what Sebastian recommended.

[Dee]

@Sebastian-Roth
Removed more and it freed up some more space.

[Sebastian Roth]

@Dee That’s looking better now. Give it a try capturing a new image again now. Possibly 75 GB free space should be enough - depending on how much data you have on the PC you want to capture.

Please let us know if your initial capture issue is solved now.

[quinniedid]

@Dee If hard disk space is a concern I would highly recommend enabling compression on the image setup page. We have ours maxed out to 22. It takes more time to capture the image but it is huge savings for us.

Here is an example:

[Dee]

@Sebastian-Roth Capturing is solved!!! Yeah you guys are the best!

[Dee]

@quinniedid Thanks for your help. You guys are the best!