wsl --mount not working on arm64

[etxaleku]

Windows Version

Microsoft Windows [Version 10.0.26100.2314]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 22.04

Other Software

Existing issue #12038 was closed after waiting for logs.

WSL2 is from Windows Store and is up-to-date (ran wsl --update to be sure).
Windows 11 is up-to-date (ran Windows Update check for updates to be sure).

$ wsl.exe --version
WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
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.2314

Repro Steps

With WSL2 IO performance (and the Linux file security model) work much better for the native filesystem (ext4) though there is very much appreciated access to the Windows NTFS filesystems through the drvfs filesystem driver albeit at a slower IO rate.

To reproduce:

• WIndows 11 on ARM64 machine (Microsoft Surface Pro 11 in my case).
• WSL2/Ubuntu 22.04 installed from Microsoft Store.
• Use Windows Disk Management to Create VHD outside of WSL2, in my case on external D: drive connected via USB.
• In Powershell get the physical disk number by running
  Get-Disk
• Then try to mount the VHD by running
  wsl.exe --mount \\.\PhysicalDrive# --bare

In my case the drive number of the new VHD was 2 so I tried running
wsl.exe --mount \\.\PhysicalDrive2 --bare
in a variety of contexts:

• from my normal user in Ubuntu/WSL2
• from the root user in Ubuntu/WSL2
• from an Administrator elevated Powershell

I am generally trying to follow the steps outlined in https://joeferguson.me/adding-another-disk-to-wsl2/, though some of those steps are apparently outdated. Like the process to get the VHD drive number, so I eventually figured out that (these days) a simple Get-Disk in Powershell will interactively provide the number.

Expected Behavior

New VHD will mount into Ubuntu where an ext4 filesystem can then be created and the resultant ext4 filesystem can then be mounted and used for normal file handling from that point forward.

So basically now a df command in Linux would show the usual / (root ext4) filesystem, all the drvfs filesystems exposing the various NTFS Windows "drives", plus this new ext4 filesystem which happens to be on a different physical disk than the root filesystem. Expectation is that the IO performance of the new VHD would be similar to the root filesystem (after taking into account any physical limitations due to the disk characteristics and interfaces, e.g. SSD vs spinning, USB, etc).

Actual Behavior

PS C:\> wsl --mount \\.\PhysicalDrive2 --bare
wsl.exe --mount is not supported for ARM64 on this version of Windows.
Error code: Wsl/Service/WSL_E_WSL_MOUNT_NOT_SUPPORTED

also tried

PS C:\> wsl --mount --vhd D:\media\extdisk.vhdx --bare
wsl.exe --mount is not supported for ARM64 on this version of Windows.
Error code: Wsl/Service/WSL_E_WSL_MOUNT_NOT_SUPPORTED

Diagnostic Logs

Since this is a WSL --mount issue, tried to follow the guidance to run the wmic command but looks like that has been deprecated.

Running wmic diskdrive get Availability,Capabilities,CapabilityDescriptions,DeviceID,InterfaceType,MediaLoaded,MediaType,Model,Name,Partitions from an elevated command prompt resulted in -
'wmic' is not recognized as an internal or external command, operable program or batch file.

Attached logs from collect-wsl-logs.ps1.

WslLogs-2024-12-09_19-33-42.zip

[github-actions]

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:

• wsl --mount not working on arm64 (#12038), similarity score: 0.78

Closed similar issues:

• Error when mounting M.2 nvme ssd partition on WSL 2. Wsl/Service/AttachDisk/0x80070032 (#9324), similarity score: 0.81
• wsl.exe --mount is not supported on ARM64 (#9611), similarity score: 0.76
• Failed to attach disk (#10858), similarity score: 0.76
• wsl --mount not working (both --bare and --partition fail), "The request is not supported." (#9739), similarity score: 0.76

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

Diagnostic information

.wslconfig found
Detected appx version: 2.3.26.0
Detected user visible error: Wsl/Service/WSL_E_WSL_MOUNT_NOT_SUPPORTED

[etxaleku]

Powershell Get-Disk output

• Disk 0 is the internal 1TB SSD,
• Disk 1 is an external 4TB USB disk, and
• Disk 2 is the VHD created using Windows DIsk Management > Action > Create VHD.

The file path for the VHD is on Disk 1 (D:\media\extdisk.vhdx).

PS C:\> Get-Disk

Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition
Style
------ ------------- ------------- ------------ ----------------- ---------- ----------
2 Msft Virtual Disk Healthy Online 512 GB RAW
0 MZ9L41T0HBLB-00BMV-SAM... 0025_38E2_4100_A58A. Healthy Online 953.87 GB GPT
1 Seagate Expansion NA8P86N1 Healthy Online 3.64 TB GPT

[benhillis]

wsl.exe --mount on ARM64 requires Windows platform support which was added in version 27653.

[etxaleku]

Hmm, sounds like maybe a WIndows OS update is needed then? And I'm guessing that that version of Windows 11 has not been released yet. I am on the Microsoft Store version of WSL2 and thought that it was decoupled from Windows ... sounds like it was mostly decoupled but maybe not entirely (but as much as technically possible).