https://bugzilla.suse.com/show_bug.cgi?id=1189776 Chenzi Cao changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |dracut-maintainers@suse.de -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c2 Antonio Feijoo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ohering@suse.com Flags| |needinfo?(ohering@suse.com) --- Comment #2 from Antonio Feijoo ---

Specifically, it is failing the check_block_and_slaves_all function in dracut-functions.sh

I was wrong about this guess. Since a certain upstream commit [1], the function to detect a block device changed from: --> [ -e /sys/dev/block/$1 ] && return 0 --< to --> for _mod in $(get_dev_module /dev/block/$1); do --< and the get_dev_module relies on udevadm, which fails to detect the nvme driver in SLE-15 SP3: virt158:~ # ls -l /dev/block total 0 lrwxrwxrwx 1 root root 10 Oct 5 05:53 259:1 -> ../nvme0n1 lrwxrwxrwx 1 root root 12 Oct 5 05:53 259:2 -> ../nvme0n1p1 lrwxrwxrwx 1 root root 12 Oct 5 05:53 259:3 -> ../nvme0n1p2 lrwxrwxrwx 1 root root 12 Oct 5 05:53 259:4 -> ../nvme0n1p3 lrwxrwxrwx 1 root root 12 Oct 5 05:53 259:5 -> ../nvme0n1p4 lrwxrwxrwx 1 root root 12 Oct 5 05:53 259:6 -> ../nvme0n1p5 virt158:~ # udevadm info -a "/dev/block/259:5" | sed -n 's/\s*DRIVERS=="\(\S\+\)"/\1/p' virt158:~ # udevadm info -a "/dev/block/259:2" | sed -n 's/\s*DRIVERS=="\(\S\+\)"/\1/p' virt158:~ # udevadm info -a "/dev/block/259:3" | sed -n 's/\s*DRIVERS=="\(\S\+\)"/\1/p' virt158:~ # udevadm --version 246 But for me the check works in Tumbleweed and the initrd includes the nvme driver: dev@localhost:~/src/dracut/test> ls -l /dev/block lrwxrwxrwx 1 root root 10 Oct 6 09:21 259:0 -> ../nvme0n1 lrwxrwxrwx 1 root root 12 Oct 6 09:21 259:1 -> ../nvme0n1p1 dev@localhost:~/src/dracut/test> udevadm info -a "/dev/block/259:1" | sed -n 's/\s*DRIVERS=="\(\S\+\)"/\1/p' nvme dev@localhost:~/src/dracut/test> udevadm --version 249 Please, could you check if this still fails with the latest snapshot of Tumbleweed? [1] https://github.com/dracutdevs/dracut/commit/6375d5d504c5eac1cc5e7d7e26a8643b... -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c4 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ohering@suse.com) | --- Comment #4 from Olaf Hering --- bug#1191378 to track the malloc error. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c6 --- Comment #6 from Olaf Hering --- This is the install initrd. It grew from a few dozen MB a decade ago to 133mb. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c8 --- Comment #8 from Antonio Feijoo --- Created attachment 852966 --> https://bugzilla.suse.com/attachment.cgi?id=852966&action=edit virt158 udevadm output You forgot to bind /dev/block. Anyway, after doing it, dracut does not include the nvme driver because udevadm does not find it (see attached file). I don't know if it needs to bind something else to simulate the system, but in my local environment udevadm v249 is able to detect the nvme driver (see comment #2). -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c10 --- Comment #10 from Antonio Feijoo ---

weird, please force the required drivers into initrd in the TMBLWEED partition, then we can actually boot into this partition and see how a Tumbleweed system behaves.

Done. virt158:/root # lsinitrd /boot/initrd-5.14.6-2-default | grep ko | grep nvme -rw-r--r-- 1 root root 69248 Oct 4 02:57 usr/lib/modules/5.14.6-2-default/kernel/drivers/nvme/host/nvme-core.ko.xz -rw-r--r-- 1 root root 26364 Oct 4 02:57 usr/lib/modules/5.14.6-2-default/kernel/drivers/nvme/host/nvme.ko.xz -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c12 Antonio Feijoo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers@suse.de Flags| |needinfo?(systemd-maintaine | |rs@suse.de) --- Comment #12 from Antonio Feijoo --- Frank, does this issue sound familiar to you? See comments #2 and #8. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c14 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com Flags|needinfo?(systemd-maintaine | |rs@suse.de) | --- Comment #14 from Franck Bui --- No sorry it doesn't ring me a bell. Can I have access to the TW system which is affected ? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c16 --- Comment #16 from Franck Bui --- (In reply to Olaf Hering from comment #15)

See comment#0 about which system is affected.

The credentials are missing and I tried the usual "default" passwords for the orthos machines but with no luck. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c18 --- Comment #18 from Franck Bui --- (In reply to Olaf Hering from comment #17)

Indeed, it is root/suse

Still doesn't work when I tried to log in via ssh: $ ssh root@virt158.devlab.prv.suse.com Can you please make accesses through ssh work ? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c20 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ohering@suse.com) --- Comment #20 from Franck Bui --- (In reply to Olaf Hering from comment #0)

Installing SLE15SP3 works fine, nvme.ko is included.

Could you show the output of 'ls -l /sys/dev/block/' for SP3 ? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c22 --- Comment #22 from Olaf Hering --- 259:1 -> ../../devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1 259:2 -> ../../devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1/nvme0n1p1 259:3 -> ../../devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1/nvme0n1p2 259:4 -> ../../devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1/nvme0n1p3 259:5 -> ../../devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1/nvme0n1p4 259:6 -> ../../devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1/nvme0n1p5 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c24 --- Comment #24 from Jean Delvare --- I asked upstream for an explanation of why NVME device sysfs paths are different from one system to the next. You can read the discussion here: https://lore.kernel.org/linux-nvme/b98f6062f59c1c1cfc4a200de83e4e244efbffbf.... I'm not going to claim I understand all the technical details, but my understanding is that the difference is there to stay and user-space will have to deal with it. Martin Wilck's answer actually includes a suggestion of how this could be done, hopefully that will help. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c26 Antonio Feijoo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS Flags|needinfo?(jdelvare@suse.com | |) | --- Comment #26 from Antonio Feijoo --- (In reply to Antonio Feijoo from comment #25)

Thanks for your feedback. Actually we've submitted a dracut PR which would solve this issue following symlinks.

https://github.com/dracutdevs/dracut/pull/1626

The patch was accepted. The fix is in progress. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 Frank Kr�ger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger@mailbox.org -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1189776 https://bugzilla.suse.com/show_bug.cgi?id=1189776#c29 Antonio Feijoo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #29 from Antonio Feijoo --- The fix for this bug is included since dracut-055+suse.152.g9d554c37 (TW and SLE-15-SP4), so we can close it. -- You are receiving this mail because: You are on the CC list for the bug.