Those 32 character groups (after the sequence) are your private keys.
You've probably found your wallet file.
They are 30 characters unfortunately and pywallet against the text file I created through grep does not get them out. I tried db_recover, no good. Also tried your dump keys program from here
https://bitcointalk.org/index.php?topic=2619534.msg26661685#msg26661685Is this the kind of thing you add two characters to the beginning like 08, gives you 32 and then you convert the keys to Bitcoin format and do something with converting the pair, or the other way around?
Any ideas?
edit: maybe they are 32 with the Berkerley DB masking the last two characters as ^@ or the first as or ^]
They're probably unprintable.
But if you convert the output to hex (e.g. with hexdump or xxd), then after visually identifying the starting sequence, you can take the next 32 hex bytes, concatenate them to a string like "DECAFBAD0ABBCDE7F...", and convert them to WIF keys with a
tool like bitaddress.org (It should always be used offline!)
Also, pywallet can recover the keys directly from a corrupted filesystem on a disk, see --recover, --recov_device and --recov_size.
e.g.
sudo pywallet.py --recover --recov_device /dev/sda1 --recov_size 20Go --recov_outputdir $HOME/bitcoin_recovery
"20Go" is the size required.
The output directory must exist.
You will need to set the password of the recovered wallet to something you'll not forget.
The list of passwords can be empty, just press enter on the "Possible passphrase" prompt.
It searches for keys in the way described by you (looking for data string above), but converts them automatically.
pywallet has not recovered any keys from any of the chunks from the grep or from any of the disks. It creates recovered_wallets and partially_recover_wallets but without keys. I will try the manual WIF key conversion on the data as you described. thx