microsoft / microsoft/WSL

fstab error on mounted VHD drive

Open
#13,924 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

file system
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

### Windows Version

Microsoft Windows [Version 10.0.26200.7462]

### WSL Version

2.5.10

### Are you using WSL 1 or WSL 2?

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

6.6.87.2-microsoft-standard-WSL2

### Distro Version

RedHat 9.7

### Other Software

_No response_

### Repro Steps

wsl --mount --partition 1 --type ext4 --vhd C:\wsldata\wsldata.vhdx --name wsldata

in fstab

UUID=3a732601-db77-44f8-8149-cfede85cceb6 /mnt/wsl/wsldata ext4 defaults 0 0
/mnt/wsl/wsldata/home/developer /home/developer none bind 0 0

### Expected Behavior

No error for mounted data drive

### Actual Behavior

Dec 16 08:28:46 PBD-IT-WL-rOMw1 mount:
Dec 16 08:28:46 PBD-IT-WL-rOMw1 /mnt/wsl/wsldata: mount point does not exist.
Dec 16 08:28:46 PBD-IT-WL-rOMw1 unknown:
Dec 16 08:28:46 PBD-IT-WL-rOMw1 mount:
Dec 16 08:28:46 PBD-IT-WL-rOMw1 /home/developer: special device /mnt/wsl/wsldata/home/developer does not exist.
Dec 16 08:28:46 PBD-IT-WL-rOMw1 unknown:
Dec 16 08:28:46 PBD-IT-WL-rOMw1 unknown: WSL (2 - init-systemd(redhat)) ERROR: UtilCreateProcessAndWait:707: /bin/mount>
Dec 16 08:28:46 PBD-IT-WL-rOMw1 unknown: WSL (2 - init-systemd(redhat)) ERROR: ConfigMountFsTab:2172: Processing /etc/f>

plus the well know message on login:

wsl: Processing /etc/fstab with mount -a failed.

and eventually I have that drive and use it!

This is the same with 6.x. Some version doesn't print it, but journalctl has it for any WSL above 2.4

### Diagnostic Logs

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported `wsl --mount` command with the shown `/etc/fstab` entries for `/mnt/wsl/wsldata` and the bind mount. Review the `mount -a` output and `journalctl` messages, then compare behavior across the mentioned WSL versions. Done means the mounted VHD and bind mount process without the reported fstab errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.