An error occurred mounting one of your file systems. Please run 'dmesg' for more details. #7565
Closed
1 of 2 tasks
Comments
|
Anuj-02 and me have the same issue #7565 after updating windows 10 to windows 11, but I have not found the solution yet. OS Name: Microsoft Windows 11 Professionnel I tried to previously uncheck the following functionalities in windows :
I rebooted for updated my PC. After rebooting, the installation of Ubuntu continued automatically: An extract of the alert / error message extracted from dmesg command: I also tried to update and restart the wsl service via command line : (Kernel version: 5.10.60.1) I also tried to restart the service LxssManager via the command: I have no wsl.conf file in my Ubuntu distribution (/etc/wsl.conf) When I try to mount the C drive directly in shell, i have the same issue This did not solve my problem. As my drive was initially crypted with Bitlocker service, il tried to put the encryption off. This did not change the issue. Anybody have an idea to solve our problem ? |
Closed
1 task
|
What kind of set up is your drive in? Is it encrypted? I see mention of BitLocker above and that changing it didn't help this error. Also could you please collect logs? /logs |
|
Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it. Thank you! |
ghost
added
the
@craigloewen-msft My hard drive has 4 partitions one of which I've encrypted with window's bitlocker. But whenever wsl2 starts it starts by displaying this message
On examining the output of dmesg, the following errors are seen: |
|
Tagging @OneBlue here, does the info above of dmesg give us enough to debug this? |
|
This is most likely a caused by bitlocker. @Anuj-02: Can you please share the output of the following command (as administrator) ?: |
|
@OneBlue Here is the result after running |
|
Anybody helped me to solve my problem. Please check if the path to the WSL kernel is correct in the .wslconfig file (C:\users\UserName\ .wslconfig). Kernel should be located within C:\WINDOWS\System32\lxss\tools\kernel Content of my valid .wslconfig file : @Anuj-02 check if it could help you. |
|
@Anthony-Biget - you need to escape |
|
Had the same issue as @Anuj-02 As soon as I removed the drive letter using Disk Management, then |
|
I don't have any partitions encrypted with BitLocker, but since I upgraded to Windows 11, this error appear to me. |
|
I get this error for 2 drives that have bitlocker enabled and I have not unlocked. I basically have separate windows installs on my machine and don't want to unlock those drives for isolation/security purposes. I don't have any idea how the WSL drive mounting works but I would say that the windows side of the mounting should only enumerate bitlocker drives that are already unlocked. |
|
no bitlocker same issue dmesg output https://gist.github.com/wkrueger/50536d6fe8773f0381455b9c061c1881 |
|
okay found it. I had the docker WSL distribution set as default. Changed it to Ubuntu and it worked. |
Solution from @wkrueger did also work for me... Output on my machine: |
|
Guys my problem was that it was trying to mount on my backup drive (HD). Since I didn't have anything stored there, I simply deleted the volume and leave only my primary drive allocated (SDD) and the error stopped. Why does it tried to mount on my secondary drive I don't know. |
|
Also started to get this. For me, it's the same reason as @jonstelly: I recently added a new partition, always locked, for security purposes, only to be unlocked on demand by me, and locked straight after doing specific work there. @craigloewen-msft Is it maybe an idea to add support in the |
|
Would like to add that if you had any additional drives that are meant to be hidden but for some reason weren't, then follow this answer on superuser.SE to hide that particular drive, thereby preventing Ubuntu from trying to mount. Command used (elevated Windows terminal): I was able to remedy the |
|
I had the same issue with wsl2 startup. In my case, it was the Windows 11 ESP drive that was causing the error. The solution was easy because I had no desire to mount this drive anyway:
|
Same issue Win 11, (DE) -WSL Ubuntu
|
2 tasks
2 tasks
|
Well, my distro is installed to my C: drive, which is bitlocker protected, but which is auto-unlocked upon boot (or logging in?). Anyway, I depend on the "automatic mounting" of Windows drives in WSL and I have an external D:\ drive also encrypted with BitLocker. What's annoying, is that after a hibernate/sleep/reboot, the drive is "Locked". So then, my WSL session no longer has access to my D:\ drive. Which really messes up my workflow with multiple tmux panes and vim sessions. While this isn't a "showstopper" because there is a way to "re-establish" the mount, it's definitely a workflow/quality-of-life issue. It is possible to re-mount the drive. However, it is not possible to unmont the existing mount because, essentially, the handle to the drive is bad, and so umount doesn't work. (NOTE: after running Windows for a long time, and several "remounts" later, I do believe there is some sort of "memory leak" that occurs, because the amount of memory used by the # If you're already in a directory on the now invalid drive, CD out of it...
$ cd /mnt
# Hopefully I got the ordering of the mount point/source correct--if not,
# let me know and I can update the example
$ sudo mount -t drvfs -o uid=1000 -o gid=1000 /mnt/d D:
$ cd /mnt/dThat should be it. I've been having to do this several times now for at least the last year because of bitlocker.
It would be nice if there was a way to somehow automatically "Reconnect" this mount point--but I don't know if that's technically possible—maybe something akin to a "weak reference" that can be automatically "refreshed" when it's found to be invalid? |
|
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
22000.258
WSL Version
Kernel Version
5.4.72
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Error occurs when a WSL session is started (i.e. wsl.exe is executed) even if WSL is already running in the background, with the message An error occurred mounting one of your file systems. Please run 'dmesg' for more details. being displayed.
On examining the output of dmesg, the following errors are seen:
[ 13.598350] init: (1) ERROR: MountPlan9WithRetry:285: mount drvfs on /mnt/d (cache=mmap,noatime,msize=262144,trans=virtio,aname=drvfs;path=D:\;uid=1000;gid=1000;symlinkroot=/mnt/ [ 13.598353] ) failed: 13 [ 13.600717] 9pnet_virtio: no channels available for device drvfsand the automatic drvfs mount of /mnt/ is missing. The same errors are repeated if an immediate attempt to mount the drive manually is made, but if one is made after several minutes, it succeeds without logging additional errors.
NOTE : I think one of my drives is locked with bitlocker so getting this error.
Expected Behavior
automatically mounted as user without error.
Actual Behavior
mounted as root with error "An error occurred mounting one of your file systems. Please run 'dmesg' for more details."
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: