wsl mounts do not persist after a reboot.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Version
Microsoft Windows [Version 10.0.22000.469]
WSL Version
- WSL 2
- WSL 1
Kernel Version
Linux version 5.10.60.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Wed Aug 25 23:20:18 UTC 2021
Distro Version
Ubuntu 20.04.3 LTS \n \l
Other Software
No response
Repro Steps
wsl --mount \.\PHYSICALDRIVE1 --bare
(disk is mounted and available in WSL2.
reboot...
(disk is no longer mounted and available for WSL2).
Expected Behavior
A disk mounted for WSL2 should still be mounted after a reboot.
Actual Behavior
The mount is not preserved.
Note this issue has been raised in: https://github.com/microsoft/WSL/issues/6073 and https://github.com/microsoft/WSL/issues/6414.
However, both of those issues have been closed despite no resolution.
Diagnostic Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repro command, wsl --mount \\.\PHYSICALDRIVE1 --bare, and the related issues #6073 and #6414 to understand prior decisions. Reproduce the behavior across a reboot and trace the WSL mount lifecycle; done means the disk remains available after reboot without requiring the command again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100