Windows 10 Build 16299

GNU Bash Version 4.3.11

VeraCrypt 1.19

Previously, I had an encrypted container mounted on the H: of my machine, which I could access with both the Explorer window and cmd line (e.g. user@host:/mnt/h/[folders and files]) alike, no problem.

However, I recently created a new encrypted container and mounted it to the R: drive, and I am now unable to access EITHER drive directories from the command line.

Using WSL bash from the command line terminal:

  • cd /mnt/c shows all of my C: folders and the full file directory
  • cd /mnt/h takes me to H:, but [ ls -l ] shows a total of 0 files underneath -- should have 6 folders and 1 file
  • cd /mnt/r takes me to R:, but shows a total of 0 files under -- should have 7 folders and 5 files

Both drives are FAT32 format, and I know about the issue being only NTFS drives working in WSL; but this was working previously, no problem, when I had only the single H: mounted and now I cannot figure out how to get access to the folders/files from the command line?

image of mnt options

Again, I used to be able to access, read, write files using commands like

'cat /mnt/h/dir1/technology/folder1/sub-folder2'

no problem.

  • Are you saying that the volumes are accessible through Windows Explorer? – Scott Apr 24 '18 at 2:02
  • Also try this command ls -lash /mnt/h . – Biswapriyo Apr 24 '18 at 10:37
  • @Scott - yes, I can access all files in h: and r: from windows explorer – user8087995 Apr 24 '18 at 14:01
  • @Biswapriyo - they are both virtual encrypted containers, setup and accessed/mounted using VeraCrypt – user8087995 Apr 24 '18 at 14:01
  • @Biswapriyo - I did, and all I see are the '.' and '..' directory inodes – user8087995 Apr 25 '18 at 15:53

Wow - So I had changed the property of the encrypted file on my SSD to 'read-only' to protect from an inadvertent deletion of the container...

When VeraCrypt was mounting the container, it carried over the 'read-only' property. Surprisingly, it also meant that I couldn't read or list any of the folders/files within the wsl/bash terminal...

I unchecked the 'read-only' value in the windows properties dialogue box, remounted the drive, and it's working.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.