Incomplete Image Caputer
-
Good day Fog community
I have an image that is not capturing to 100%, it stops and 99% and stays in the active task list. The machine reboots and goes into a BSOD loop.
When checking the image size (size on client), it tells me its 500mb - this seems to me that its the System reserve partition ( its first in the partition table)
The image itself on Fog is set to capture the whole disk “partition = everything”, the "image type = single disk- resizeable.
The same thing happens whether capturing from a VM or a physical machine.
Before closing the image, a chkdsk /f is run and machine rebooted successfully.
Then a .bat file that links to an .xml file that runs specific closure commands ( this process works perfectly for other images)
We have 2 storage nodes - both with more than enough space to hold the image. The above mentioned happens when changing the storage location “image path”
What or where can I start looking for a solution to capture the image to completion (100%) and stop the machine from BSOD boot looping.
Please let me know if you; the community, needs some screenshots or more info, happy to share!
-
@sonic136 There is a fair amount of questions coming up from our side. Let’s start with some basics:
- Which version of FOG do you run?
- Which version of the kernel and FOS inits do you use?
- How are the storage nodes configured exactly (people use this term in different ways)? Please take pictures of your storage node settings in the web UI and post that here.
I have an image that is not capturing to 100%, it stops and 99% and stays in the active task list.
What do you mean by it stops at 99%? What do you actually see on the screen? It kind of sounds like you have not watched the screen right to the end where things seem to go wrong. From the sparse information we have so far I can imagine the last step of moving the captured image from
/images/dev/...to/images/...is failing for some reason. Please do another capture and make sure you sit next to that screen and take a picture of the error you see right at the end. Post that picture here.The machine reboots and goes into a BSOD loop.
While this should not happen I can see the image type “resizable” to cause something like this. Please use image type “non-resizable” to see if this same thing happens again.
When checking the image size (size on client), it tells me its 500mb - this seems to me that its the System reserve partition ( its first in the partition table)
This value is being updated when capturing. As your capture does not finish all the way to the end that figure might not be updated at all. I don’t know at what stage exactly the update of that number is done from the top of my head. As soon as we figure out why it doesn’t finish.
The image itself on Fog is set to capture the whole disk “partition = everything”, the "image type = single disk- resizeable.
As I said before. Use “non-resizable” as a test. We will get back to resizable when we have fixed all the other issues you have.
Then a .bat file that links to an .xml file that runs specific closure commands ( this process works perfectly for other images)
What exactly does this batch file do? While I don’t think this is causing the issue there is always a chance this is causing trouble. Have you tried not running the batch file and doing a capture yet? Just to make sure this is not causing it?
We have 2 storage nodes - both with more than enough space to hold the image. The above mentioned happens when changing the storage location “image path”
Well, how do you change the “image path”? There is a lot more to it then just changing it in the web UI and click save. Why do you change it?
-
turns out that the image had to be set to “Multiple partition image - single disk (not resizeable)”
@Sebastian-Roth for future reference, I will be sure to mention version numbers
Everything else worked including the .xml file.
Thank you for the assistance!!
