Re: Looking for confirmation as I enter the acceptance stage.

On 23 Jul 2023 18:40 -0400, from [email protected] (blobfish):
> command:    sudo hexdump -C /dev/sdb1 | head -n 1024 > badDriveHexDump1024.txt
> result:     see attached file.

I haven't looked closely at what you posted, but at a glance, it seems
to me that you are in a slightly better position than most. Depending
on exactly what triggers the error message, there just MIGHT POSSIBLY
be a glimmer of hope.

Please post the full output of `blkid /dev/sdb1` and `lsblk -bJO
/dev/sdb1`, along with the output from running `cryptsetup luksOpen`
on the container with `--debug` specified.

Also a clarification: you mention that you know the passphrase. Did
the container have more than one active key slot? (Say, one with a
passphrase you've memorized, and one with the key file you attached.)

Also, would it be possible for you to post the corresponding data
unencoded?

Something like

sudo dd if=/dev/sdb1 of=sdb1.head bs=32525167 count=1
sudo gzip sdb1.head

and post the resulting sdb1.head.gz.

It will contain the same data you have already posted here, only
formatted differently. (32525167 == 0x1f04b60 + 15)

In all cases, of course, adjusting the device name in case you've
rebooted or it otherwise might have changed in the interim.

-- 
Michael Kjörling                     🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”