Timelessprod
commented
1 year ago I Updated WSL to kernel 5.15.74.2-microsoft-standard-WSL2 and OS Ubuntu 20.04.5 LTS on Windows 10 x86_64 but the problem is still there.
Closed Timelessprod closed 1 year ago
Timelessprod
commented
1 year ago I Updated WSL to kernel 5.15.74.2-microsoft-standard-WSL2 and OS Ubuntu 20.04.5 LTS on Windows 10 x86_64 but the problem is still there.
Biswa96
commented
1 year ago Did you mount the ESP manually? Can you unmount it?
Timelessprod
commented
1 year ago 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.
Biswa96
commented
1 year ago I mean unmounting the ESP from Windows side. For example, the command should be mountvol F: /D in your case. Run wsl.exe --shutdown and that mountvol command as administrator.
Timelessprod
commented
1 year ago Is it very safe to unmount the ESP partition ? Wouldn't it break booting ?
By the way, I tried the solution suggested here : https://github.com/microsoft/WSL/issues/7565#issuecomment-1227496759 but it doesn't work for me.
Biswa96
commented
1 year ago That might be totally different topic. But it is not required to mount ESP for any cases. Booting is handled by system.
Timelessprod
commented
1 year ago Ok I did it, looks like it fixed my problem. But as said https://github.com/microsoft/WSL/issues/8953#issuecomment-1304721429, WSL shouldn't try to mount such partitions.
Thank you for the help !
Biswa96
commented
1 year ago WSL shouldn't try to mount such partitions.
The same thing applies to user also. Users shouldn't try to mount such partitions in normal use cases :)
Timelessprod
commented
1 year ago 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 ?
Biswa96
commented
1 year ago 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 /etc/wsl.conf file as documented here https://learn.microsoft.com/en-us/windows/wsl/wsl-config
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 --updateon 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.confwas corrupted and I had to manually reset it to 8.8.8.8 and disable again its autogenerating at startup (https://github.com/microsoft/WSL/issues/5420#issuecomment-645208552).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: