kirk-marple commented 1 day ago

Windows Version

Microsoft Windows [Version 10.0.26100.2152]

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 24.04

Other Software

WSL version: 2.3.24.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2152

Repro Steps

For months I've been running WSL2/Ubuntu, and accessing folders on my Win11 Dev Drive through VS Code Remote.

My Win11 laptop rebooted last night, and then today I can't access anything on that Dev Drive through VS Code/WSL2 Remote.

I've tried uninstalling the distro and reinstalling; tried remounting the drive... nothing works.

I see some older bugs similar to this, but they have been closed with no solution.

Expected Behavior

Same access to Dev Drive files using VS Code/WSL2.

Actual Behavior

My d: drive (Dev Drive) is no longer accessible through VS Code/WSL2.

Looking at the mounts, the d: drive is obviously messed up.

kirk@DEV-USSEASUR6:/mnt$ ls -l
total 0
drwxrwxrwx 1 kirk kirk 4096 Oct 11 15:28 c
d--------- 0 kirk kirk    0 Dec 31  1969 d
drwxrwxrwt 2 root root   60 Oct 11 16:13 wsl
drwxrwxrwt 7 root root  300 Oct 11 16:14 wslg

Here's my wsl.conf:

kirk@DEV-USSEASUR6:/mnt$ cat /etc/wsl.conf
[boot]
systemd=true

Diagnostic Logs

VS Code logs:

[2024-10-11 23:28:43.545] Extension version: 0.88.4
[2024-10-11 23:28:43.546] L10N bundle: none
[2024-10-11 23:28:43.575] authorityHierarchy: wsl+ubuntu
[2024-10-11 23:28:43.575] WSL extension activating for a local WSL instance
[2024-10-11 23:28:43.591] Resolving wsl+ubuntu, resolveAttempt: 1
[2024-10-11 23:28:43.591] NodeExecServer run: C:\WINDOWS\System32\wsl.exe --status
[2024-10-11 23:28:43.638] WSL feature installed: true (wsl --status)
[2024-10-11 23:28:43.638] NodeExecServer run: C:\WINDOWS\System32\wsl.exe --list --verbose
[2024-10-11 23:28:43.679] 1 distros found
[2024-10-11 23:28:43.680] Starting VS Code Server inside WSL (wsl2)
[2024-10-11 23:28:43.680] Windows build: 26100. Multi distro support: available. WSL path support: enabled
[2024-10-11 23:28:43.680] Scriptless setup: false
[2024-10-11 23:28:43.680] No shell environment set or found for current distro.
[2024-10-11 23:28:43.776] WSL daemon log file: 
[2024-10-11 23:28:43.778] Connecting to daemon started by other WSL window... 5.15.153.1-microsoft-standard-WSL2 Ubuntu
[2024-10-11 23:28:43.778] WSL resolver response: 127.0.0.1:51854
[2024-10-11 23:28:43.778] To debug connection issues, open a local browser on http://127.0.0.1:51854/version
[2024-10-11 23:28:43.792] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e /home/kirk/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '127.0.0.1', port: 34255 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-11 23:28:43.868] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e /home/kirk/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '127.0.0.1', port: 34255 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-11 23:28:44.090] Download in background is enabled

github-actions[bot] commented 1 day ago

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

after wsl --update, can't mount C: windows drives in WSL2 (#11812), similarity score: 0.79
Lost access to Win 11 FS within WSL2 instances, <3>WSL (9) ERROR: UtilTranslatePathList:2671: Failed to translate issues? (#9481), similarity score: 0.77

Closed similar issues:

WSL broke after Windows update (#10831), similarity score: 0.77
Unable to mount a drive under wsl : An error occurred mounting one of your file systems (#7572), similarity score: 0.76
Error mounting /mnt/c after restarting Windows (#4557), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.