Not capturing image
-
@Dee Do you have an ability to capture a screenshot of when it is capturing? Do you see diskpart pulling the image? Is it failing to update the database which is one of the last steps? There should be a halt at the end if something failed and should wait 2 minutes before rebooting the machine. Do you see this at all?
-
Will run through the process again and see if I can take pictures.
-
@Dee said in Not capturing image:
Will run through the process again and see if I can take pictures.
This is the best to get a clear screen shot of the actual error. There are many things that could be at fault. Get a clear shot of any error messages on the target computer as its imaging. FOS should produce a stop screen with a reboot in 1 minute message. Get a clear shot of the error (close ups so we can read the error and the kernel parameters).
-
@Dee said in Not capturing image:
but never captures the image so it restarts the capturing process over and over.
Are you sure it does not capture at all? Do you see the blue partclone screens at all? How long does it take till the client reboots? Is it under a minute or more than that?
Probably best if you could take a video of the whole process. I am sure this will speed up finding the solution very much. Rest your camera / smartphone on a pile of books in front of the client screen so we get a steady picture and no head ache.
Possibly it’s just the finishing part (updating the database) that goes wrong?! We’ll see.
-
@quinniedid 
image url
Here are the errors I’m seeing.ACPI BIOS Error (bug) : Failure looking up [_SB>PCI0>XHC.RHUB.HS11] AE_NOT_FOUND 920180105/dswload-211)
ACPI Error: AE_NOT_fOUND, During name lookup/catalog (20180105/psobject-252)
ACPI Error: AE_NOT_fOUND, (SSDT:DELL_UMA) while loading table (20180105/tbxfload) -
@Dee 
-
@Dee Although you had those errors at the beginning it appears it found the disk to capture. Based on your most recent upload it might be that your server is out of disk space.
Would you please run this command on your server and report back?:
df -h -
@quinniedid I agree based on the very first error spewed by partclone (no space left on device).
@OP From the fog server console please key in the following command and posts the results
df -h -
@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? -
@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 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.
-
Looks like there are 12 part images but only 2 showing?
-
@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.
-
@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).
-
@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.
