since the update to Virtualbox 5.2 I cannot mount a veracrypt container from a shared folder. Also if I want to create a new one I get the same error.
Veracrypt Error Message:
- Code: Select all Expand viewCollapse view
Input-/Output error:
/dev/mapper/veracrypt1
The drive is damaged (there is a physical defect on it) or a cable is damaged, or the memory is malfunctioning.
Please note that this is a problem with your hardware, not with VeraCrypt. Therefore, please do NOT report this as a bug/problem in VeraCrypt and please do NOT ask for help with this in the VeraCrypt Forums. Please contact your computer vendor's technical support team for assistance. Thank you.
Note: If the error occurs repeatedly at the same place, it is very likely caused by a bad disk block, which should be possible to correct using third-party software (note that, in many cases, the 'chkdsk /r' command cannot correct it because it works only at the filesystem level; in some cases, the 'chkdsk' tool cannot even detect it).
VeraCrypt::File::ReadAt:306
The same was working without any problems in Linux guests (e.g. Ubuntu 17.10) with Virtualbox 5.1 and it is also still working in Windows guests with Virtualbox 5.2.
So this problem seems to be a regression in Linux Guests with Virtualbox 5.2 only.