Image Not Capturing

[Tom Elliott]

@imagingmaster21 it’s aftee. When capturing the image is uploaded to /images/dev/<macaddressofmachinecapturing>

[imagingmaster21]

@tom-elliott Ok. So what would possibly cause it to get stuck at 94%? This image was a known good one that was pulled off another FOG Server. It is being put on a FOG Server that is on a laptop to image on the fly. I verified all the settings in the FOG interface are good and that the fog config files match setting wise, with the exception of different IPs.

[Tom Elliott]

@imagingmaster21 If I had to guess, off the top of my head? Disk Space.

You can verify this with:

df -h /images

[imagingmaster21]

@tom-elliott I have 196 GB available.

[imagingmaster21]

@Tom-Elliott The drive that I am capturing the image off of only has 30.6gb of used space.

[imagingmaster21]

@Tom-Elliott I restarted the server and it is still getting stuck at 97%.

[imagingmaster21]

@tom-elliott

Even at 97% nothing gets written to the images/dev directory the folder is blank.

[Tom Elliott]

@imagingmaster21 I’m not sure I understand the problem.

Can you please output the df -h /images command as well as run:
ls -lhRt /images/

[imagingmaster21]

@tom-elliott
Here you go:
https://dl2.pushbulletusercontent.com/4lm814kFRT4PvEEc2SX1RCiV71xqciF1/20180302_143432.jpg

So basically if I pull an image off our main FOG server and then capture it off our mobile FOG (built on a laptop for imaging on the fly) server it will capture up to 97% and will end up rebooting without stating any errors. If you look in FOG Task management it will show it still at 97% but the machine will reboot as if it was captured. If you look in the images directory and look at the folder for the image there is no files in there. I’ve tried clearing the task and restarting the task and still no luck. I also tried a different network switch.

[Tom Elliott]

The image is being stored to /images/dev/507b9d22485d

[imagingmaster21]

@tom-elliott
But nothing gets written to there, even when it gets stuck at 97% nothing is there.

[Tom Elliott]

@imagingmaster21 do you have more than one storage node?

[Tom Elliott]

Sorry, i’m trying to piece together the information, based on what I’m seeing the image is going to the “main FOG Server” rather than your current “mobile FOG server”

But I don’t know.

I need to know the image layout as well as where the image is actually going.

Doing our df and ls commands confirmed that you have enough space, but the fact that it’s not writing anything to the server is strange (leading me to think it’s writing to the main server you talked about).

[imagingmaster21]

@tom-elliott No only ones storage node.

[imagingmaster21]

@tom-elliott
Ok let me clarify. I have two servers main and mobile. I pulled a image called ‘Win10_Stu’ from main onto a machine. I’ve registered that machine on mobile and then captured the image with the only change to it being adding Chrome. I go onto mobile to capture it and the machine gets stuck at 97% on mobile when capturing if you look on task management status. But the machine reboots as if it captured fine with no errors.

The mobile FOG server is not connected in any way to the main FOG server they are not even on the same part of the network.

[Tom Elliott]

@imagingmaster21 and how is the image configured? I mean in the gui.

[imagingmaster21]

@tom-elliott
Right here is the settings for the image.
https://dl2.pushbulletusercontent.com/wKXMsj2AJ0Nl8YGYA6MFu7aQdvmBE2kA/camera_capture.jpg

[Tom Elliott]

@imagingmaster21 what is the output of cat /etc/exports?

[Sebastian Roth]

@imagingmaster21 Where exactly do you see the 94/97%? Is this in the web UI and does it jump from zero up to 94/97 straight? Or is this in the blue partclone screen on the client. If it’s on the client, what do you see in the web UI and if it’s in the web UI what do you see on the client?

[george1421]

@magingmaster21
Please setup a debug capture (schedule a capture again, but tick the debug option) and then PXE boot the target computer. This will drop you to a linux command prompt on the target computer after a few Enter key presses. From the FOS comand prompt key in the following cat /proc/cmdline. Finally please post the output here. That kernel command line will tell us where the captured images are going.