External drive --mount in WSL2 yields "The system cannot find the file specified." #6910
Comments
|
I have the same problem |
|
Me too |
|
Same problem here on my Surface Pro X (Windows 11 Pro 22000.318) also trying to mount a vhdx virtual disk: Is it an arm64 related issue? |
|
Using this alternative worked for me: |
|
I'm having the same issue. I'm not suspecting this to be an ARM64 specific problem as I'm currently experiencing this on an AMD64 machine. |
|
Same problem here... Windows 10.0.22000 On top of command not working, it also "Ejects" the drive as a side effect. |
|
Same problem here. @dmitry-ovon You can bring back the drive using following command: |
|
I'm getting the same problem trying to mount an SD card over USB in Windows 11 22000.593 |
|
Same thing here while trying to mount an USB disk with 2 partitions (one of them is Lukys encrypted) with ext4 filesystem I'm on Windows 11 and my CPU has an x86 arch (so, it is not related to ARM) |
|
Hi all. Same error. |
|
Same issue here. The removable media (SD card in a USB reader) has a FAT32 partition and an EXT4 partition. It is unmountable on my AMD64 (Ryzen 5600X) machine. Additionally, the drive ejects in Win11 when I attempt the wsl --mount command. |
|
Same problem here.
|
|
This issue is already over a year old, any updates @craigloewen-msft ? |
|
Tagging @OneBlue here for visibility! |
|
I am having the same problem on W11 22622.436 |
|
Same problem on Win11 (21H2 22000.832), and ArchWSL. Administrator in C:\Arch
❯ Get-CimInstance -ClassName Win32_Processor | Select-Object -ExcludeProperty "CIM*"
DeviceID Name Caption MaxClockSpeed SocketDesignation Manufacturer
-------- ---- ------- ------------- ----------------- ------------
CPU0 AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx AMD64 Family 23 Model 24 Stepping 1 2600 FP5 AuthenticAMD
Administrator in C:\Arch
❯ GET-CimInstance -query "SELECT * from Win32_DiskDrive"
DeviceID Caption Partitions Size Model
-------- ------- ---------- ---- -----
\\.\PHYSICALDRIVE0 ADATA SX6000LNP 3 256052966400 ADATA SX6000LNP
\\.\PHYSICALDRIVE1 Kingston DT 101 II USB Device 1 8027873280 Kingston DT 101 II USB Device
Administrator in C:\Arch
❯ wsl --mount \\.\PHYSICALDRIVE1
The system cannot find the drive specified.
Administrator in C:\Arch
❯ wsl --mount \\.\PHYSICALDRIVE1 --bare
The system cannot find the drive specified. |
|
In my case, a SDXC card in a reader will neither mount in WSL2 via --mount nor using the /etc/fstab route:
It is formatted NTFS, normally not a problem to refer to it as /mnt/e. Linux (dual booted) sees this partition as /dev/mmcblk0p1 and mounts it fine. WSL seems crankier about it ... Here's the output from dmesg, not helpful to me at least:
Possible (bad) interaction with Antivirus in Windows? Seems that way to me. |
|
same problem for me after the updates on 12th January. Still looking for a resolution to it. |
|
/logs |
|
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt: The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging Thank you! |
ghost
added
the
|
There are some problems with the Docker desktop that uses WSL 2 backend as the based engine. I do some workaround such remove the linux distro and WSL 2 I'm using and reinstalled it again. However, in the distribution installation step, I got:
I've spent several hours tried to troubleshoot it but still stuck on it. |
|
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it. Thank you! |
|
Why was this issue closed? It's still a problem. I can't mount/access an SD Card with wsl. Logs attached. |
|
This continues to be a problem. |
|
Have the same problem, i always make an image from the drive, then mount the image as loop, after work i flash the image back to the drive. Will this be ever solved????? |
Seems to be closed because I didn't reopen it or reply with logs (which I thought I provided in the OP, but seemingly didn't). I'll dust off my Pro X and collect some logs tomorrow and reopen the issue. |
|
This exact issue has been reported in various places for over 2 years. It's clear most of these folks are dealing with a Raspberry Pi (SD card, 2 partitions, fat32 and ext4). It's ludicrous that someone in Redmond hasn't taken the 10 minutes necessary to repro this issue then step their code to see what's broken. Of course, fixing it would enable all these people to successfully and easily use a different device with a different OS, so after 40 years, Microsoft is still...Microsoft. |
|
Yes, exact same issue here. Raspberry Pi SD card and |
I have exactly the same problem |
|
I have the same issue using AM5 platform Windows 11. It works on my Intel gigabyte laptop Windows 11. |
|
Posting to reopen this, happens for me too. Surprised there's not an automated test in place to check this functionality given how new WSL2 is. The Microsoft Learn Article documenting this was updated March 20th. |
|
Hi all. I have the same problem and still did not find out how to actually solve it, as far as the built-in SD card reader of my laptop is concerned. However, I found a workaround with an external USB SD Card reader and this awesome video: |
|
Unfortunately, this is currently unsupported. From https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk:
Which indicates the use of a third-party open source utility called usbipd-win. |
nice |
That explains, cool, and thanks for the usbipd-win link - good stuff! |
|
I'm using it here to decrypt a LUKS-encrypted USB stick. It works good. The only downside is having to compile the WSL kernel with USB storage support. |
|
I'm having the same issue: Want to write an image file with Win32 Disk Imager under Win11 from a Raspi SD card, but only the NTFS partition shows up, not the ext4 one. Used to work under Win10 |
|
Same issue, disappointing it hasn't been fixed in three years.
|
|
Haha the internet is packed full of people complaining about this. It's actually hilarious it's taken years. I wonder if Microsoft is doing an experiment to see how long people will keep trying when they won't fix the solution to their bugs. The answers website is spammed with these questions too. In concept it seems fairly trivial to fix this- what would cause an ext4 mount failure? I know Windows generally needs a running driver to access ext* filesystems so I presume the solution must be in a driver somewhere. It's definitely not trivial to translate a filesystem although mounting, I think, shouldn't be too hard. I wonder if it's a problem with the partitions? Has anyone succesfully mounted an EXT* filesystem via USB with ONE partition? Just curious.. |
|
How the fuck has this still not been fixed? |
|
i overcome it by making image if the drive i want to modify (HddRawCopy), mount it in loop in WSL/Ubuntu, modify, unmount, reimage. What a pain in the ass. Trying to leave windows now, going to macOS or ubuntu. |
|
yk how I overcame this? I used Linux bare metal 🤷♂️ In my case I used a RPi4 to create the image I wanted to create from WSL first. It has the same arch, was able to do my stuff. Still baffled that this isn't solved. Maybe its an architectural issue with WSL2 VMs. |
|
This is still an issue and not "closed" - Same problem here. |
Create a new one and tag this, I can't reopen it afaics |
that's hacky as fu*ck but it's clever. |
|
Why on Earth was it closed? |
|
Same problem with RPi image....damn, why its closed... |
|
Same problem with USRP N300 SD-card. Now I need to search normal Ubuntu laptop to flash it. |
and others
Windows Build Number
10.0.21370.1 (ARM64 / Surface Pro X)
WSL Version
Kernel Version
5.4.72
Distro Version
No response
Other Software
No response
Repro Steps
Expected Behavior
A mounted block device in WSL
Actual Behavior
WSL returns
The system cannot find the file specified.Diagnostic Logs
ETL-file captured logs: etl-file.zip
The specific error from the ETL-file seems Hyper-V related:
[ { "ResourcePath": "VirtualMachine/Devices/Scsi/0/Attachments/2", "RequestType": "Add", "Settings": { "Type": "PassThru", "Path":"\\\\.\\PHYSICALDRIVE1" } }, { "Error": -2147024894, "ErrorMessage": "The system cannot find the file specified.", "ErrorEvents": [ { "Message": "'Virtual Machine': Attachment '\\\\?\\usbstor#disk&ven_wdc_wd64&prod_00bevt-22a0rt0&rev_#20151222&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}' could not be found due to error: 'The system cannot find the file specified.' (0x80070002). (Virtual machine ID A1BB5BC7-228E-4484-83F3-21AC60FADE15)", "Provider": "edacd782-2564-4497-ade6-7199377850f2", "EventId": 12240, "Flags": 5, "Data": [ { "Type": "String", "Value": "Virtual Machine" }, { "Type":"String", "Value": "A1BB5BC7-228E-4484-83F3-21AC60FADE15" }, { "Type": "String", "Value":"\\\\?\\usbstor#disk&ven_wdc_wd64&prod_00bevt-22a0rt0&rev_#20151222&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}" }, { "Type":"String", "Value":"%%2147942402" }, { "Type":"String", "Value":"0x80070002" }, { "Type":"String", "Value":"Hyper-V Virtual Machine Management service" }, { "Type":"String", "Value":"" } ] } ] } ]The text was updated successfully, but these errors were encountered: