# Cannot boot latest 8.10 kernel on two of my 100+ Rocky 8 machines

**URL:** <https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695>\
**Category:** Rocky Linux Help & Support\
**Created:** [June 18, 2024, 6:07pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695 "2024-06-18T18:07:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![praines](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@praines](https://forums.rockylinux.org/u/praines)\
**Post date:** [June 18, 2024, 6:07pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695/1 "2024-06-18T18:07:37Z")

</div>

Over the weekend I updated over 100+ servers and workstations (mostly Dell Poweredge servers or Precision workstations) from Rocky 8.9 to 8.10. For the vast majority of these machines everything went fine. But on two of the, both Precision 5820, the new kernel 4.18.0-553.5.1.el8\_10 shows in the GRUB menu but when selected on just gets a blank screen forever with never any output. The system also never appears online at its configured IP. If we select the previous kernel on each box they boot and run just fine.

I tried reinstalling all the kernel packages with

yum reinstall $(rpm -qa | grep 553.5.1)

but same result on reboot. I tried ‘dracut -fv’ and ‘grub2-mkconfig …’ as well with no change.

BTW, I have removed ‘quiet’ from the grub boot parameters so I normally see kernel messages immediately on selecting the older kernel in GRUB. We see nothing with the new kernel.

Any ideas what might be going on?

---

<div class="post-metadata">

**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\
**Post date:** [June 18, 2024, 7:45pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695/2 "2024-06-18T19:45:32Z")

</div>

While booted into the previous kernel, are you able to see any messages at all from the attempt to boot into the newer kernel?

---

<div class="post-metadata">

**Author:** ![praines](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@praines](https://forums.rockylinux.org/u/praines)\
**Post date:** [June 18, 2024, 7:53pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695/3 "2024-06-18T19:53:30Z")

</div>

No, nothing in the /var/log/messages at all from those attempts. Since I see no kernel boot messages I am pretty sure it never gets far enough for the filesystems to be mounted and for any logs to get written too.

I get no error message from GRUB either, so it seems to find the kernel file to boot, but something in booting in the first few microseconds locks the system up.

---

<div class="post-metadata">

**Author:** ![rfs](https://avatars.discourse-cdn.com/v4/letter/r/a87d85/32.png) [@rfs](https://forums.rockylinux.org/u/rfs)\
**Post date:** [June 24, 2024, 8:26pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695/4 "2024-06-24T20:26:35Z")

</div>

Are these the only two machines which are Precision 5820, or are there others of this type for which it’s working ? If they are the only ones, what output do you get from  
lspci -nn | grep VGA  
if any ?

---

<div class="post-metadata">

**Author:** ![praines](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@praines](https://forums.rockylinux.org/u/praines)\
**Post date:** [June 24, 2024, 8:41pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695/5 "2024-06-24T20:41:55Z")

</div>

I have several other Precision 5820’s but after looking at the difference the two machines with the boot issue are both running a BIOS dated from 01/24/2019. All the rest that work have a later BIOS. So I am going to try upgrading the BIOS later this week.

---

<div class="post-metadata">

**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\
**Post date:** [June 25, 2024, 9:03pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695/6 "2024-06-25T21:03:08Z")

</div>

While they are still in the broken state, can you try; either edit existing grub entry, or create a new one.

```auto
remove : "rhgb quiet" (already done)
add : "console=tty0 console=ttyS0,115200 rd.debug initcall_debug"

```

reboot, then choose the “debug” menu entry. On my machine, I got huge extra detail during boot, BUT

Are the machines using UEFI and secure boot?

If so, it might be getting stuck running shim…

---

<div class="post-metadata">

**Author:** ![praines](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@praines](https://forums.rockylinux.org/u/praines)\
**Post date:** [July 5, 2024, 7:22pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695/7 "2024-07-05T19:22:39Z")

</div>

Tried adding “rd.debug initcall\_debug” but still got just a blank screen on boot. We upgraded the box to the latest BIOS version from Dell and still just a blank screen. We then tried booting the 8.10 install USB image to see if that would boot and it did not.

So we have given up at this point and will just stick to the older kernel on these boxes till there is a newer Rocky 8 kernel to try.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [September 3, 2024, 7:23pm UTC](https://forums.rockylinux.org/t/cannot-boot-latest-8-10-kernel-on-two-of-my-100-rocky-8-machines/14695/8 "2024-09-03T19:23:08Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
