iPXE initialises devices ok but reboots when Configuring(net0 00:23:7d:b8:a5:54)......
-
Fog stops in IPXE even when i just want to get to the menu.
-
Are you using undionly.kpxe or undionly.kkpxe? Could you try ipxe.pxe?
Is this on ALL machines, or just this particular model?
Is it ONLY this machine itself and all others work?
I’m just trying to get all the info.
-
Now i’m using undionly.kpxe. I tried undionly.kkpxe but it did not work.
I will try ipxe.pxe.
This occurs in all machines.Thanks
-
I changed the boot file to ipxe.pxe and i’ve got the same original problem.
So i downloaded the boot file ipxe.pxe using this command:
wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.pxe -O /tftpboot/ipxe.pxe
And the result was the same as using undionly.kpxe, stops at IPXE.
-
@luislesi I spent almost the entire day today trying to figure out a very similar issue - I was seeing the same response to pxe boot. We have two VLANs in the building and one worked and the other did not. On our “problem” VLAN it turns out we had spanning tree turned on, but it was turned off on the “good” VLAN. To make matters worse we can’t turn it off because the network issue it is resolving hasn’t been located yet.
What I ended up doing was turning portfast (props @Sebastian-Roth) on individually for each of the ports being used by the machines I wanted to image. I’m NOT a network guru, I can’t explain to you why it works but it did in my case. Just my 0.02, I don’t see that you have yet posted the results of the STP/PF adjustments you planned to make.
Edit: To try to clarify, I believe the iPXE messages you’re seeing up to the point of the “iPXE>” prompt is the output of the PXE boot ROM of the computer, not anything coming from the network. The DHCP boot process is failing and the PC is not reaching the FOG server. In my case it was due to spanning tree being turned on in our network. The only way around that was to enable portfast on the switch.
-
@gwhitfield The portfast it’s enabled in all ports of the switch so at this moment i dont know what to do anymore. Thanks for all that helped me.
-
@luislesi Sorry if this is a repeat, I quickly looked through the thread and didn’t see this…
Can you upgrade your 1.2.0 stable version of fog to 1.3.0-rc4? This will upgrade the FOG environment to the latest. https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
I feel you have done everything with 1.2.0 with no success. I’m not saying for absolute that 1.3.0-rc4 will fix your issue, but there has been quite a few enhancements in the boot code for ipxe as well as the fos engine (linux OS that is booted on the target computer).
-
I agree with George. There’s just no reason to not use the latest RC. It’s solid. And the more people we have testing it, the more sure we can be that it’s ready.
-
I’m having the same problem trying to image using ASIX88772B dongle …
I’m using undionly.kkpxe as boot file fog 1.2.0 and the machine is in legacy mode.
What can be wrong? -
@koenkeersmaekers As the other answers suggest, please upgrade to the RC’s as it will have much better support for these things. FOG 1.2.0 is nearly 3.5 years old now. The RC’s are much more reliable (I think) and will likely address common issues related to what you’re possibly seeing as well as the LARGE number of improvements made overall.
-
@Tom-Elliott thanks but after the upgrade it didn’t work neither it got worse
deploying and capturing images is not working anymore (image doesn’t belong to storage node) and i cant add hosts by the quick host registry …
I’m considering to downgrade to the latest stable version(1.2.0) … -
@koenkeersmaekers that makes 0 sense. What do you mean it got worse?
-
@Tom-Elliott i mean the asix dongle doesn’t work neither with the new version and the ‘worse’ part is that i can’t manage the images made by the older version
(1.2.0) … it has something to do with the storage nodes i guess
i’m not giving up
thanks for the help, i keep you posted! -
@koenkeersmaekers check your images are assigned to storage groups. Images groups changed from 1.2.0 to the rcs and that change is difficult to fully automated. Images can belong to multiple groups now. As a part of that it needs to belong to at least one group.
