Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mounting partitions fails in WSL 2 #11955

Closed
1 of 2 tasks
Lingchen218 opened this issue Aug 24, 2024 · 5 comments
Closed
1 of 2 tasks

Mounting partitions fails in WSL 2 #11955

Lingchen218 opened this issue Aug 24, 2024 · 5 comments

Comments

@Lingchen218
Copy link

Lingchen218 commented Aug 24, 2024

Windows Version

版本 10.0.22631.4037]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

ubuntu 2022

Other Software

No response

Repro Steps

First, I cannot view the version by typing wsl --version in the command line.
Second, when I execute wsl --mount \.\PHYSICALDRIVE0 --bare, it prompts that the disk is occupied. How do I solve this problem? My Windows system is in PHYSICALDRIVE1. PHYSICALDRIVE0 has an ext4 partition and an NTFS partition. I want to load the ext4 partition in PHYSICALDRIVE0.

Expected Behavior

I want to load the ext4 partition in PHYSICALDRIVE0.

Actual Behavior

When I execute wsl --mount \.\PHYSICALDRIVE0 --bare, it prompts that the disk is occupied. How do I solve it?
image

Diagnostic Logs

No response

Copy link

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 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, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] 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!

Closed similar issues:

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

@Lingchen218
Copy link
Author

Copy link

Diagnostic information
Appx package is not installed

@OneBlue
Copy link
Collaborator

OneBlue commented Sep 11, 2024

@Lingchen218: I wonder if that device is your boot disk. Can you share the output of gwmi Win32_BootConfiguration inside a powershell window ?

Copy link
Contributor

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-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants