Updating Fedora 34 kernel leads to unbootable machine. How to reproduce: - start i3.large machine - update the kernel-core package (brings in linux-firmware, and can not be --exclude'd) - reboot - machine doesn't start anymore There's no possibility to go through AWS remote console, because i3 instances don't support that. Log: [root@ip-172-30-2-21 ~]# dnf update kernel-core Last metadata expiration check: 0:01:32 ago on Tue 12 Oct 2021 09:26:26 AM UTC. Dependencies resolved. ============================================================================== Package Architecture Version Repository Size ============================================================================== Installing: kernel-core x86_64 5.14.10-200.fc34 updates 35 M Installing dependencies: linux-firmware noarch 20210818-122.fc34 updates 184 M Transaction Summary ============================================================================== Install 2 Packages Total download size: 219 M Installed size: 272 M Is this ok [y/N]: y Downloading Packages: (1/2): kernel-core-5.14.10-200.fc34.x86_64.rpm (2/2): linux-firmware-20210818-122.fc34.noarch.rpm ---------------------------------------------------------------------- Total Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : Installing : linux-firmware-20210818-122.fc34.noarch Installing : kernel-core-5.14.10-200.fc34.x86_64 Running scriptlet: kernel-core-5.14.10-200.fc34.x86_64 Verifying : kernel-core-5.14.10-200.fc34.x86_64 Verifying : linux-firmware-20210818-122.fc34.noarch Installed: kernel-core-5.14.10-200.fc34.x86_64 linux-firmware-20210818-122.fc34.noarch Complete! [root@ip-172-30-2-21 ~]# reboot When I create a snapshot image from such instance, I can start the box with other instance type (e.g. m5*).
System log (for google): [ OK ] Reached target Basic System. Starting dracut initqueue hook... [ 3.610370] nvme nvme0: pci function 0000:00:1e.0 [ 3.631836] nvme nvme0: 15/0/0 default/read/poll queues [ 131.397946] dracut-initqueue[335]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 131.404583] dracut-initqueue[335]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f386769a3-cfa5-47c8-8797-d5ec58c9cb6c.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then [ 131.418040] dracut-initqueue[335]: [ -e "/dev/disk/by-uuid/386769a3-cfa5-47c8-8797-d5ec58c9cb6c" ] [ 131.423759] dracut-initqueue[335]: fi" [ 131.426372] dracut-initqueue[335]: Warning: dracut-initqueue: starting timeout scripts [ 131.954427] dracut-initqueue[335]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 131.960217] dracut-initqueue[335]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f386769a3-cfa5-47c8-8797-d5ec58c9cb6c.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then [ 131.971638] dracut-initqueue[335]: [ -e "/dev/disk/by-uuid/386769a3-cfa5-47c8-8797-d5ec58c9cb6c" ] [ 131.977012] dracut-initqueue[335]: fi" ....
Might this be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2010058 ?
Thanks for looking, Kevin. I noticed the Dracut update now, yeah, perhaps duplicate to that and #2013183. *** This bug has been marked as a duplicate of bug 2010058 ***