[HELP] Encrypted LUKS Disk + Pet Cat + Windows 10 + Initialize Disk Button = Uh oh.
Posted: 13 Feb 2020, 18:53
Greeting to all of you!
▛▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝ ▜
I found myself in a very shocking position recently. So her eit goes... I had the idea I wanted to view my Linux drives within Windows since recently I had to be using Windows more than often. I started checking things out and suddenly a window popped up exactly like this...
Suddenly I found myself needing to go to the bathroom, I didn't really think about what had just popped up on the screen regarding one of my most important drives. All I knew was that I didn't want to click that button. I came back from the bathroom and I found my cat curling himself on my mouse like he usually does in order to try to get me to stop what I'm doing and give him my attention. I looked at the screen and my heart sank... It had just successfully initialized my most important encrypted drive. I calmly removed my lovely cat from the desk and in slow motion looked back to the computer screen and said "Oh................." ... as I slowly sat down while saying "oooooooookkkaaaaaayyyyyyy" while sliding into my chair and not wanting to admit to myself that anything bad had just happened... but days later after dozens of different attempts, yeah, something bad definitely happened.
It feels as if a big part of my life, is over. Gone, wiped away.
Whats on this drive? Well, in the worlds eyes, the most important thing would be the bitcoins. I don't know if I should mention how much there are on this thing because I really don't want to cause any craziness. But to myself, it would be my files, the bitcoins too, but I really want my files...
Apparently, in Windows operating systems, it's super easy to Initialize a Disk as it contains nothing but a big easy button to push and no warnings whatsoever... CLICK. DONE. Apparently, this is because Windows doesn't recognize any other filesystems other than their own, lol... so most are treated as unrecognized.
I just hope that I can get this disk back and running with the same files on it. As for the bitcoins, it's not that I need the money... but might as well go rip up a winning lottery ticket, because essentially that's exactly whats taking place here.
Any help is greatly appreciated, and will be rewarded. In return for the much appreciated help and in the event we can get back into the encrypted drive, I will happily reward the geniuses a bitcoin, or two, possibly three.
▙ ▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▟
Here's some things I've done so far + useful information that might be helpful for a successful recovery.
1.) The original commands that were used to create the LUKS encryped disk/partition:
2.) testdisk, writing what you see here in the screenshot to the disk did nothing.
...also tried START SECTORS: 2048, 512, 245, 316, 4096, and 1
However, I am not entirely sure of what "type" to select... BUT it does find the encrypted disks LABEL, "SB_5TB_HDD" as you can see above.
After writing to disk using testdisk, I ran this command:
Which gave me the following output:
After each attempt I would restore the screwed up drive with Clonezilla and try again, but only to fail...
3.) EXACTLY what the disk looked like within Disk Utility when the drive was working, before this all happened.
4.) This is what the disk looks like now.
5.) My current setup for this disk within /etc/crypttab (string inside fake trash file)
6.) My current setup for this disk within /etc/fstab
9. Also, after writing this screenshot to disk using testdisk
I ran this command:
but it wouldn't find anything...
======================
So I went back to Clonezilla and restored it back to its crap-state in order try again with something else. Any ideas?
Thank you so much for your time.
▛▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝▝ ▜
I found myself in a very shocking position recently. So her eit goes... I had the idea I wanted to view my Linux drives within Windows since recently I had to be using Windows more than often. I started checking things out and suddenly a window popped up exactly like this...
Suddenly I found myself needing to go to the bathroom, I didn't really think about what had just popped up on the screen regarding one of my most important drives. All I knew was that I didn't want to click that button. I came back from the bathroom and I found my cat curling himself on my mouse like he usually does in order to try to get me to stop what I'm doing and give him my attention. I looked at the screen and my heart sank... It had just successfully initialized my most important encrypted drive. I calmly removed my lovely cat from the desk and in slow motion looked back to the computer screen and said "Oh................." ... as I slowly sat down while saying "oooooooookkkaaaaaayyyyyyy" while sliding into my chair and not wanting to admit to myself that anything bad had just happened... but days later after dozens of different attempts, yeah, something bad definitely happened.
It feels as if a big part of my life, is over. Gone, wiped away.
Whats on this drive? Well, in the worlds eyes, the most important thing would be the bitcoins. I don't know if I should mention how much there are on this thing because I really don't want to cause any craziness. But to myself, it would be my files, the bitcoins too, but I really want my files...
Apparently, in Windows operating systems, it's super easy to Initialize a Disk as it contains nothing but a big easy button to push and no warnings whatsoever... CLICK. DONE. Apparently, this is because Windows doesn't recognize any other filesystems other than their own, lol... so most are treated as unrecognized.
I just hope that I can get this disk back and running with the same files on it. As for the bitcoins, it's not that I need the money... but might as well go rip up a winning lottery ticket, because essentially that's exactly whats taking place here.
Any help is greatly appreciated, and will be rewarded. In return for the much appreciated help and in the event we can get back into the encrypted drive, I will happily reward the geniuses a bitcoin, or two, possibly three.
▙ ▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▖▟
Here's some things I've done so far + useful information that might be helpful for a successful recovery.
1.) The original commands that were used to create the LUKS encryped disk/partition:
Code: Select all
sudo cryptsetup -c aes-xts-plain64 -s 512 -h sha512 --iter-time 5000 --use-random --verify-passphrase luksFormat /dev/sdg
sudo cryptsetup luksOpen /dev/sdg SB_5TB_HDD
ls -arlt /dev/mapper | tail
sudo mkfs.ext4 /dev/mapper/SB_5TB_HDD
sudo mount /dev/mapper/SB_5TB_HDD /mnt/SB_5TB_HDD
2.) testdisk, writing what you see here in the screenshot to the disk did nothing.
...also tried START SECTORS: 2048, 512, 245, 316, 4096, and 1
However, I am not entirely sure of what "type" to select... BUT it does find the encrypted disks LABEL, "SB_5TB_HDD" as you can see above.
After writing to disk using testdisk, I ran this command:
Code: Select all
sudo cryptsetup luksOpen /dev/sdg SB_5TB_HDD
Code: Select all
Device /dev/sdg is not a valid LUKS device.
3.) EXACTLY what the disk looked like within Disk Utility when the drive was working, before this all happened.
4.) This is what the disk looks like now.
5.) My current setup for this disk within /etc/crypttab (string inside fake trash file)
Code: Select all
SB_5TB_HDD /dev/SB_5TB_HDD /mnt/USB_Key/.Trash-1000 luks
6.) My current setup for this disk within /etc/fstab
Code: Select all
# DO mount, and DO show in menu
/dev/mapper/SB_5TB_HDD /mnt/SB_5TB_HDD auto nosuid,nodev,nofail,x-gvfs-show 0 0
9. Also, after writing this screenshot to disk using testdisk
I ran this command:
Code: Select all
sudo hexdump -C /dev/sdh | grep LUKS
======================
So I went back to Clonezilla and restored it back to its crap-state in order try again with something else. Any ideas?
Thank you so much for your time.