Hello. I'm no more able to enter into a VeraCrypt container. This is what happened: after a files copy into it while I watched a video from the same container, suddenly it blocks (I know, it wasn't a good choice). I remember that the container was almost full during that copy, but without exceed the available space.

Anyway, I try to mount the device with VeraCrypt and this is the result:

mount: wrong fs type, bad option, bad superblock on /dev/mapper/veracrypt1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.

After digit "sudo dmesg | tail" this is the result:

[ 5292.889732] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[ 5292.889737] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 5292.889740] blk_update_request: I/O error, dev sdb, sector 0
[ 5292.889748] Buffer I/O error on dev sdb, logical block 0, async page read
[ 5292.889877] ldm_validate_partition_table(): Disk read failed.
[ 5292.889978] Dev sdb: unable to read RDB block 0
[ 5292.890096] sdb: unable to read partition table
[ 5292.902969] sdb: sdb1
[ 5342.351196] device-mapper: uevent: version 1.0.3
[ 5342.351314] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com

The drive is a Lexar 32 GB Micro SD, and I made the hidden container on the sdb1 partition with ext4 file system. I'm still able to restore the Volume Header with the VeraCrypt option "Volume Tools", but I'm not expert in these things so I can't understand what can I do for trying to recover the hidden container.

If can help, the hidden container was made on Debian 9 that I actually use, but this unespected thing happens in the last Tails version.