Not capturing image
-
@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. -
@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.
-
@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 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.
-
@Sebastian-Roth
Removed more and it freed up some more space. -
@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.
-
@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:
-
@Sebastian-Roth Capturing is solved!!! Yeah you guys are the best!
-
@quinniedid Thanks for your help. You guys are the best!
