Sample Header Ad - 728x90

Initramfs can't find root partition UUID after update

1 vote
1 answer
443 views
I am running Parabola Linux (libre fork of Arch) on a laptop with an nvme SSD. I ran a full system update yesterday and since then I have been getting the following error on boot: Image of initramfs error. It appears to be an initramfs issue: it seems to not be able to find the root partition by UUID. I have checked lsblk and verified that the UUID is correct. I have also tried going in with an arch-chroot and re-running mkinitcpio, but still get the same error. I have also checked the initram image with lsinitcpio, to verify that it includes the nvme modules (it does). The fallback initramfs image seems to give the same error. The keyboard also doesn't work in the rootfs prompt, which suggests the issue is due to modules not being loaded correctly. Does anyone have any idea what the issue might be here and how to resolve it? Neither grub.cfg nor /etc/fstab were touched during the system update, so I am at a complete loss as to what may have happened here. --------------------------------------- **Update:** I made a custom initcpio hook to try to debug the issue, as suggested by frostschutz in the comments. This shows the output of several other commands during boot: Boot output with custom initcpio hook. It seems fairly conclusive from this that udev is not doing it's job and is not loading any kernel modules during the initcpio phase. The modules loaded in the initramfs are the correct version for the kernel, as evidenced by the fact that a couple have been loaded (which I explicitly requested in mkinitcpio.conf). Does anyone have any idea why udev is now suddenly not working, following the system update? I believe some changes were made to udev during the update (I think it changed to a different udev package?).
Asked by Time4Tea (2628 rep)
Feb 15, 2025, 11:58 AM
Last activity: Feb 16, 2025, 12:35 AM