040ee119 error on boot
-
[quote=“Tom Elliott, post: 27969, member: 7271”]All with this issue:
Per suggestion from one of our Project Leads: Chuck Syperski,
I’ve rebuilt the undionly.kpxe and ipxe.kpxe with the ipxescript set as:
[code]#!ipxe
dhcp || reboot
chain default.ipxe[/code]Please try both if possible.
They are located at:
[url]https://mastacontrola.com/ipxe.kpxe[/url]
[url]https://mastacontrola.com/undionly.kpxe[/url]I’d recommend using the undionly.kpxe first, if that doesn’t work try the ipxe.kpxe AS your undionly.kpxe.[/quote]
Sadly, both produce the same error only this time the client restarts after it fails.
-
[quote=“DanielR, post: 27985, member: 17896”]Sadly, both produce the same error only this time the client restarts after it fails.[/quote]
What is the “same error”? What are the systems, are they virtual or physical systems? I’m sorry if you’ve already answered this but it seems to me like NOTHING is working for your systems and that sounds in accurate. How are these systems failing? Are they getting the 040ee119 error or some other error? Are they freezing at initializing devices? What exactly is happening? Can you provide a screenshot?
-
[quote=“Tom Elliott, post: 28013, member: 7271”]What is the “same error”? What are the systems, are they virtual or physical systems? I’m sorry if you’ve already answered this but it seems to me like NOTHING is working for your systems and that sounds in accurate. How are these systems failing? Are they getting the 040ee119 error or some other error? Are they freezing at initializing devices? What exactly is happening? Can you provide a screenshot?[/quote]
Physical Server on an Isolated Network, running Ubuntu 14.04 and Fog 1.0.1. Able to image our Acer B113 laptops flawlessly, but when it comes to the Acer 1830T, iPXE returns the error 0x040ee119 when trying to configure net0. Its not a big issue as I still have a secondary Fog Server running 0.32 which images both Acer model laptops without a hiccup.
I figured it would be useful to operate with 1.0.1 since it’s received so much praise. The other issue I have is when trying to iPXE boot the new Lenovo Yoga Laptops, which is the main reason I decided to build a Fog 1.0.1 server in an attempt to capture and image those laptops as well, since imaging wasn’t working for them in 0.32
[url=“/_imported_xf_attachments/0/825_photo.JPG?:”]photo.JPG[/url]
-
I’m having the same issue with one of our computers onboard LAN, i’m just leaving the details just in case it helps. I’m going to throw a PCI NIC in it and Fog it anyway. Same 040ee119 error on iPxe, it does get an address at the start of the PXE boot. I’ve attempted to use the last undionly.kpxe which you posted four posts back but that just PXE boots, gets an address and when iPXE tries to run, it times out, i’m guessing and reboots the machine. I don’t get the 040ee119 error. The NIC is a Realtek PCIe GBE Famiily Controller on an Asus P8H61-M LXZ R2.0 Motherboard.
-
For all interested in trying to see what works what doesn’t and if something may have a fix for you:
I’m Rebuilding revs of ipxe in all the forms (e.g. undionly.kpxe, undionly.kkpxe, ipxe.pxe, ipxe.kpxe, ipxe.kkpxe) on my web site.
If you go to the link:
[url]https://mastacontrola.com/ipxe[/url] it will show a listing of folders with a revision name and status:Currently there’s only two rev’s to work with:
f473: This is the revision from r1312 that seems to “just work” so it’s got the tag: f473-GOODAll others will be:
<rev>-TESTAs we get more and more information I’ll be changing labels around. Seeing as nothing, but f473, works I’m just going through the revisions to see if I can narrow down what the issue actually is.
The two that are currently there, f473 is “good” and aaf2 is the “mid-range” between the “good” and the current revisions.
Thank you and hopefully we can figure out the exact nature of this problem.
-
I just tried the f473 undionly.kpxe and got the attached error.
I too was having the 0x040ee119
[url=“/_imported_xf_attachments/0/856_ScreenShot519.png?:”]ScreenShot519.png[/url]
-
Both undionly.kkpxe and undionly.kpxe work 100% of the time for my Dell 3010s with realtek controllers.
However now our 380s with broadcom controllers fail almost evertime with the previous and get stuck in a boot loop.Awesome work, i really appreciate everything you guys are doing.
-
[quote=“Buddy, post: 28536, member: 225”]I just tried the f473 undionly.kpxe and got the attached error.
I too was having the 0x040ee119[/quote]
The error I’m seeing here seems to be of the type of error where something is configured improperly. Possibly due to a schema update? Or the IP it’s using to get the info isn’t correct? The error presented is NOT the 040ee119, so the question remains, with the f473 it’s booting, but giving a different message. With this f473 undionly, are you still getting the 040ee119 message?
-
[quote=“Seb, post: 28602, member: 7969”]Both undionly.kkpxe and undionly.kpxe work 100% of the time for my Dell 3010s with realtek controllers.
However now our 380s with broadcom controllers fail almost evertime with the previous and get stuck in a boot loop.Awesome work, i really appreciate everything you guys are doing. :)[/quote]
Thanks for the support. With which undionly are you getting the issues with the 380’s? And which error?
-
[quote=“Tom Elliott, post: 28603, member: 7271”]The error I’m seeing here seems to be of the type of error where something is configured improperly. Possibly due to a schema update? Or the IP it’s using to get the info isn’t correct? The error presented is NOT the 040ee119, so the question remains, with the f473 it’s booting, but giving a different message. With this f473 undionly, are you still getting the 040ee119 message?[/quote]
With the f473 the 040ee119 went away. Now the “Operation not supported” error is in its place. I can work on 90% of our computers without issues, but the others get stuck on boot. Seems to be the same computers that the 040ee119 was effecting.
-
That doesn’t sound like a problem with undionly. Normally, the error you’re now presented with, is if it can’t communicate with the server, or there’s a schema update needed which isn’t returning the values properly for the boot menu.
I’ve built many rev’s, yesterday, of testing the undionly/ipxe files and the “GOOD” and the “BAD” have been labeled as such. If it’s an undionly problem, try a later revision.
The rev’s I have are labeled, so you can try either or all of them, just use the “GOOD” tagged ones. If you feel like trying to help narrow where the issue use, go ahead and try the TEST labeled files.
f3d42 (most current) “BAD”
aaf2 (mid between f473 and f3d42) “GOOD”
7aa6 (mid between aaf2 and f3d42) “BAD”
57933 (mid between 7aa6 and aaf2) “GOOD”
277f (mid between 57933 and f3d42) “GOOD”
6f410 (mid between 277f and f3d42) “BAD”
6931 (mid between 6f410 and 277f) “BAD” <- FIRST BAD COMMIT
71ed (mid between 6931 and 277f) “GOOD” -
[quote=“Tom Elliott, post: 28604, member: 7271”]Thanks for the support. With which undionly are you getting the issues with the 380’s? And which error?[/quote]
Both undionly.kpxe and undionly.kkpxe on [url]https://mastacontrola.com/ipxe/f473-GOOD/[/url] provide very similar results (100% working on dell 3010)
It is the same 040ee119 error on the 380s, it then reboots and trys again.
I have also since found that dell 755 and 760 have the same issue.So it seems like just our older models.
-
[quote=“Seb, post: 28626, member: 7969”]Both undionly.kpxe and undionly.kkpxe on [url]https://mastacontrola.com/ipxe/f473-GOOD/[/url] provide very similar results (100% working on dell 3010)
It is the same 040ee119 error on the 380s, it then reboots and trys again.
I have also since found that dell 755 and 760 have the same issue.So it seems like just our older models.[/quote]
Try using the ipxe.kkpxe for your environment to see if that will fix your “Old” system issues.
-
Ok went through about 10 of the different undionly.kpxe and still have the problem. Is there anyway I can for a schema update again? I tried to re-run the installer and it said it didn’t need it - so it skipped it. Should I be trying both the ipxe.kpxe and the undionly.kpxe? We have imaged some machines so everything else looks ok. Also it still appears to be affecting only dell 990’s. We pushed the current firmware and no difference.
-
Hello All,
iPXE Developers acknowledged an issue with the iPXE software and has pushed a potential fix for the problem. As always, the files are on my website at: [url]https://mastacontrola.com/ipxe/[/url]
The rev number to test is: d6300-DEFAULT-TEST but all of our pre-tests appear to be successful of this 040ee119 issue. If this error occurs now, it’s likely an actual DHCP issue rather than a problem with the software as it was before.
As the prospects seem good at the moment, I’ve pushed SVN 1769 and 1770 with all of the undionly/ipxe files in svn trunk. undionly.kpxe is the one that we want to work, but if it isn’t working for your systems, try one of the kkpxe or pxe files as your undionly.kpxe.
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp[/url] is the location.
Special thanks to Wolfbane8653 for testing all of these and keeping an amazing log that we could easily track and find out where the issue was.
The FOG Dev team took many build as you can guess, but we don’t have all the hardware or issues others were having. I hope this is the end-all-be-all fix for this issue, and thank you all for the patience. The FOG Dev team’s debugging, suggestions, patience, and testing was instrumental in finding what we could do to “fix” the issue which lead to the iPXE dev team to find an entirely separate, but related, issue with this problem.
So again, I thank you all personally and understand your frustration but appreciate your patience with this. I think I speak for the entire Dev team in saying thank you all very much.
Now on to the regularly scheduled updates. Go forth and test and report as normal. If you’re still having issue please don’t hesitate to let us know so we can track and help further.
Thank you,
-
This newest Undionly.kpxe is working for my DC 7900’s.
-
Bit of a noob on this - but do I just literally download the files that are provided in the link and replace them with the files that are in the boot folder? or is there something else I should do?
-
the tftpboot folder, yes
-
Hi,
Another day, another bash at trying to get this working again…
I’ve replaced the files in the tftpboot folder with the files in the above link, and when I PXE boot from the client now I get IP Address etc (as before) it shows as version iPXE 1.0.0+ (d630) I get a message saying configuring … OK
then I get/defaut.ipxe… No such file or directory
and just sits there
Any thoughts?
Cheers
Matt
-
My guess is this is an issue of the tftp server not being located at the proper location.
See if your FOG server has /var/lib/tftp or /var/lib/tftpboot. Verify that the /tftpboot/default.ipxe file exists, if it does and one of the other directories exist as well, try:
[code]ln -s /tftpboot/default.ipxe /var/lib/{WHICHEVER}/default.ipxe[/code] Try booting again and hopefully all will start working.
