[Bug 1200710] New: dracut-initqueue[581]: mount.nfs: No such device
https://bugzilla.suse.com/show_bug.cgi?id=1200710 Bug ID: 1200710 Summary: dracut-initqueue[581]: mount.nfs: No such device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers@suse.de Reporter: schwab@suse.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This appears to be a missing synchronisation with NFS root: [ 10.481118][ T371] mmc_spi spi1.0: SD/MMC host mmc0, no DMA, no WP, no poweroff [ 10.518721][ T17] mmc0: host does not support reading read-only switch, assuming write-enable [ 10.526746][ T17] mmc0: new SDHC card on SPI [ 10.528219][ T368] macb 10090000.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 10.539131][ T368] macb 10090000.ethernet: GEM doesn't support hardware ptp. [ 10.608768][ T373] mmcblk0: mmc0:0000 SD32G 29.9 GiB [ 10.643933][ T373] mmcblk0: p1 p2 p3 p4 p5 [ 10.659954][ T399] MACsec IEEE 802.1AE [ 10.751273][ T368] macb 10090000.ethernet eth0: Cadence GEM rev 0x10070109 at 0x10090000 irq 16 (70:b3:d5:92:f1:07) [ 12.570426][ T441] macb 10090000.ethernet eth0: PHY [10090000.ethernet-ffffffff:00] driver [Microsemi VSC8541 SyncE] (irq=POLL) [ 12.581251][ T441] macb 10090000.ethernet eth0: configuring for phy/gmii link mode [ 16.151411][ T17] macb 10090000.ethernet eth0: Link is Up - 1Gbps/Full - flow control tx [ 16.158934][ T17] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 16.196121] dracut-initqueue[548]: wicked: eth0: Request to acquire DHCPv4 lease with UUID 8a5a9562-2808-0600-2402-000001000000 [ 16.413613][ T549] NET: Registered PF_PACKET protocol family [ 17.110211] dracut-initqueue[548]: wicked: eth0: Committed DHCPv4 lease with address 10.168.4.88 (lease time 1296000 sec, renew in 648000 sec, rebind in 1134000 sec) [ 17.747339][ T582] FS-Cache: Loaded [ 17.939969] dracut-initqueue[581]: mount.nfs: No such device [ 18.855132] dracut-initqueue[602]: mount.nfs: No such device [ 179.792006] dracut-initqueue[384]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 179.797072] dracut-initqueue[384]: Warning: /lib/dracut/hooks/initqueue/finished/nfsroot.sh: "[ -e $NEWROOT/proc ]" [ 179.804241] dracut-initqueue[384]: Warning: dracut-initqueue: starting timeout scripts The only dracut related updates were dracut-kiwi-lib and dracut-kiwi-oem-repart. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c1 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antonio.feijoo@suse.com --- Comment #1 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Andreas Schwab from comment #0)
The only dracut related updates were dracut-kiwi-lib and dracut-kiwi-oem-repart.
It's been a long time without dracut updates. These dracut-kiwi-* packages belong to python-kiwi and are maintained by the kiwi team. If everything worked fine until you updated it, this must be reassigned to them, but I'm not sure who is working on it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c2 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com --- Comment #2 from Thomas Blume <thomas.blume@suse.com> --- nfsroot.sh contains: # root is in the form root=nfs[4]:[server:]path[:options], either from # cmdline or dhcp root-path Maybe a wrong root Parameter was passed? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c3 --- Comment #3 from Andreas Schwab <schwab@suse.de> --- It hasn't changed in ages. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c4 --- Comment #4 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Andreas Schwab from comment #3)
It hasn't changed in ages.
Can you attach the full boot log with debug enabled? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c5 --- Comment #5 from Andreas Schwab <schwab@suse.de> --- Downgrading python-kiwi didn't change anything. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c6 --- Comment #6 from Andreas Schwab <schwab@suse.de> --- How do I enable debug? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c7 --- Comment #7 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Andreas Schwab from comment #6)
How do I enable debug?
remove the "quiet" boot parameter (if present) and add: "debug rd.debug". -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c8 --- Comment #8 from Andreas Schwab <schwab@suse.de> --- Created attachment 859700 --> https://bugzilla.suse.com/attachment.cgi?id=859700&action=edit rdsosreport.txt -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c12 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek@suse.com Flags| |needinfo?(msuchanek@suse.co | |m) --- Comment #12 from Antonio Feijoo <antonio.feijoo@suse.com> --- This error didn't happen in snapshot 20220406 (kmod-29-9.1, kernel-5.17.1-1-default), even updating dracut to the HEAD version. Manually adding /sbin/sysctl to the initrd solves the issue (at least the errors are gone from the log, I don't have any NFS test machines). The current version is kmod-29-9.4, but its latest entry in the Factory kmod.changes file seems to be unrelated. Michal, do you if this is caused by some change in modprobe? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c13 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msuchanek@suse.co | |m) | --- Comment #13 from Michal Suchanek <msuchanek@suse.com> --- How is kmod responsible for missing sysctl? Whatever installs modprobe configuration that depends on sysctl should also install a dracut module that pulls it into initramfs. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c14 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@suse.com Flags| |needinfo?, | |needinfo?(nfbrown@suse.com) --- Comment #14 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Michal Suchanek from comment #13)
How is kmod responsible for missing sysctl?
Whatever installs modprobe configuration that depends on sysctl should also install a dracut module that pulls it into initramfs.
Thanks for pointing me in the right direction. This issue was recently added by nfs-utils: https://build.opensuse.org/package/view_file/openSUSE:Factory/nfs-utils/0001... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c15 --- Comment #15 from Andreas Schwab <schwab@suse.de> --- Adding sysctl to the initrd doesn't change anything here. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c16 --- Comment #16 from Andreas Schwab <schwab@suse.de> --- Forgot to recreate the u-boot image. Adding sysctl does indeed fix the issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c17 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #17 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Andreas Schwab from comment #16)
Forgot to recreate the u-boot image. Adding sysctl does indeed fix the issue.
But take it only as a temporary workaround, see comment #13 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c18 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|dracut-maintainers@suse.de |nfbrown@suse.com Flags|needinfo?(nfbrown@suse.com) | --- Comment #18 from Neil Brown <nfbrown@suse.com> --- Sorry about this. I hadn't imagined the modprobe.d file being installed somewhere that sysctl didn't exist. One option might be to blacklist the file from the initramfs. However it is probably easier to make the scriptlet safe. install sunrpc /sbin/modprobe .... && { /sbin/sysctl .... ; exit 0 ; } seems to work. I'll submit an update. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c19 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson@suse.com --- Comment #19 from Antonio Feijoo <antonio.feijoo@suse.com> --- *** Bug 1201042 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c20 --- Comment #20 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- As reported in bug 1201042 I have the same/similar issues. The actual problem happens when the scripts tries to run: [ 7.344408] dracut-initqueue[729]: + mount -t nfs -orw,nolock 192.168.2.1:/mama/machines/kbl/x86_64/tumbleweed /sysroot [ 7.406876] dracut-initqueue[735]: mount.nfs: No such device If I wait for the timeout to kick in and get access to the shell I can manually type the mount command and everything works fine. I get this problem with both virtual machines and real hardware. I'm attaching the boot log as serial output from a virtual machine. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c21 --- Comment #21 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- Created attachment 859922 --> https://bugzilla.suse.com/attachment.cgi?id=859922&action=edit Serial console output from vm -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c22 --- Comment #22 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- (In reply to Neil Brown from comment #18)
Sorry about this. I hadn't imagined the modprobe.d file being installed somewhere that sysctl didn't exist. One option might be to blacklist the file from the initramfs. However it is probably easier to make the scriptlet safe.
install sunrpc /sbin/modprobe .... && { /sbin/sysctl .... ; exit 0 ; }
seems to work. I'll submit an update.
I gave this a try but it didn't fix the problem for me. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c23 --- Comment #23 from Neil Brown <nfbrown@suse.com> ---
I gave this a try but it didn't fix the problem for me.
That surprises me. Can you please provide an exact copy of your new /usr/lib/modprobe.d/50-nfs.conf file, and confirm that you rebuilt the initramfs after this changing the file. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c24 --- Comment #24 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Neil Brown from comment #18)
Sorry about this. I hadn't imagined the modprobe.d file being installed somewhere that sysctl didn't exist. One option might be to blacklist the file from the initramfs. However it is probably easier to make the scriptlet safe.
install sunrpc /sbin/modprobe .... && { /sbin/sysctl .... ; exit 0 ; }
seems to work. I'll submit an update.
Thanks Neil, I tried your patch (http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=5e60e38aa4ba251e...) and it works for me (at least there is no modprobe failure, I don't have a NFS test setup), but as a minor nitpick it still causes a log entry because stderr is not redirected to /dev/null:
Jul 04 08:13:17 localhost dracut-pre-udev[322]: sh: line 1: /sbin/sysctl: No such file or director
How about something like: install sunrpc /sbin/modprobe ... && { /sbin/sysctl ... 2>/dev/null ; exit 0 ; } -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c25 --- Comment #25 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- (In reply to Neil Brown from comment #23)
I gave this a try but it didn't fix the problem for me.
That surprises me. Can you please provide an exact copy of your new /usr/lib/modprobe.d/50-nfs.conf file, and confirm that you rebuilt the initramfs after this changing the file.
Maybe I messed something up in 50-nfs.conf but here it is: /bin/dracut-emergency@26(): echo 'Entering emPress Enter for maintenance (or press Control-D to continue): sh-5.1# cat /usr/lib/modprobe.d/50-nfs.conf # Ensure all NFS systctl settings get applied when modules load # sunrpc module supports "sunrpc.*" sysctls # install sunrpc /sbin/modprobe --ignore-install sunrpc $CMDLINE_OPTS && /sbin/sysctl -q --pattern sunrpc --system install sunrpc /sbin/modprobe --ignore-install sunrpc $CMDLINE_OPTS && { /sbin/sysctl -q --pattern sunrpc --system ; exit 0 ; } # rpcrdma module supports sunrpc.svc_rdma.* install rpcrdma /sbin/modprobe --ignore-install rpcrdma $CMDLINE_OPTS && /sbin/sysctl -q --pattern sunrpc.svc_rdma --system # lockd module supports "fs.nfs.nlm*" and "fs.nfs.nsm*" sysctls install lockd /sbin/modprobe --ignore-install lockd $CMDLINE_OPTS && /sbin/sysctl -q --pattern fs.nfs.n[sl]m --system # nfsv4 module supports "fs.nfs.*" sysctls (nfs_callback_tcpport and idmap_cache_timeout) install nfsv4 /sbin/modprobe --ignore-install nfsv4 $CMDLINE_OPTS && /sbin/sysctl -q --pattern 'fs.nfs.(nfs_callback_tcpport|idmap_cache_timeout)' --system # nfs module supports "fs.nfs.*" sysctls install nfs /sbin/modprobe --ignore-install nfs $CMDLINE_OPTS && /sbin/sysctl -q --pattern fs.nfs --system -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c26 --- Comment #26 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- When checking the log I can no longer see the sunrpc error so that part seems to be fixed. But I still get: mount.nfs: No such device -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c27 --- Comment #27 from Neil Brown <nfbrown@suse.com> --- Thanks Patrick, You need to make the change on each line, not just the sunrpc line. In particular the "install nfs" line needs it. Thanks Antonio, I think your suggestion of "2> /dev/null" is a good one. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c28 --- Comment #28 from Neil Brown <nfbrown@suse.com> --- I have (At last) submitted a fix for this problem. Sorry about the delay, and thanks for the useful reports. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c30 --- Comment #30 from Patrik Jakobsson <patrik.jakobsson@suse.com> --- (In reply to Neil Brown from comment #27)
Thanks Patrick, You need to make the change on each line, not just the sunrpc line. In particular the "install nfs" line needs it.
Ah thanks, that explains it. Your fix works fine for me. -Patrik -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c31 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #31 from Neil Brown <nfbrown@suse.com> --- Thanks. Closing as FIXED -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c36 Lidong Zhong <lidong.zhong@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |darcy.partridge@suse.com --- Comment #36 from Lidong Zhong <lidong.zhong@suse.com> --- *** Bug 1208155 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c37 --- Comment #37 from Maintenance Automation <maint-coord+maintenance-robot@suse.de> --- SUSE-RU-2023:1587-1: An update that has four recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1200710, 1206781, 1207022, 1207245 Sources used: SUSE Linux Enterprise High Performance Computing 12 SP5 (src): nfs-utils-1.3.0-34.42.1 SUSE Linux Enterprise Server 12 SP5 (src): nfs-utils-1.3.0-34.42.1 SUSE Linux Enterprise Server for SAP Applications 12 SP5 (src): nfs-utils-1.3.0-34.42.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200710 https://bugzilla.suse.com/show_bug.cgi?id=1200710#c38 --- Comment #38 from Maintenance Automation <maint-coord+maintenance-robot@suse.de> --- SUSE-RU-2023:1586-1: An update that has five recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1200710, 1203746, 1206781, 1207022, 1207843 Sources used: openSUSE Leap Micro 5.3 (src): nfs-utils-2.1.1-150100.10.32.1 openSUSE Leap 15.4 (src): nfs-utils-2.1.1-150100.10.32.1 SUSE Linux Enterprise Micro for Rancher 5.3 (src): nfs-utils-2.1.1-150100.10.32.1 SUSE Linux Enterprise Micro 5.3 (src): nfs-utils-2.1.1-150100.10.32.1 Basesystem Module 15-SP4 (src): nfs-utils-2.1.1-150100.10.32.1 SUSE Linux Enterprise Real Time 15 SP3 (src): nfs-utils-2.1.1-150100.10.32.1 SUSE Linux Enterprise Micro 5.1 (src): nfs-utils-2.1.1-150100.10.32.1 SUSE Linux Enterprise Micro 5.2 (src): nfs-utils-2.1.1-150100.10.32.1 SUSE Linux Enterprise Micro for Rancher 5.2 (src): nfs-utils-2.1.1-150100.10.32.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com