# Rocky 9 kernel-5.14.0-70.17.1.el9\_0.x86\_64 System falls to boot **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [August 3, 2022, 8:49pm UTC](https://forums.rockylinux.org/t/rocky-9-kernel-5-14-0-70-17-1-el9-0-x86-64-system-falls-to-boot/6837 "2022-08-03T20:49:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![stevejkra](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@stevejkra](https://forums.rockylinux.org/u/stevejkra)\ **Post date:** [August 3, 2022, 8:49pm UTC](https://forums.rockylinux.org/t/rocky-9-kernel-5-14-0-70-17-1-el9-0-x86-64-system-falls-to-boot/6837/1 "2022-08-03T20:49:21Z")
After updating the kernel on rocky 9 on a new install it fails to boot, system falls in to emergency mode due initrd-switch-root.service entered failed state. I am able to select the older kernel to get it to boot fine. I did find this on the Redhat forums [https://access.redhat.com/solutions/4973191](https://access.redhat.com/solutions/4973191) but this is for 7.5 I am unable to find anything about this on 9 ---
**Author:** ![stevejkra](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@stevejkra](https://forums.rockylinux.org/u/stevejkra)\ **Post date:** [August 3, 2022, 9:06pm UTC](https://forums.rockylinux.org/t/rocky-9-kernel-5-14-0-70-17-1-el9-0-x86-64-system-falls-to-boot/6837/2 "2022-08-03T21:06:27Z")
I have removed `dnf remove kernel-5.14.0-70.17.1.el9_0.x86_64 kernel-core-5.14.0-70.17.1.el9_0.x86_64 kernel-devel-5.14.0-70.17.1.el9_0.x86_64 kernel-modules-5.14.0-70.17.1.el9_0.x86_64` to get rid of the offending kernel ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [August 4, 2022, 12:13am UTC](https://forums.rockylinux.org/t/rocky-9-kernel-5-14-0-70-17-1-el9-0-x86-64-system-falls-to-boot/6837/3 "2022-08-04T00:13:09Z")
If you are running dnf update during a kickstart in the `%post` section, this is a known issue. Running a dnf update after a kickstart should work normally. ```auto [label@awx ~]$ uname -r 5.14.0-70.17.1.el9_0.x86_64 ``` ---
**Author:** ![stevejkra](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@stevejkra](https://forums.rockylinux.org/u/stevejkra)\ **Post date:** [August 4, 2022, 12:30am UTC](https://forums.rockylinux.org/t/rocky-9-kernel-5-14-0-70-17-1-el9-0-x86-64-system-falls-to-boot/6837/4 "2022-08-04T00:30:50Z")
Yes I did issue a `dnf update -y` in my `%post` script in my kickstarter thanks for the info I did not find that in my search. ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [August 4, 2022, 4:00am UTC](https://forums.rockylinux.org/t/rocky-9-kernel-5-14-0-70-17-1-el9-0-x86-64-system-falls-to-boot/6837/5 "2022-08-04T04:00:22Z")
Yeah this issue affects stream 9 also. I’m actually writing up a bug report as we speak upstream to see if there’s documentation that explains this weird behavior. As a work around, you can probably do this (untested at the moment): ```auto yum update -y source /etc/default/grub NEWKER=$(grubby --default-kernel) grubby --args="${GRUB_CMDLINE_LINUX}" --update-kernel="${NEWKER}" grubby --remove-args="inst.repo inst.stage2 ip inst.ks" --update-kernel="${NEWKER}" ``` There is a comment on the red hat bugzilla that alludes to this behavior too: [1969362 – grubby: apply current arguments to future kernels](https://bugzilla.redhat.com/show_bug.cgi?id=1969362#c37) - so even with the above, the root=… parameter isn’t being populated in /etc/default/grub, so my script above wouldn’t cut it. As an additional edit, doing the below seemed to work, but it expects you to know what the volume/partitions/uuid’s are and such. If you’re doing kickstart installs, it’s likely you’ll know this information. ```auto yum update -y source /etc/default/grub NEWKER=$(grubby --default-kernel) grubby --args="root=/dev/mapper/rockyvg-root ${GRUB_CMDLINE_LINUX}" --update-kernel="${NEWKER}" grubby --remove-args="inst.repo inst.stage2 ip inst.ks" --update-kernel="${NEWKER}" ``` ---
**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brian/32/5777_2.png) [@brian](https://forums.rockylinux.org/u/brian)\ **Post date:** [August 25, 2023, 3:43am UTC](https://forums.rockylinux.org/t/rocky-9-kernel-5-14-0-70-17-1-el9-0-x86-64-system-falls-to-boot/6837/6 "2023-08-25T03:43:26Z")
Closed on August 25, 2023, 3:43am UTC