Image fails to capture 30% through
-
I don’t have a lot of info about why this is failing, because I don’t know if there are any logs I can find that are generated during an image capture. It technically doesn’t fail it just stalls.
This is a windows 11 image and I’m attempting to capture from a Yoga 7i 14ITL5
I can deploy images to this computer. Here’s what happens when it fails.
I wish I had more info but maybe if someone can point me to some logs we can get to the bottom of things because I assume this isn’t enough to pinpoint what’s happening.
I’m running FOG version 1.5.10
-
@TBCS Make sure your firmware is up to date on this target computer.
What version of FOS Linux (a.k.a the kernel) is installed on your FOG server (FOG UI->FOG Settings->Kernel Update. If you don’t have 5.15.x series installed please do so.
Some of the comments I found that linux kernel 5.12.11 fixed this issue in the kernel. Its not the same exact error, but very close.
I’m also seeing a possible fix for this error by going into the host definition for this computer and putting the following value in the kernel parameters field
libata.noacpi=1I would consider this a last resort. Lets try the firmware and linux kernel update routes first. -
@george1421 Thank you george. Updating the kernel did fix the issue however the capture still halts at around 30%. Unfortunately there’s no error as the capture doesn’t fail, it just stops. This is the first windows 11 image I’ve attempted to capture though I notice it doesn’t exist on the drop down when I specify the OS when creating the image (only windows 10, which is what I selected). Could something related to windows 11 be causing this issue?
-
@TBCS OK Just so I understand. Now the error printed on the screen no longer appears. It was fixed by the kernel update to 5.15.x.
Now when you capture the image capture just freezes at 30% and no visible error is displayed.
Do you have another one of this model you can try to capture? So the question is, is the problem related to this specific computer or this computer model. I’m suspecting there is something strange with the source computer’s storage media. As of now there is no difference in disk structure between windows 10 and 11. So selecting win 11 in the fog ui should work well.
