[Data Recovery Problem] Recovering many Wallet.dat from repartitioned Hard drive

[Praxis]

Yay, I have a pywallet_partial_recovery_timestamp.dat file now.

If I load it in, say, Worldcoin, it gives me an error.  I think I should run pywallet ON this file now to extract the crypted keys from it somehow? If I just put -recov_device as the file instead of /dev/sda like you said, it still crashes like before

[jackjack]

This file is not a wallet at all, it's just the list of the places where pywallet found keys.
Thus this avoid to read the disk again: pywallet just has to look around these places.

So you don't have to wait 3 hours each time you try the recovery

For now I didn't try any fix so it's normal it crashes like before. The goal was only to create this intermediate file.
Try this (using the partialrecoveryfile:, as you will always do from now on) and post all the output
2.1.0b6
http://pastebin.com/raw.php?i=UeavfR1a

[Praxis]

I ran it with the file, not /dev/sda, like you said:

Code:

Possible passphrase: 

Starting recovery.

Loaded 640.1 Go from /dev/sda

Found 46 possible wallets
Found 8414 possible encrypted keys
Found 5443 possible unencrypted keys

Possible wallet #1
    with passphrase #1  a
b
[manjaro@manjaro ~]$

[jackjack]

Odd
Do you have strange/UTF8 characters in your passphrase?

[Praxis]

Odd
Do you have strange/UTF8 characters in your passphrase?

only alphanumeric mixed with few symbols such as  ! , # , % , & , ...

but now that I think of it, when I encrypted the passwords, I was using a Slovenian keyboard / encoding, which is basically like American plus a few extra characters... and the keys are placed a bit differently

could that be the reason? (even though I did not use those special Slovenian characters in the passwords)

[jackjack]

I can't reproduce it
Try with random passphrases containing only alphanumeric characters
Does it crash too?

but now that I think of it, when I encrypted the passwords, I was using a Slovenian keyboard / encoding, which is basically like American plus a few extra characters... and the keys are placed a bit differently

could that be the reason? (even though I did not use those special Slovenian characters in the passwords)

Maybe but not likely if there is no Slovenian character in the passphrase
I'll try other things when I'm back home in a few hours

[Praxis]

Code:

[manjaro@manjaro Documents]$ sudo python2 ../Downloads/pywallet.py --recover --recov_device=PartialRecoveryFile:./pywallet_partial_recovery_1374430501.dat --recov_outputdir /home/manjaro/Documents/ --recov_size 640.1Gio
Enter the passphrase for the wallet that will contain all the recovered keys: asdf

Enter the possible passphrases used in your deleted wallets.

Possible passphrase: fdsa
Possible passphrase: 

Starting recovery.

Loaded 640.1 Go from /dev/sda

Found 46 possible wallets
Found 8414 possible encrypted keys
Found 5443 possible unencrypted keys

Possible wallet #1
    with passphrase #1  a
b
[manjaro@manjaro Documents]$ 

[jackjack]

Try this one and post the lines beginning with "crypter" and "skfp": http://pastebin.com/raw.php?i=0SMbAwat (with random passphrases too as it will print the passphrase you entered)

I'm sorry to make you try files so many times...

[Praxis]

It is I who am sorry for all these complications and deeply thankful for your help.

I attach a picture because I'm worried copy/paste wouldn't reproduce the strange characters it outputs:

[jackjack]

This seems desperately normal...
This one? http://pastebin.com/raw.php?i=PgXbLpdL

Ok I'll tell you what I'm doing, that would be less annoying for you. I found the function that crashes but I don't understand why it crashes without printing any error as it should. Also I don't even understand why it is crashing at all.
The last version prints something after each line within that function so that I'll know which one crashed.

Did you compile ssl yourself?

[Praxis]

Thank you for the information. I will try the other file now.

I did not compil SSL myself. I'm using a LiveCD of Manjaro which is a version of the rolling-release Arch distribution.

Here's verbose information output on SSL version:

Code:

[manjaro@manjaro Downloads]$ openssl version -a
OpenSSL 1.0.1e 11 Feb 2013
built on: Sun Feb 17 13:43:48 CET 2013
platform: linux-x86_64
options:  bn(64,64) md2(int) rc4(8x,int) des(idx,cisc,16,int) idea(int) blowfish(idx) 
compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -m64 -DL_ENDIAN -DTERMIO -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
OPENSSLDIR: "/etc/ssl"
[manjaro@manjaro Downloads]$ 

[Praxis]

Different error this time - with the latest pastebin:

[jackjack]

Good idea posting the openssl version. I have 1.0.1c but I highly doubt this comes from that. I'll check though.

About the error, please delete these two lines and try again:
   line 769:   print strKeyData.encode('hex')
   line 772:   print chSalt.encode('hex')

[Praxis]

Code:

Possible wallet #1
    with passphrase #1  a
b
SKFP params: fdas �m�����* 58001 0
za
zc
zd
ze
[manjaro@manjaro Downloads]$ 

[jackjack]

I'm really starting to think this comes from openssl
http://pastebin.com/raw.php?i=1QyNB5Af

[Praxis]

Code:

Possible wallet #1
    with passphrase #1  a
b
SKFP params: ytrewq �m�����* 58001 0
za
zc
zd
ze
zf
zg
zh
zi

Perhaps I should just try another distribution that has another version of openssl?

[jackjack]

Yes, please try another distribution if you can
Don't forget to keep pywallet_partial_recovery_1374430501.
Do you have an exotic hardware?

[Praxis]

[manjaro@manjaro Documents]$ sudo hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
   Model Number:       WDC WD6401AALS-00L3B2                   
   Serial Number:      WD-WCASY4710125
   Firmware Revision:  01.03B01
   Transport:          Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
Standards:
   Supported: 8 7 6 5
   Likely used: 8
Configuration:
   Logical      max   current
   cylinders   16383   16383
   heads      16   16
   sectors/track   63   63
   --
   CHS current addressable sectors:   16514064
   LBA    user addressable sectors:  268435455
   LBA48  user addressable sectors: 1250263728
   Logical/Physical Sector size:           512 bytes
   device size with M = 1024*1024:      610480 MBytes
   device size with M = 1000*1000:      640135 MBytes (640 GB)
   cache/buffer size  = unknown
Capabilities:
   LBA, IORDY(can be disabled)
   Queue depth: 32
   Standby timer values: spec'd by Standard, with device specific minimum
   R/W multiple sector transfer: Max = 16   Current = 1
   Recommended acoustic management value: 128, current value: 254
   DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
        Cycle time: min=120ns recommended=120ns
   PIO: pio0 pio1 pio2 pio3 pio4
        Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
   Enabled   Supported:
          SMART feature set
          Security Mode feature set
      *   Power Management feature set
      *   Write cache
      *   Look-ahead
      *   Host Protected Area feature set
      *   WRITE_BUFFER command
      *   READ_BUFFER command
      *   NOP cmd
      *   DOWNLOAD_MICROCODE
          Power-Up In Standby feature set
      *   SET_FEATURES required to spinup after power up
          SET_MAX security extension
          Automatic Acoustic Management feature set
      *   48-bit Address feature set
      *   Device Configuration Overlay feature set
      *   Mandatory FLUSH_CACHE
      *   FLUSH_CACHE_EXT
      *   SMART error logging
      *   SMART self-test
      *   General Purpose Logging feature set
      *   64-bit World wide name
      *   Segmented DOWNLOAD_MICROCODE
      *   Gen1 signaling speed (1.5Gb/s)
      *   Gen2 signaling speed (3.0Gb/s)
      *   Native Command Queueing (NCQ)
      *   Host-initiated interface power management
      *   Phy event counters
          DMA Setup Auto-Activate optimization
      *   Software settings preservation
      *   SMART Command Transport (SCT) feature set
      *   SCT Read/Write Long (AC1), obsolete
      *   SCT Write Same (AC2)
      *   SCT Error Recovery Control (AC3)
      *   SCT Features Control (AC4)
      *   SCT Data Tables (AC5)
          unknown 206[12] (vendor specific)
          unknown 206[13] (vendor specific)
Security:
   Master password revision code = 65534
      supported
   not   enabled
   not   locked
   not   frozen
   not   expired: security count
      supported: enhanced erase
   118min for SECURITY ERASE UNIT. 118min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee257f47641
   NAA      : 5
   IEEE OUI   : 0014ee
   Unique ID   : 257f47641
Checksum: correct

[Praxis]

Gonna try with a more standard/stable live distro.

[jackjack]

And your computer? Processor? Nothing special?

Gonna try with a more standard/stable live distro.

I hope it will help