Booting issues after upgrading to dis. kernel ver 6.18.8

[ShidaDoKongo]

Hello everyone,

After upgrading to Gentoo distribution kernel version 6.18.8 yesterday, my initramfs seems to not include udev support which is manifested by the "by-uuid" folder that is missing under /dev/disks folder. I am using dracut to generate the initramfs image. Please see the attached image that shows the exact error message that I am getting during boot.

I am including a screenshot of the issue on this link: https://i.postimg.cc/yYk209sX/Dracut-Issue1.png

To summarize, after a distribution kernel upgrade, dracut seems to not build the intramfs properly where root file system can't be discovered during boot by the blkid of the file system.

Please help if you have any info how to fix this issue.

Thank you!

[zen_desu]

Hello everyone,

After upgrading to Gentoo distribution kernel version 6.18.8 yesterday, my initramfs seems to not include udev support which is manifested by the "by-uuid" folder that is missing under /dev/disks folder. I am using dracut to generate the initramfs image. Please see the attached image that shows the exact error message that I am getting during boot.

I am including a screenshot of the issue on this link: https://i.postimg.cc/yYk209sX/Dracut-Issue1.png

To summarize, after a distribution kernel upgrade, dracut seems to not build the intramfs properly where root file system can't be discovered during boot by the blkid of the file system.

Please help if you have any info how to fix this issue.

Thank you!

udev may be running but it sounds like potentially kmods for your storage are missing?

You may be able to run lsmod in the recovery env to see that. If lsmod is not included, you could read /proc/modules

I don't think dracut includes the actual "blkid" tool, but may have "lsblk"

[ShidaDoKongo]

udev may be running but it sounds like potentially kmods for your storage are missing?

You may be able to run lsmod in the recovery env to see that. If lsmod is not included, you could read /proc/modules

I don't think dracut includes the actual "blkid" tool, but may have "lsblk"

Thanks for the replay! Yes you are correct udev is actually running. It looks like the kernel module for my SAS controller is missing on 6.18.8. But after looking at /proc/modules, the module seems to be there (shown as "mpt3sas") see attached picture here: https://i.postimg.cc/Z5gL7yxN/Dracut-1.jpg.

But I booted to my pervious working kernel ( ver 6.12.58 ) and regenerated the initramfs using the following code to include the missing kernel module:

Code: Select all

dracut --force --add-drivers "mpt3sas" --hostonly --kver 6.18.8-gentoo-dist

But the issue is still there.

After that I included the following kernel command line option on boot to the 6.18.8 version "rd.debug" to see what is really going on. I have the following screenshot from that: https://i.postimg.cc/7LKqrwbf/Dracut-2.jpg.

I don’t know how to move forward from this. I don't want to be stuck on my old kernel 6.12.58.

FYI I moved the drive that has the gentoo installation to the onboard SATA controller and I am able to boot normally with kernel version 6.18.8. But I can't see the other drives that are on the SAS controller using lsblk.

[zen_desu]

udev may be running but it sounds like potentially kmods for your storage are missing?

You may be able to run lsmod in the recovery env to see that. If lsmod is not included, you could read /proc/modules

I don't think dracut includes the actual "blkid" tool, but may have "lsblk"

Thanks for the replay! Yes you are correct udev is actually running. It looks like the kernel module for my SAS controller is missing on 6.18.8. But after looking at /proc/modules, the module seems to be there (shown as "mpt3sas") see attached picture here: https://i.postimg.cc/Z5gL7yxN/Dracut-1.jpg.

But I booted to my pervious working kernel ( ver 6.12.58 ) and regenerated the initramfs using the following code to include the missing kernel module:

Code: Select all

dracut --force --add-drivers "mpt3sas" --hostonly --kver 6.18.8-gentoo-dist

But the issue is still there.

After that I included the following kernel command line option on boot to the 6.18.8 version "rd.debug" to see what is really going on. I have the following screenshot from that: https://i.postimg.cc/7LKqrwbf/Dracut-2.jpg.

I don’t know how to move forward from this. I don't want to be stuck on my old kernel 6.12.58.

FYI I moved the drive that has the gentoo installation to the onboard SATA controller and I am able to boot normally with kernel version 6.18.8. But I can't see the other drives that are on the SAS controller using lsblk.

While it doesn't resolve your exact issue, ugrd may just work here (won't rely on udev stuff). Someone else may be able to help more, but this sounds like a dracut bug and may be worth a bug report (especially given it works with the same config on a different kernel version)