Image Not Capturing
-
@Tom-Elliott I restarted the server and it is still getting stuck at 97%.
-
Even at 97% nothing gets written to the images/dev directory the folder is blank.
-
@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/
-
@tom-elliott
Here you go:
https://dl2.pushbulletusercontent.com/4lm814kFRT4PvEEc2SX1RCiV71xqciF1/20180302_143432.jpgSo 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.
-
The image is being stored to
/images/dev/507b9d22485d
-
@tom-elliott
But nothing gets written to there, even when it gets stuck at 97% nothing is there. -
@imagingmaster21 do you have more than one storage node?
-
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).
-
@tom-elliott No only ones storage node.
-
@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.
-
@imagingmaster21 and how is the image configured? I mean in the gui.
-
@tom-elliott
Right here is the settings for the image.
https://dl2.pushbulletusercontent.com/wKXMsj2AJ0Nl8YGYA6MFu7aQdvmBE2kA/camera_capture.jpg -
@imagingmaster21 what is the output of
cat /etc/exports
? -
@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?
-
@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 followingcat /proc/cmdline
. Finally please post the output here. That kernel command line will tell us where the captured images are going. -
-
-
@sebastian-roth
I see the 94/97% on the Web UI, it does just jump right to it it goes through the process like it is working. The blue part clone does show up on the client and does act like it went through on the client but still shows as stuck on the Web UI. -
@imagingmaster21 said in Image Not Capturing:
The blue part clone does show up on the client and does act like it went through on the client …
What do you mean by “does act like”. Does it actually read data from the drive. I mean do you see the byte count go up at reasonable speed or does that jump as well? Sorry if this sounds stupid but I just haven’t got an idea yet. Maybe you can take a video of the client screen while this is going on. Possibly there is something that jumps at us.