Root partition not recognized after update to kernel 5.18

Support Kernel
21

I just did. Same error. I am back to 5.17 now.

22

By any chance, in bios, you donā€™t have raid mode set for the drive, but ahci/nvme, right?

Iā€™d still like to see this.

23

Here is the photo. No I dont have any raid setup. And I havenā€™t modified anything in the bios before or after the update to 5.18

IMG_20220617_143447
IMG_20220617_1434471920Ɨ1080 82 KB

24

If you do:

mount /dev/nvme1n1p3 /new_root && exit

does it boot?

Edit:

I understand. But can you check what setting you have next time you reboot.

25

no idea! iā€™ll try a bit later and report back

26

I just tried it and I get special device /dev/nvme1n1p3 does not exist

also I just noticed that blkid only reports the data devices when I am in this emergency console. is it possible that the nvme support in 5.18 is bugged?

IMG_20220617_153334
IMG_20220617_1533341920Ɨ1080 98.6 KB

27

As you can see there are no NVMe drives detected in initramfs. You can try googling that for possible solutions. Perhaps:

  • adding vmd to MODULES in /etc/mkinitcpio.conf, or
  • adding some additional HOOKs to mkinitcpio.conf (sorry, too lazy to find which ones :D), or
  • Enter BIOS Setup ā†’ Advanced ā†’ Chipset Configuration ā†’ North Bridge ā†’ IIO Configuration ā†’ Intel VMD Technology ā†’ Intel VMD for Volume Management Device on CPU, and DISABLE ā€œIntel VMD for Volume Management Deviceā€ option.
  • etc.

TLDR: Either something has to be changed in bios or in mkinitcpio (and then run mkinitcpio -P), I think at least.

1 Like
28

understood! i have tried the vdm thing in modules but that didnā€™t work. i will look into hooks and then for the rest iā€™ll have to find the equivalent for amd i suppose because i have an amd chipset.

29

The filesystem drivers for the root partition is missing.

30

how do i solve this? why are they missing all of a sudden?

31

Can you post /etc/fstab ?

32

If this is true, why not hang tight with kernel 5.15 LTS or kernel 5.17 then?

Thereā€™s no crucial need to always have the very latest kernel with every upstream release.

2 Likes
33

5.17 is EOL and 5.15 is old and boring. :stuck_out_tongue:

34

I didnā€™t realize ā€œexcitingā€ was something to strive for in a kernel that youā€™re not even supposed to be aware of as you use you computer day-to-day. :wink:

35

Have you checked your bios settings yet?
I have another awesome idea though. Can you edit kernel 5.18 entry in grub menu and replace
initramfs-5.18-x86_64.img with Ƭnitramfs-5.17-x86_64.img

Edit: yeah ok, that wonā€™t work. Weā€™ll find some other hacky way to make this fun. :smiley:

36

We as humans need to strive to uncover the unknown.

37

i did a bit earlier in the conversation!

38

yes that is exactly the reason! plus if I see that update notification what am I supposed to do? ignore it?!

39

yes I checked the bios and there is no VDM in there. There is hardly anything regarding NVME that I can affect.

Also vdm in MODULES in mkinitcpio is apparently only for Intel. There was a mention somewhere (I lost the link) that for amd one should add nvme instead of vdm. I did that but still nothing.

40

WIth 5.18 installed, and as a root, post output of:

diff <(lsinitcpio -a /boot/initramfs-5.18-x86_64.img) <(lsinitcpio -a /boot/initramfs-5.17-x86_64.img)

Btw in the end something stupid will work, ie. reinstalling systemd and/or mkinitcpio or some other bs. :stuck_out_tongue:

Also, I still need you to test it with your iommu and pci passthrough parameters removed.