-
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
WSL2 keeps trying (and fails) to mount ESP partition #9122
Comments
I Updated WSL to kernel |
Did you mount the ESP manually? Can you unmount it? |
No I didn't do anything about mounting. I cannot unmount it since it failed mounting. |
I mean unmounting the ESP from Windows side. For example, the command should be |
Is it very safe to unmount the ESP partition ? Wouldn't it break booting ? By the way, I tried the solution suggested here : #7565 (comment) but it doesn't work for me. |
That might be totally different topic. But it is not required to mount ESP for any cases. Booting is handled by system. |
Ok I did it, looks like it fixed my problem. But as said #8953 (comment), WSL shouldn't try to mount such partitions. Thank you for the help ! |
The same thing applies to user also. Users shouldn't try to mount such partitions in normal use cases :) |
Note that mounting manually caused a lot of issues with my files : unable to GIT clone on the C partition as well as having GIT doubting of the owning of files. Maybe the manual mounting requires to set metadata ? |
That's a different topic of mounting than this issue. You are probably asking about mount Windows partition in WSL. Then you can configure those options with |
Version
10.0.22621.755
WSL Version
Kernel Version
5.15.68.1-microsoft-standard-WSL2
Distro Version
20.04
Other Software
No response
Repro Steps
Drive context
I have a single 1TB NVMe SSD drive whith only Windows installed into it. When going to the disk management of my drive, I have 6 partitions :
Only the C:\ partition has a letter, but when opening Windows Explorer, I can see a F:\ partition of 146 MB (47.5 MB used) for which the access is denied.
Windows and WSL context
I installed WSL2 back when I had Windows 10 with a Ubuntu 20.04 distro. Recently I upgraded to Windows 11 and then run
wsl.exe --update
on Powershell as recommended.Expected Behavior
WSL2 should start as usual without any modification of its behavior. It should not be able to see this partition or trying to mount it.
Actual Behavior
Every time I start a new terminal with WSL, I got a
Failed to mount F:\, see dmesg for more details.
before the first prompt. I also noticed that the/etc/resolv.conf
was corrupted and I had to manually reset it to 8.8.8.8 and disable again its autogenerating at startup (#5420 (comment)).Here is the output of
ls -la /mnt
:I didn't find any workaround to fix this. Unmounting the drive is not possible as it has fail to mount. I don't know what are those other directories
d
,e
,h
.Diagnostic Logs
Content of the dmesg:
Here is the error:
The text was updated successfully, but these errors were encountered: