Solved Almalinux 8 can't bootable, grub terminal show up.

[Ohm J]

This is fresh install ISO and do first update.
Anyone encouter when updating via "dnf update" and reboot then it's not boot, "grub>" terminal show instead ?

So lucky this is just my test server

it's be something like this



###To fixed this problem ###
#fresh install from ISO and execute these command

reboot # Ensure new installed from ISO should working fine.

dnf update grub2-common -y
grub2-install /dev/xvda #this command should return "no error"

reboot # Ensure new "grub2" should working fine.

 

[zEitEr]

Hello,

If you modified /etc/default/grub prior to the upgrade, then it might be the reason

Anyone encouter when updating via "dnf update" and reboot then it's not boot, "grub>" terminal show instead ?

 

[Ohm J]

this is fresh install from ISO, only 1 command execute "dnf update" and reboot.

 

[zEitEr]

I can recollect my own fresh installs from ISO, in certain cases they never booted by normal meanings. Wrong partitioning, missing bootloader, etc.

I am not sure what help you might want in this case. If it is a testing system you might either re-install and see whether the issue re-occurs, or troubleshoot the boot process typing booting commands manually.

this is fresh install from ISO, only 1 command execute "dnf update" and reboot.

 

[Ohm J]

Ahhhh, after spend times 24hr, now I can fixed this issued.

The issued happending when running VM on some cloud software, so "grub2-install {device}" can solved the problem after updated the new version of "grub2-common".

#fresh install from ISO and execute these command

reboot # Ensure new installed from ISO should working fine.

dnf update grub2-common -y
grub2-install /dev/xvda #this command should return "no error"

reboot # Ensure new "grub2" should working fine.

 

[Richard G]

Glad to see you fixed it. I always thought when installing from iso the boot section was automatically done.

Out of curiosity, when you run a normal server in raid 1, how to you copy the boot section to the other device so when first device is corrupted and need replacement, system will boot from the second device?
With the older situations when still using MBR I used this command from /dev/sda:
grub2-install /dev/sdb
kind of like you did now.
And when sda was synchronised then I used the same command with /dev/sda to put the bootsector to sda again.

But this won't work with UEFI anymore. How is it done with UEFI? Any idea?

 

[Richard G]

Ah never mind, just found out this does not work like this with UEFI.
Need to have UEFI partition on both disks. I do have them on both disks, so I hope they will boot when replaced.

 

[Ohm J]

I use virtual machine with legacy boot.

I have dedicated server with cloud software installed something like... xcpNG or proxmox, so I can create the Virtual Machine and can remote access to any VM.

in my case, boot with rescue mode using Linux ISO and mount partition and you can running the command to fixed the issues.



p.s. I still don't know why upgrade the "grub2-common" will breaking the boot operation, so this fixed is just workaround