On the other hand, if VeraCrypt properties dialog doesn't indicate that the volume is read-only, then there maybe an issue with fuse itself.but this is less probable.
In this case, can you check your system logs to see if the kernel loads the drive as read only or if there are any errors linked to this drive.For example, some RAID 1 drives can revert to read-only after rebooting (you can many issues linked to this on the internet). If yes, then since you didn't select the "read only" option either through the command line or the password dialog, the only left possibility is that VeraCrypt receives an Read-only filesystem error when trying to open the volume (error codes are: EROFS, EACCES or EPERM) as you can see in the code: When you display the volume properties using VeraCrypt, does it show that it is read-only?
The original poster for the issue on Windows didn't come back with more information which is frustrating.Anonymous posters tends to forget to give feedback.
0 kommentar(er)
