Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Win 10 Build 18363: WSL2 and NFS client mount attempt yields mount.nfs: No such device #5838

Closed
cjbryant-github opened this issue Aug 31, 2020 · 5 comments

Comments

@cjbryant-github
Copy link

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Your Distribution version: [On Debian or Ubuntu run `lsb_release -r` in WSL]
Whether the issue is on WSL 2 and/or WSL 1: [run `cat /proc/version` in WSL]

Steps to reproduce

WSL logs:

Expected behavior

Actual behavior

@cjbryant-github
Copy link
Author

cjbryant-github commented Aug 31, 2020

Hello,
I am having trouble mounting to ANY Linux NFS server (elsewhere on my network) on WSL2 (Ubuntu 20.04) getting mount.nfs: No Such device. I have reas this could be a problem with the installed NFS Kernel modules. I have issued all the apt-get commands for mount, nfs client packages, nfs library and lock packages, etc.

If these NFS kernel modules are out of whack, how can this be repaired? This is fresh Ubuntu 20.04 install from the Microsoft App Store and fresh NFS install and I have rebooted the WIn 10 machine afterwards.

I am running Win 10 Build 18363.

There is nothing inside the /usr/lib/modules or the /lib/modules directory.

Issuing "systemctl list-unit-files | grep -i nfs" shows:

proc-fs-nfsd.mount static enabled
nfs-blkmap.service disabled enabled
nfs-common.service masked enabled
nfs-config.service static enabled
nfs-idmapd.service static enabled
nfs-kernel-server.service enabled
nfs-mountd.server static enabled
nfs-server.service enabled enabled
nfs-utils.service static enabled
nfs-client.target.service enabled enabled

Thank you for any assistance!

@cjbryant-github cjbryant-github changed the title Running WIn 10 Build 18363: WSL2 and NFS mount attempt yields mount.nfs No such device Running WIn 10 Build 18363: WSL2 and NFS client mount attempt yields mount.nfs No such device Aug 31, 2020
@cjbryant-github cjbryant-github changed the title Running WIn 10 Build 18363: WSL2 and NFS client mount attempt yields mount.nfs No such device Running Win 10 Build 18363: WSL2 and NFS client mount attempt yields mount.nfs No such device Aug 31, 2020
@cjbryant-github cjbryant-github changed the title Running Win 10 Build 18363: WSL2 and NFS client mount attempt yields mount.nfs No such device Running Win 10 Build 18363: WSL2 and NFS client mount attempt yields mount.nfs: No such device Aug 31, 2020
@therealkenc
Copy link
Collaborator

I am running Win 10 Build 18363.
I have reas this could be a problem with the installed NFS Kernel modules.

There are no kernel modules (and no Linux kernel) in WSL1. Academically same #2869. NFS is available in WSL2 as of 20H1 aka version 2004 aka build 19041.

@cjbryant-github
Copy link
Author

Hello,
Thank you for your reply! I mistakenly thought downloading the latest Ubuntu 20.04 from the Win 10 App Store was WSL2. My machine does indicate Win 10 Build 1909. I do have access to some 2004 Win 10 machines so I will re-try there. Thank you very much!

~Charlie

@Ashark
Copy link

Ashark commented Oct 4, 2020

So, still no way to mount nfs with utf-8 file names when windows is itself in virtual machine.
wsl1 have not got kernel modules, and wsl2 requires the physical virtualization available.

@dragonly
Copy link

I am running Win 10 Build 18363.
I have reas this could be a problem with the installed NFS Kernel modules.

There are no kernel modules (and no Linux kernel) in WSL1. Academically same #2869. NFS is available in WSL2 as of 20H1 aka version 2004 aka build 19041.

Thanks! Tested on Version 2004 Build 19041.610 and it works!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants