-
Notifications
You must be signed in to change notification settings - Fork 835
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
Processing fstab with mount -a failed for bound directories #9321
Comments
Thanks for reporting this @3axap4eHko. Can you share the output of |
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging Thank you! |
@OneBlue this is `dmesg` right after the fail
|
logs from the script |
@3axap4eHko the relevant info is:
If you use the |
@elsaco do you think this is the correct behavior when WSL is not ready before running
|
Closing since this issue has been resolved. |
This issue has not been resolved, a work around was implemented. I have the same issue. I setup an nfs mount in my fstab file, and it works fine, but every time I open a terminal/shell I get the error message. I do also have docker installed and it shows up in the list of distros. I'm not sure if that's related, but my ubuntu distro is the default. |
same problem here. I use task schedular to mount the physical disk with highest priviliage, then mount it with fstab and UUID. I can access the disk properly, but the error message appeared and it's annoying.
|
Version
Microsoft Windows [Version 10.0.22621.900]
WSL Version
Kernel Version
5.15.79.1
Distro Version
Ubuntu 22.04
Other Software
N/A
Repro Steps
sudo mount -a ll ~/projects
Processing fstab with mount -a failed.
even if the directory is already mountedsudo mount -a
Expected Behavior
Automatically mount fstab
Actual Behavior
does not mount automatically, requires manual running
sudo mount -a
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: