So, i realize i made the mistake of posting this on a Friday afternoon, but i’m still as stuck as i was previously. Has anyone else run into this?
cklemm last edited by cklemm
@tom-elliott Sorry about the confusion. I’m having some trouble with video, but there really only are a few screens. Also, sorry, for imgur, but apparently the images are too big to be uploaded directly.
This shows the basic booting to the NIC.
This is the computer at Fog OS, showing not registered.
I selected ‘Perform Full Host Registration and Inventory’ though the same thing happens with quick registration.
Then the computer reboots and shows this:
This is where it gets stuck.
Does that help?
EDIT: And the images aren’t showing up anyway. Added links.
Also, apparently if i leave it at that screen long enough it moves to this screen:
@cklemm can you provide a video of the restart and what it is, or rather not, doing? I’m still not sure where problems are happening.
@tom-elliott Yeah, it loads into Fog OS, but when it reboots to register with the server is when it gets caught. On the DHCP server i’ve set up options 66 & 67, as well as every option mentioned on this page: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
Is there anything else that I might need?
@cklemm I didn’t know it made it into FOS and was thinking it was failing to load ipxe. I would check dhcp configuration just in case there is a misconfiguration though.
I made sure that that was configured. As it happens, both the server and the clients I’m testing are plugged into the same switch right now, however, nothing seems to be different.
I did manage to get into a limited command space where it let me put in a number 1-7 for different options. That showed that i wasn’t able to ping the server (or anything else) and that the device itself didn’t have an IP.
The specific way it gets stuck looks like this:
udhcpc: started, v1.26.2
udhcpc: sending discover (x3)
udhcpc: no lease, failing
Either DHCP failed or we were unable to access <fog server> for connection testing.
It repeats all that three times, then says:
No DHCP response on interface eth0, skipping it.
Failed to get an IP via DHCP! tried on interface(s): eth0
Please check your network setup and try again.
Does that make sense? Is there a way i could just give it an IP at this screen, or is there something that i should have configured on the DHCP server that is missing?
This really sounds like a spanning tree issue from the network. Please see if using rapid stp or fast stp is feasible. As a quick verification and operational standpoint, you could also put a dumb switch between the host and the main lan and see if it works better for you.