Can't read CTR while initializing i8042 + Failed to start OpenSSH -> boot could not complete

Hardware: HP PROLIANT DL380 GEN10 PLUS server
OS: RHEL 8.9

Problem:
After an electrical cuts the system we are unable to login into the system.
Using ILO (v.5) we reboot the machine and we get the following sequence:

1. we get the following messages:
   • [0.070382] x86/cpu: SGX disabled by BIOS.
   • [2.171788] i8042: Can't read CTR while initalizing i8042

2. The system then continues the boot process normally:

3. At an specific point of time we choose between start the RHEL or System Setup. We choose the first one.

4. We are asked to introduce the LUKS2 decryption key: we introduce it and the boot continues.

5. Later on, the following error message is shown: "Failed to start OpenSSH server daemon".

6. Finally, we get the system prompt (login) but we are unable to provide an input (user and password), i.e., nothing is written in the screen, the keyboard seems unresponsive. Therefore, we can not log into the system.

-0-
as part of the troubleshooting:

• we entered the RHEL emergency mode by pressing the ‘e’ key while the system is booting.

• This allows to edit the Grub ‘linux’ line, replacing the “ro” with “rw init=/sysroot/bin/sh” and pressing CTRL + X to boot the system.

• After boot, ‘:/# ‘ prompt is shown, and we are able to use systemctl as systemd is enabled and running. However, we cannot see the partitions of the system yet, and the services shown are not the ones present on the system when normal boot is completed succesfully. To mount the root system, we executed the command:

:/# chroot /sysroot

• This allowed me to access the root partition. However, after this command, I cannot use ‘systemctl’ commands as systemd is no recognized on the system. As far as we have read on fórums, systemd and systemctl are only available if systemd is PID 1.

• How can we mount the rest of partitions apart from the /root? As /var and /var/log/ partitions are separated and not mounted, I cannot access them to check the logs.

• Is it posible to mount the partitions in emergency mode and still be able to use systemd / systemctl?

• When in emergency mode, journalctl is not showing any boot information, as commands like ‘journalctl -b 1’ ‘journalctl -b 3’ are empty. How can we access this information from emergency mode? Is there a possibility to access this information on normal boot before the system crashes? (apparently, it crashes when login prompt is shown)