# Rocky 9.4 AWS ami not booting after kernel update

**URL:** <https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [May 15, 2024, 4:32pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091 "2024-05-15T16:32:32Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![jaredc](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@jaredc](https://forums.rockylinux.org/u/jaredc)\
**Post date:** [May 15, 2024, 4:32pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/1 "2024-05-15T16:32:32Z")

</div>

Hello

We have noticed that on our AWS environments since the 9.4 ami was published our servers do not boot up after a kernel/dnf update which is part of our provisioning

AMI id: ami-02d6d64456f57b99d  
AMI Name: Rocky-9-EC2-Base-9.4-20240509.0.x86\_64  
Region: eu-west-2  
Disk type: gp3  
Instance type: t3.medium

The serial console snippet:

```auto
[15.746077] nvme nvme0: pci function 0000:00:04.0
[15.746470] ACPI: \_SB_.LNKD: Enabled at IRQ 11
[15.770394] nvme nvme0: 2/0/0 default/read/poll queues
[15.775054] nvme0n1: p1 p2 p3 p4
[143.289253] dracut-initqueue[429]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[143.336391] dracut-initqueue[429]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2floop0p4.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[143.436561] dracut-initqueue[429]: [-e "/dev/mapper/loop0p4"]
[143.465303] dracut-initqueue[429]: fi"
[143.482303] dracut-initqueue[429]: Warning: dracut-initqueue: starting timeout scripts
[143.845722] dracut-initqueue[429]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[143.892666] dracut-initqueue[429]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2floop0p4.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[143.992287] dracut-initqueue[429]: [-e "/dev/mapper/loop0p4"]
[144.022260] dracut-initqueue[429]: fi"
[144.038265] dracut-initqueue[429]: Warning: dracut-initqueue: starting timeout scripts
[144.398278] dracut-initqueue[429]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[144.444311] dracut-initqueue[429]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2floop0p4.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[144.541977] dracut-initqueue[429]: [-e "/dev/mapper/loop0p4"]

<snip - same message repeated>

[209.332749] dracut-initqueue[429]: Warning: dracut-initqueue: starting timeout scripts
[209.332777] dracut-initqueue[429]: Warning: Could not boot.
         Starting Dracut Emergency Shell...
Warning: /dev/mapper/loop0p4 does not exist

Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.

dracut:/# 

```

I am new to the forum so will try figure out how to attach the whole console log

Has anyone experienced anything similar?

Regards  
Jared

---

_[View the full topic](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091)._