Either use another operating system that won't suggest to format RAW media storage, somehow configure your OS to not mention to format, or create a VC container volume on your USB instead encrypting the entire device. To be clear, this is not a VC issue, but a thing of convenience for technical inepts. This way they can make a new RAW media storage usable without too much hassle. Greets
Do try to open volumes created with TrueCrypt? In this case, afaik, support for those was dropped. Have you tried to mount the volumes using the VC GUI? What does it have to say to those volumes? Greets
For your first command, regarding the documentation, it should be two backslashes before the question mark: /v \?\Volume{...}\ Regarding the 2nd command, you wrote "veracryypt". Anyway, you could try your commands directly on the CLI to make sure, they work as expected. Maybe something helpful comes up there. Additionally, have a look at the changelogs to make sure, no incompatibilities regarding your volume itself was introduced by, e.g., now deprecated algorithms. Greets
I'm not a Windows guy, but I would assume, that you should not execute "Device.exe" but "veracrypt.exe" to work on volumes. VeraCrypt documentation about CLI usage: https://veracrypt.fr/en/Command%20Line%20Usage.html Hope, that helps. Greets.
Please elaborate in more detail the initial system condition, what exactly you did and what you tried to achieve. Additionally, you should never need to copy EFI (partition?) to anywhere. Greets
Please provide more information about your system and what you did in which order to produce the message provided above. Additionally, how do you try to verify filesystem integrity, and what's even the filesystem to begin with? Please provide as much information as possible. Otherwise, all we can do is guess work. Greets.
Could you please provide some more detailed information on how you tried to recover from what kind of RAID drive? I don't think that you only use two storage devices for two RAID drives. RAID0 and RAID1 both need at least two independent devices. More complex variants need even more devices. Something's odd here. I would advise visiting a data recovery forum or something similar. After correct recovery of your container file, you could also try to mount using the backup header within your container...
On the third screenshot, it clearly states that there's a hardware issue with either your HDD or the cable connection. It's advisable to do further testing. Search the web for "HDD bad sector scanner" or similar. You could try again and see, if the message pops up again at the same stage of progress. In such case, it would be very likely faulty hardware. To continue with in-place encryption can lead to data loss, as stated in the messages. In any case, you should back up important data from this...