View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000110 | AlmaLinux-8 | almalinux-release | public | 2021-06-29 11:58 | 2021-07-27 12:05 |
| Reporter | Wumbeer | Assigned To | alukoshko | ||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Platform | Dell PowerEdge T340 | OS | AlmaLinux | OS Version | 8.4 |
| Summary | 0000110: Fresh install - do all updates - reboot - BIOS does not find OS - no grub | ||||
| Description | Fresh install of AlmaLinux will not boot after updates - BIOS message about no bootable device or operating system. You do not even get to grub menu showing kernels. Been running AlamaLinux for few months on this server and was just doing updates and killed it. I reinstalled again and did a yum update and it broke again, exact same way, so it is reproducible. Not sure what is killing it, I assume a grub problem. I found https://www.reddit.com/r/CentOS/comments/i0ozrs/cant_boot_in_after_latest_kernel_update_for/ 3 which seems similar, but 11 months ago, so we tried it - and I get same problem user Joeg1484 got. Gave up and just not going to install updates. | ||||
| Steps To Reproduce | 1. Install AlmaLinux 2. Update all packages (coming from CentOS so I been using yum) 3. Reboot | ||||
| Tags | No tags attached. | ||||
| abrt_hash | |||||
| URL | |||||
|
|
Hello. Are you in BIOS or UEFI mode? Is Secure Boot enabled? What version I should install to reproduce update bug 8.3 or 8.4? |
|
|
UEFI mode. Secure boot is not enabled. 8.4 was the version. |
|
|
I verified just to make sure I was not incorrect about the above: [root@virtual1 ~]# mokutil --sb-state SecureBoot disabled [root@virtual1 ~]# ls -l /sys/firmware/efi total 0 -r--r--r--. 1 root root 4096 Jun 30 15:29 config_table drwxr-xr-x. 2 root root 0 Jun 27 14:08 efivars -r--r--r--. 1 root root 4096 Jun 30 15:29 fw_platform_size -r--r--r--. 1 root root 4096 Jun 30 15:29 fw_vendor drwxr-xr-x. 2 root root 0 Jun 30 15:29 mok-variables -r--r--r--. 1 root root 4096 Jun 30 15:29 runtime drwxr-xr-x. 9 root root 0 Jun 30 15:29 runtime-map -r--------. 1 root root 4096 Jun 30 15:29 systab drwxr-xr-x. 2 root root 0 Jun 30 15:29 tables drwxr-xr-x. 77 root root 0 Jun 30 15:29 vars |
|
|
I have the same situation for 'mokutil --sb-state' and 'ls -l /sys/firmware/efi'. I've installed system, update them by 'yum update' and it rebooted without any problem. I've repeated this twice. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-06-29 11:58 | Wumbeer | New Issue | |
| 2021-06-29 13:15 | alukoshko | Note Added: 0000290 | |
| 2021-06-29 13:51 | alukoshko | Assigned To | => alukoshko |
| 2021-06-29 13:51 | alukoshko | Status | new => assigned |
| 2021-06-30 19:28 | Wumbeer | Note Added: 0000296 | |
| 2021-06-30 19:35 | Wumbeer | Note Added: 0000297 | |
| 2021-07-27 12:05 | sfokin | Note Added: 0000319 |
