Error mounting /mnt/c after restarting Windows #4557
Comments
|
@m1ghtym0 I had the same issue, but the problem was solved by upgrading to 18990.1. |
|
@SvenGroot recently fixed this. |
|
I'm also seeing this symptom. Usually some time, after first interactive login. Running in the SLOW Ring. My problem is exacerbated by the terminal program I usually use, which copies a runtime instance into a working directory ( My environment$ wslsys
Release Install Date: 0x5df7fbbb
Branch: vb_release
Build: 19041
Full Build: 19041.1.amd64fre.vb_release.191206-1406
Uptime: 2d 19h 57m
Linux Release: Ubuntu 18.04.3 LTS
Linux Kernel: Linux 4.19.84-microsoft-standard
Packages Count: 1441`/etc/wsl.conf`# Enable extra metadata options by default
[automount]
enabled = true
root = /
options = "metadata,umask=22,fmask=11"
mountFsTab = true
# Enable DNS - even though these are turned on by default, we’ll specify here just to be explicit.
[network]
generateHosts = true
generateResolvConf = true
[interop]
enabled = true
#appendWindowsPath = true
appendWindowsPath = false
# vim: tabstop=2 shiftwidth=2 expandtab filetype=dosini syntax=dosiniSymptom$ df
df: /c: Input/output error
df: /d: Input/output error
df: /g: Input/output error
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb 263174212 27836984 221899072 12% /
tmpfs 4668488 0 4668488 0% /wsl
tools 194436380 166102560 28333820 86% /init
none 4666012 0 4666012 0% /dev
none 4668488 8 4668480 1% /run
none 4668488 0 4668488 0% /run/lock
none 4668488 0 4668488 0% /run/shm
none 4668488 0 4668488 0% /run/user
tmpfs 4668488 0 4668488 0% /sys/fs/cgrouppartial workaround$ sudo umount /d && sudo mount -t drvfs D: /d -o metadata,umask=22,fmask=11
$ df /d
Filesystem 1K-blocks Used Available Use% Mounted on
D: 270996476 178935352 92061124 67% /d
$ mount
..
D: on /d type 9p (rw,relatime,dirsync,aname=drvfs;path=D:;metadata;uid=1000;gid=1000;umask=22;fmask=11;symlinkroot=/,mmap,access=client,msize=65536,trans=fd,rfd=3,wfd=3)dmesg log
system bootfailing mountsVirgil |
|
Same here on build I have the |
|
Updating to |
|
I just started to get this same error on WSL2 and I'm on |
|
Given this shiped insiders in October 2019, whateverwas addressed made 2004 aka 20H1. If folks are still seeing similar errors in dmsg please spin up a new issue. |
2 tasks
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
If you have a feature request, please post to the UserVoice.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".
Please fill out the below information:
Your Windows build number: Microsoft Windows [Version 10.0.18980.1]
What you're doing and what's happening:
* Open Ubuntu 18.04 wsl 2
*
/mnt/cis empty:What's wrong / what should be happening instead:
dmesg gives:
See our contributing instructions for assistance.
The text was updated successfully, but these errors were encountered: