Error JME:Disable TX Engine Timeout
I am receiving the error above when trying to deploy an known working image to multiple laptops (The image has been deployed successfully to 30 other laptops of the same make/model).
Currently using FOG v1.2.0
Wayne Workman last edited by
For future readers - this problem was most likely caused by the image being deployed to a HDD that was too small to hold the image. This is a common error with non-resizable type images and is normally resolved by using resizable type images or by deploying to HDDs that are large enough to receive the image. Further documentation can be found in the WiKi here:
@Uncle-Frank, Thanks for your suggestion.
The issue has now been resolved.
@HighfieldsSch Thanks for the picture. This is very helpful. Without it I would have thought that you see this error on bootup (long before FOG does its work).
To me this looks like your destination disk is smaller than the one you pulled the image from. See this discussion for more information: https://forums.fogproject.org/topic/5956/images-not-being-deployed
HighfieldsSch last edited by Wayne Workman
Please see photo attached. The Laptops are Stone NT307, and the laptops were successfully deployed about 3/4 months ago. The error appears after the kernel has loaded.
Please let me know if you need any further info
Taking a look at both the source code of the linux kernel and iPXE I saw that this error can be thrown by both - as both seam to use a very similar implementation of the JME driver. So I am wondering where exactly you see the error. Before or after kernel (bzImage/init.xz) is being loaded?? Probably best if you could upload a picture of the error message on screen.
Are you absolutely sure those laptops have the exact same NIC? What is the exact laptop model (so we could also try to find out about the hardware details on the net)?
Which iPXE binary do you use? undionly.kpxe, ipxe.pxe
Maybe you can try using undionly.kkpxe (note the double ‘k’).
Wayne Workman last edited by Wayne Workman
@HighfieldsSch Can you provide a photo of the error? At what point in the imaging process does the error happen? What happens just before the error? And what is the make/model of these 4 laptops, and have you ever been able to image that make/model before?
Happened on 4 hosts, all 4 same make/model.
Is this only impacting one host? Maybe the host has something wrong?