2.1 KiB
Boot Issues
SecureBoot
While having secure boot enabled it is not possible to load the yfs kernel module or Nvidia drivers. Therefore it is important that secure boot is disabled on the systems booting EFI!
This is how to check on a running system if secure boot is enabled:
mokutil --sb-state
https://access.redhat.com/articles/5337691
Network Boot Failure on UEFI System
If the system downloads the bootloader, but then fails, it might be due to downloading the wrong bootloader, here pxelinux.0 instead of shimx64.efi.
The Linux Team can check in the journal of boot.psi.ch what was actually downloaded.
If that is confirmed, then the issue is probably a so far unknown Vendor Class which is sent with the DHCP request of the firmware. It is configured in QIP:
Please inform the network team about the missing Vendor Class.
(for plain dhcpd there would be a generic solution but apparently this cannot be implemented in QIP (yet?)).
Redirect Serial Output to File in VMware
To change the serial port settings the VM needs to be shut down. Then edit the VM settings and add a new serial device by clicking "ADD NEW DEVICE" on top right and there select "Serial Port".
The serial port should then be connected to a file on the datastore serial_console:
At the moment we have this setup for lxdev06, lxdev07 and lxdev08 already prepared.
These files then can be accessed over lxsup.psi.ch:/data/serial_console.
Send Grub Output to Serial Port
For sending out Grub debug information over the serial port to a file because it is to much to fit the screen or for later inspection, you might do the following:
- in the Grub menue type
cto get to the command line - configure the serial port with
serial --unit=0 --speed=115200
- set the output to the serial port, run the debug command and set the output back:
terminal_output serial; lsefi; terminal_output console