One of many MicroOS machines hanging in GRUB after reboot
Hi all, for some reason, one of my MicroOS servers is hanging in GRUB after a reboot each day. This has started some days ago, I think on Sunday. I have a monitor connected to the servers, when I power on the monitor I see the GRUB menu just waiting for the confirmation. Hitting enter makes the machine boot properly. I have several MicroOS servers, x86_64, armv7l and aarch64, this particular one is part of a 3-node Kubernetes cluster that gets rebooted by kured. All of the machines should[tm] be configured the same, all were installed (a) year(s) ago and are updated automatically using the transactional-updates.timer. Not sure why the other machines do not show this behaviour, if this was introduced by an update then all machines should show it. Any ideas? Kind Regards, Johannes
Hello, On Wed, Aug 07, 2024 at 07:01:39AM +0200, Johannes Kastl wrote:
Hi all,
for some reason, one of my MicroOS servers is hanging in GRUB after a reboot each day. This has started some days ago, I think on Sunday.
I have a monitor connected to the servers, when I power on the monitor I see the GRUB menu just waiting for the confirmation. Hitting enter makes the machine boot properly.
probably something generates a key event, either on a keyboard or there is a noise on serial port if you have one. If it hangs reliably the noise should be quite frequent, and you should see it with evtest or reading the serial port(s). Grub can probably be configured to not boot automatically as well. Make sure the grub.cfg as well as the environment is really identical between the machines. HTH Michal
Hi Michal, On 07.08.24 08:38 Michal Suchánek wrote:
probably something generates a key event, either on a keyboard or there is a noise on serial port if you have one. If it hangs reliably the noise should be quite frequent, and you should see it with evtest or reading the serial port(s).
Grub can probably be configured to not boot automatically as well. Make sure the grub.cfg as well as the environment is really identical between the machines.
Grub booted automatically on this machine until Sunday or so, without me changes anything. So either something surfaced that was there for a long time, or some update changed something. But a hardware issue that only affects one machine is more likely in this case, I'll check that. Kind Regards, Johannes
participants (2)
-
Johannes Kastl -
Michal Suchánek