Stuck on iPXE Initializing Devices
-
No luck with ipxe.pxe. Got the same result, stuck on initializing devices. Think downgrading the kernel would have any effect?
-
@jclumbo33 two things.
- The kernel is not at issue just yet. This is in the iPXE realm. (ipxe starts the kernel [bzImage], but you need to see the iPXE FOG menu first).
- Test by starting the computer from a cold start not a reboot.
I take it this computer is in legacy (bios) mode? Is the firmware up to date on this unit?
-
I’ve tested it from a cold boot with no success and on a few of the same machines that worked a month ago. Yes the machines are in legacy mode. I have not updated the firmware, could this be the issue even though it previously worked?
-
@jclumbo33 What version of fog were you using 1 month ago?
Sorry, second part. When you pxe boot a target computer it displays ipxe banner on that banner there is a hex code in square brackets. Can you post what that code is?
-
@george1421 OK my memory is not so good, it was parentheses not squared brackets. In this case the number is 356f.
-
I was on 1.5.2 when it last worked on those machines. I actually updated to 1.5.3 today to see if that would solve the issue, so it didn’t work on either version.
It doesn’t get to that point, it stops right before it. Here’s a screenshot of where is hangs:
-
Interesting 2 months ago it worked and you were on 1.5.2 , and now it didn’t work, you upgraded to 1.5.3 and it still doesn’t work.
OK lets try rolling back undionly.kpxe back to 1.4.4 version.
On your FOG server change into /tftpboot
cd /tftpboot
Rename your existing undionly.kpxe to a save file.
sudo mv undionly.kpxe undionly.kpxe.sav
Now copy in the 1.4.4 undionly.kpxe into the /tftpboot directory. (look at your fog forum chat bubble)
Now ensure that you update your dhcp server to send out undionly.kpxe as the FOG boot file.Lets see moving back to 1.4.4 version of iPXE does anything different.
-
Still no luck, it hangs in the same spot. I appreciate your help, I was hopeful on that one.
-
@jclumbo33 OK SO… its probably not ipxe that is causing things to stick, but the target system because we’ve kind of ruled out any changes to iPXE kernel or FOG since 1 year ago.
Would you ensure a firmware update does not address this?
It would be interesting to know what is different between the 400 G1 and others that do work.
-
Upgrading the firmware worked!!! No idea what has changed in the last month, but I am just glad for a fix. Thanks for your help!
