Server reboots after downloading kernel in the iPXE process

[Daniel Mare]

I'm having trouble booting a new server which fails after downloading the kernel in the iPXE boot process.  The other 100+ nodes work fine, but this one is using newer hardware, specifically ASUS ProArt Z790-Creator WIFI LGA1700 ATX Desktop Motherboard with i7-12700 CPU.  

I don't know where to start troubleshooting.  I couldn't find any Warewulf logs on the master server, doesn't seem to be anything under /var/log/ as far as I could see and /etc/warewulf/conf files don't seem to reference any sort of logging?  

I have enabled debugging for the node with wwsh object modify -D DEBUG=3, but looks like it might not even be getting to the stage where it can launch the debug shell - still goes into a reboot loop.

The first file it downloads is http://192.168.1.254/WW/ipxe/cfg/58:11:22:b6:4a:8e   Where do I find this, or any of the files it downloads, on the master server?  Or is this dynamically generated at the time the client requests it?  (Currently running a find to try and find it)

I'm not sure if anyone has advice or whether this is perhaps too early in the boot process to be truly warewulf-related?

The exact messages I see right before it reboots are shown below:

>>Checking Media Presence...... 

>>Media Present......

 Downloading NBP file...

   NBP file downloaded successfully. 

iPXE initialising devices...ok

iPXE 1.0.0+ Open Source Network Boot Firmware -- http://ipxe.org

Features: DNS HTTP iSCSI TFTP AOE EFI Menu 

neto: 58:11:22:b6:4a:8e using NII on NII-0000:07:00.0 (open)

  [Link: down, TX:0 TXE:0 RX:0 RXE:0]
  [Link status: Unknown (http://ipxe.org/1a086194)] 

Configuring (neto 58:11:22:b6:4a:8e)...... ok
neto: 192.168.4.9/255.255.248.0 

Next server: 192.168.1.254

Filename: http://192.168.1.254/WW/ipxe/cfg/58:11:22:b6:4a:8e
http://192.168.1.254/WW/ipxe/cfg/58%3A11%3A22%3Ab6%3A4a%3A8e... ok 58:11:22:b6:4a:8e : 455 bytes [script] Now booting RRT-S9 with Warewulf bootstrap (3.10.0-957.1.3.el7.x86_64)
http://192.168.1.254/WW/bootstrap/x86_64/7/initfs.gz... ok http://192.168.1.254/WW/bootstrap/x86_64/7/kernel... ok

[Jason Stover]

Sounds like a kernel issue with the newer hardware. What happens after
downloading that bootstrap file (Warewulf3), is it loads the kernel.
At this point we don't have logs until the initramfs starts up. Check
the HTTP logs and see what's getting requested.... If you setup remote
logging on your master for rsyslog, a node will do process logging to
the master if it's configured (i.e. We're running this step).

The Kernel you're loading (3.10.0-957.1.3.el7) was ... 7.4? 7.5? ....
Do you have a newer kernel (bootstrap) imported that you can test the
node with? What Warewulf does for the Kernel, is load the kernel over
iPXE... it will copy any modules it knows about into the downloaded
VNFS, then switch_root over. So you don't need to worry a lot about
VNFS and Kernel version being lock step unless you have a need for it.

-J

> --
> You received this message because you are subscribed to the Google Groups "Warewulf" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to warewulf+u...@lbl.gov.
> To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/c62dc23f-a52d-4ef6-8097-eb2b07242104n%40lbl.gov.