u/divergentchessboard

I've been using Cryptomator a lot, and one thing I do not like about it is that it doesn't matter how much parity you have for a file, if the encrypted .c9r file gets even a single block of data corrupted, then the decrypted file is entirely useless with no way to recover it.

if I encrypt a non-system partition with VeraCrypt, will it have the same weakness as Cryptomator to data corruption?

I am not necessarily worried about permanently losing data as I have multiple backups of all my important data. I am wondering if the parity files I'm creating are entirely useless if stored on a VeraCrypt drive.

I've been using a mix of VeraCrypt and Cryptomator to store various files on my local drives and cloud backup, and something that I noticed, at least with Cryptomator, is that if the .c9r file holding your encrypted data gets corrupted in any way, even if only a single byte of data gets corrupted, it's almost impossible to recover the data belonging to that file, even with parity files via par2, and generating hashes of those files to check for silent corruption every now and then seems entirely ineffective for some reason. Hashes need to be generated for the .c9r files instead of the decrypted data along with par2 files which is far from ideal

VeraCrypt itself has mostly worked fine so far, but I'm questioning how resilient it is to not losing all my data if the drive it's on encounters any sort of issue and takes all my data down with it due to damage to the VeraCrypt volume.

Is there no better way besides keeping backups of your containers on multiple drives hoping you don't eventually fall victim to silent corruption, and keeping a backup of your VeraCrypt header?

Building a new PC dedicated to running an OS with ZFS and ECC RAM is currently out of the picture due to RAM prices.

Topaz Video stores project data in its default user/documents/topaz folder. However, when upscaling videos, those files are stored in your systems temp folder via ffmpeg before being assembled and exported and not your project folder. This has caused an extreme level of tear on my system drive (10% health gone in a year) and the only solution I've found to this is changing where your temp folder is under system environment variables.

Reinstalled Windows due to a bugged 3rd party driver crashing my PC upon boot. Finished setup and got into Windows attempting to mount my storage drive (NOT windows partition) only for it to constantly say that it failed to mount due to "incorrect password, volume pin, blah blah"

https://preview.redd.it/nr91kmyvm9zg1.png?width=573&format=png&auto=webp&s=7cf8fc89f8745c0dce012eeee68bd555d738ecf6

I know the password is correct because I'm copy+pasting it from a password manager. Is the problem that the new drive (which was previously mounted as K:) no longer has the same drive letter due to Windows seeing it as a RAW unformatted drive so it no longer has a letter? and if so, how do I go about fixing that? Not sure what other options could be preventing it from mounting. I'm using the same portable VeraCrypt instance so its also the same version I used to encrypt the drive, and I left everything at default when I made the instance and dont remember doing anything like adding a PIM volume number as I never saw one with decrypting the drive