Sorry for the late reply. I can never tell how late I'm replying cause 8chan timestamps don't auto convert to my time zone, but I could've replied sooner had I not just felt sick about reading the exerpt of your earlier post I greentexted. I haven't even eaten today, but I couldn't even make myself eat. I know this is all my fault, but to me the blame is entirely on my mindset for my not being afraid of losing the data, and of the poor, decision-making after that point. I just hate that I was ever vulnerable. I don't know.
>Why did you have to decrypt the entire disk, you could just mount the veracrypt container and copy all files? Or were some files missing in your veracrypt container, you panicked and started to decrypt the disk before cloning it?
Please describe what happened in chronological order. What is the oldest possible state you have of any of the files involved?
Well, as you mentioned later in the post:
>Also, I think I remember you saying you have an old backup. So, between "only" losing 32GB + metadata, ability to (probably) restore with photorec and still having some old files that you can match with the current ones, you may actually have lost little data - your old hydrus db may actually contain a lot of subs...
Yes, I did mention in a previous thread that I might have a 500GB HDD, which would have been a several year old version of the boot drive (that had the bad sector), since after filling the 500GB HDD, I cloned it to a larger drive, and booted from the larger drive instead. But, I think I might not have the 500GB HDD anymore, since I started using my old HDDs as a secondary HDD. So provided it's not just formatted clean, it must only have the contents of my second HDD, which is where I put all my private data. If I have any hard drive with my boot HDD (where my hydrus was stored), it must be the 256GB or so HDD the laptop came with. But I distinctly remember using the 500GB HDD as a secondary HDD. I don't think there's any chance for it being a backup.
But otherwise, the only reason I decrypted the disk was because the program I used to clone/image ("Macrium Reflect") didn't work for veracrypt-encryption. Even in the past when I was using it to change my boot drive to a bigger hard drive, I had decrypted my boot drive first. I didn't know I had any other options, even though I had last checked several years ago. Even though I can't really cope with confronting the reality being that myself is the blame, to be fair, those several years ago when I searched how to clone/image, none of the articles I read that recommended the program I used mentioned veracrypt encryption; I viewed relatively few sources that actually mentioned the program and veracrypt in the same breath.
I didn't understand that corrupted data means the operating system considers it to be free space that can freely be overwitten by writing data. I know it seems obvious to assume as much, but I thought when I pressed "print screen", opened mspaint, pasted the fullpage screencap on my clipboard, and was unable to save it due to the fileystem being corrupt, that it means the operating system refused to overwrite the corrupt data. I don't know what I was thinking. I obviously would have only walked in a straight line of preserving my data had I had the insight I had now.
But another reason I decrypted the bad sector boot HDD (where my hydrus was stored) was because I was afraid if I shut it down, it wouldn't be able to be mounted again, because of the bad sector. Also the way you phrased it, of using the word "copy" at first (even though you later said "clone" in the same paragraph), it makes it sound like I could just copy my hydrus folder as soon as the corruption happened, and then perform recovery on the isolated copy. I thought I needed every sector of the dying HDD to perform recovery on, since anything corrupted started appearing as empty space to the OS. Also, because it was my boot HDD, I couldn't mount it unless I booted from it. My second HDD (with my private data [the HDD is still healthy]) actually came with Windows 10 installed, and at first I encrypted it by booting from it. But I couldn't mount it unless I booted from it. Unless veracrypt changed to support this retroactively-
or, sorry. Maybe even if I had to boot from my bad sector boot HDD to mount it, if I were able to perform a sector-by-sector clone of it before ever shutting it down (which the program I used ["Macrium Reflect"] was unable to do), I might've been able to clone it to a replacement HDD, then boot from that, and maybe it wouldn't have had any negative effects. I don't know. In the end, I just wish I hadn't been vulnerable. But being educated on how to properly compensate for the situation only helps.
>On the original disk, you now have the "decrypted" version of your data, which is what you cloned to the other disk?
>And after recovering on the cloned disk, 32GB of your data is missing?
Yes, but the "recovery" wasn't a "recovery" at all, but was me performing Windows 7 "chkdsk" on the clone, to use the clone as a replacement boot hard drive. I'm sure the only thing it "recovered" was the Windows operating system.
>Please don't put much hope into this, my guess is that the damage was done before or during decryption - gargabe in, garbage out. But if you have some new drives anyway, it can't hurt to try.
I keep trying not to phrase it as that one onion article; "Man Who Thought He'd Lost All Hope Loses Last Additional Bit Of Hope He Didn't Even Know He Still Had". But, it keeps happening to me. Every time I thought the feeling was over, it hits me again when I read something new. I only even had the motivation to try recovery because I thought I found that the "bad sector" check I did with "HD Tune Pro" didn't actually write any data, so the "only" heavy writing done was from my watching hours of videos/streams, and booting from the bad sector HDD three times. But, upon learning decrypting it wrote data, I feel like there's no hope in even trying anything anymore.
One thing I think I can amend about what happened in your previous post (which admittedly, I only skimmed reading after learning that decrypting my drive wrote data, since I felt like laying down and dying), was this part:
>- You then made a clone (NOT an image) of the original disk to another disk, this copied disk failed to boot when you plugged it in.
>- This cloned disk, you are now encrypting with veracrypt (your ONLY copy of the failing disk)
After decrypting my 2TB bad sector boot HDD (with my hydrus database), I cloned to an external 5TB HDD. But when I tried booting from the external 5TB HDD, it wasn't recognized as a boot device (not that it even tried, but the OS failed to boot, or anything). So this was when I booted from the same 2TB bad sector boot HDD, three times in total, at which point I created an image of it, which is currently on the external 5TB HDD, which is currently being encrypted in place (92.3% done, with 25 hours left).
Thank you for the patient replies. Thank you for the insight. Thank you for being real with me. Even though I can't stomach this being my reality, I'm taking note of all the advice, information, and suggestions I've been given. I wish I had never been vulnerable enough to think not having backups was a fair reality. I wish I had never continued making mistakes to my bad sector HDD after the fact. But thanks for helping me properly compensate for all the context involved in this.