WSL: WSL automount failure
-
Your Windows build number: (Type
verat a Windows Command Prompt) Version 10.0.18362.113 -
What you’re doing and what’s happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
Created /etc/wsl.conf with automount options:
cat /etc/wsl.conf [automount] enabled = true options = metadata
terminated wsl with wsl.exe --terminate ubuntu
After wsl/ubuntu is launched, windows volumes are not mounted at all:
mount rootfs on / type lxfs (rw,noatime) none on /dev type tmpfs (rw,noatime,mode=755) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime) proc on /proc type proc (rw,nosuid,nodev,noexec,noatime) devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,gid=5,mode=620) none on /run type tmpfs (rw,nosuid,noexec,noatime,mode=755) none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime) none on /run/shm type tmpfs (rw,nosuid,nodev,noatime) none on /run/user type tmpfs (rw,nosuid,nodev,noexec,noatime,mode=755) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755) cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
dmesg [ 0.010291] Microsoft 4.4.0-18362.1-Microsoft 4.4.35 [ 0.113173] <3>init: (1) ERROR: UtilCreateProcessAndWait:360: /bin/mount failed with status 0 [ 0.113181] 2000 [ 0.113492] <3>init: (1) ERROR: LogException:23: FS: Could not start file system server. Operation not permitted @.\plan9.cpp:33 (TranslatePath) [ 0.133961] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Program Files\WindowsApps\CanonicalGroupLimited.UbuntuonWindows_1804.2019.521.0_x64__79rhkp1fndgs [ 0.134017] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Windows\system3 [ 0.134081] init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Windows [ 0.134127] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Windows\System32\Wbe [ 0.134180] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Windows\System32\WindowsPowerShell\v1.0 [ 0.134227] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Windows\System32\OpenSSH [ 0.134288] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Program Files\Git\cm [ 0.134335] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Users\e\AppData\Local\Microsoft\WindowsApp [ 0.134382] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Users\e\AppData\Local\Programs\Microsoft VS Code\bi [ 0.134442] <3>init: (4) ERROR: UtilTranslatePathList:2154: Failed to translate C:\Users\e\AppData\Local\hyper\app-3.0.2\resources\bi
- What’s wrong / what should be happening instead:
Windows volumes should be auto mounted with metadata option.
Thank you.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 9
- Comments: 66 (12 by maintainers)
Thank you, I am on Version 2004 (OS Build 20241.1000) same issue.
I ran powershell as admin
then I restarted my pc and wsl mounted correctly on start up.
after upgrading to Microsoft Windows [Version 10.0.20201.1000] WSL2 failed to mount on startup.
wsl --updatefrom elevated account fixed it for meI have no .wslconfig on my %USERPROFILE% and still not work here.
+1
@SvenGroot has some recent fixes in this path that are on the way to Insider Fast.
I see these errors in dmesg: [ 0.480751] 9pnet_virtio: no channels available for device drvfs [ 0.480919] init: (1) ERROR: UtilCreateProcessAndWait:655: /bin/mount failed with status 0x [ 0.480921] 2000 [ 0.480924] init: (1) WARNING: Retrying mount [ 0.582024] 9pnet_virtio: no channels available for device drvfs [ 0.582169] init: (1) ERROR: UtilCreateProcessAndWait:655: /bin/mount failed with status 0x [ 0.582171] 2000 [ 0.582174] init: (1) WARNING: Retrying mount [ 0.683198] 9pnet_virtio: no channels available for device drvfs [ 0.683335] init: (1) ERROR: UtilCreateProcessAndWait:655: /bin/mount failed with status 0x [ 0.683337] 2000 [ 0.683340] init: (1) WARNING: Retrying mount [ 0.784439] 9pnet_virtio: no channels available for device drvfs [ 0.784581] init: (1) ERROR: UtilCreateProcessAndWait:655: /bin/mount failed with status 0x [ 0.885625] 9pnet_virtio: no channels available for device drvfs [ 0.886468] 9pnet_virtio: no channels available for device drvfs [ 0.987671] 9pnet_virtio: no channels available for device drvfs [ 1.089109] 9pnet_virtio: no channels available for device drvfs [ 1.190361] 9pnet_virtio: no channels available for device drvfs [ 1.291645] 9pnet_virtio: no channels available for device drvfs [ 1.293035] 9pnet_virtio: no channels available for device drvfs [ 1.371163] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1.394202] 9pnet_virtio: no channels available for device drvfs [ 1.495491] 9pnet_virtio: no channels available for device drvfs [ 1.596787] 9pnet_virtio: no channels available for device drvfs [ 1.698027] 9pnet_virtio: no channels available for device drvfs
Your wsl.conf should be multiple lines, like this:
Same issue
+1. thx all, any ideas when this is solved. all my work is stopped because no distro is working now!
Any solution in between to work! we had also docker integrated with wsl 2. and after last windows update, not work any more!
however manual mount works just fine:
This fixed it for me, TYVM!
@ted-marozzi wrote:
Verified that this worked for me…
In my case I didn’t need the elevated powershell (probably due to the way I installed WSL).
UPDATE: a full system restart with 20175 solved the problem.
Getting the dmesg failure under U18 after a recent update: [ 0.018751] Microsoft 4.4.0-20175.1000-Microsoft 4.4.35 [ 0.303534] <3>init: (1) ERROR: UtilCreateProcessAndWait:652: /bin/mount failed with status 0 [ 0.303557] 2000
WSL1.
However my windows mount is properly mounted in every way I can see. No /etc/wsl.conf file, I was wondering if I had an old smb mount around somewhere, but I don’t have an fstab. I was experimenting with mounting samba servers through WSL but I don’t think it was on this machine / WSL instance. It would be nice if the error message said which /bin/mount entry, or is that always the root?
Yes, this sounds like a known issue with UAC off and the built-in Administrator that has already been fixed in later builds. Please keep an eye on the insider release notes for the fix, and try again afterwards.
@eugenetaranov, this has nothing to do with the original issue. Sorry for hijacking your thread. Please check my post above about wsl.conf formatting to see if that resolves your problem.
@SvenGroot
If I turn UAC to Level 3 (from top), WSL won’t be started. Then, I turn UAC to OFF again (restart PC), WSL working normally now.
(Tested on Normal Account)
@KayLeung Can you please send me the entire log of a clean start (after running
wsl --shutdownand starting a distro).I was able to resolve this by removing/renaming the config file at %USERPROFILE%.wslconfig , and shutting down wsl (wsl --shutdown) . After starting it again Ubuntu was able to mount properly.
I found this workaround here: https://github.com/microsoft/WSL2-Linux-Kernel/issues/91#issuecomment-632233488