Good luck
Topic: [Data Recovery Problem] Recovering many Wallet.dat from repartitioned Hard drive - page 3. (Read 7906 times)
July 20, 2013, 08:32:28 AM
Great
Good luck
Good luck
July 20, 2013, 08:28:31 AM
Works!! You're awesome! I run the proccess now
July 20, 2013, 08:06:34 AM
2.1.0b4 should work: http://pastebin.com/raw.php?i=wmXTdQrf
July 20, 2013, 07:58:32 AM
Code:
Starting recovery.
Can't open /dev/sda, check the path or try as root
("'module' object has no attribute 'O_BINARY'",)
July 20, 2013, 03:52:27 AM
Pretty dumb I don't print the error when it crashes...
Done here 2.1.0b3: http://pastebin.com/raw.php?i=pXXh2bNF
You will still get the "path or try as root" error but the line just below will give some additional details
Done here 2.1.0b3: http://pastebin.com/raw.php?i=pXXh2bNF
You will still get the "path or try as root" error but the line just below will give some additional details
July 19, 2013, 11:40:44 PM
Thanks for the ideas. Problem is, I made new partitions, not just deleted the old ones.haven-t done anything except making new partitions though. No idea how Gparted could restore my old partition table ...
the good news is that I feel I'm really close to recovering wallets with jackjack's pywallet after he made the changes to scan encrypted wallets
the good news is that I feel I'm really close to recovering wallets with jackjack's pywallet after he made the changes to scan encrypted wallets
It depends, if by "make" new partitions that includes formatting them, then it does hurt your chances pretty badly. Gparted scans the disk for filesystem signatures and can deduce the partitions' start and size from those. If all you've done was delete the partition table and allocate space for new partitions, those signatures and all the rest of the data needed to store the old files would still be there.
Even if you formatted the new partitions, it might still be able to find something if the beginnings of the old and new partitions happened to be far enough apart, but it seems like a slim chance, and maybe you don't need to try it if you're making progress with pywallet.
July 19, 2013, 11:15:02 PM
Have you tried guessing the old partition table with gpart? Gparted has a nice UI frontend that will scan for partitions, then let you mount them.
If all that's happened is your partition table is gone, you have pretty good chances of finding your filesystems entirely intact, you just have to find where they are located on the disk.
If all that's happened is your partition table is gone, you have pretty good chances of finding your filesystems entirely intact, you just have to find where they are located on the disk.
Thanks for the ideas. Problem is, I made new partitions, not just deleted the old ones.haven-t done anything except making new partitions though. No idea how Gparted could restore my old partition table ...
the good news is that I feel I'm really close to recovering wallets with jackjack's pywallet after he made the changes to scan encrypted wallets
Maybe for the next time but if something like this happens it's important to first make a raw disk image and store it somewhere as a backup. Then work on the drive to get your data back. In case something goes wrong you at least have a raw backup image of the drive.
Hope with the good tools in this thread you'll get everything back or at least the important wallets !
July 19, 2013, 09:17:20 PM
Have you tried guessing the old partition table with gpart? Gparted has a nice UI frontend that will scan for partitions, then let you mount them.
If all that's happened is your partition table is gone, you have pretty good chances of finding your filesystems entirely intact, you just have to find where they are located on the disk.
If all that's happened is your partition table is gone, you have pretty good chances of finding your filesystems entirely intact, you just have to find where they are located on the disk.
Thanks for the ideas. Problem is, I made new partitions, not just deleted the old ones.haven-t done anything except making new partitions though. No idea how Gparted could restore my old partition table ...
the good news is that I feel I'm really close to recovering wallets with jackjack's pywallet after he made the changes to scan encrypted wallets
July 19, 2013, 09:05:20 PM
Have you tried guessing the old partition table with gpart? Gparted has a nice UI frontend that will scan for partitions, then let you mount them.
If all that's happened is your partition table is gone, you have pretty good chances of finding your filesystems entirely intact, you just have to find where they are located on the disk.
If all that's happened is your partition table is gone, you have pretty good chances of finding your filesystems entirely intact, you just have to find where they are located on the disk.
July 19, 2013, 08:14:01 PM
I'm using windows since yesterday so I think I made a windows fix that broke it...
Sorry for this, I'll give it a look a bit later
Sorry for this, I'll give it a look a bit later
July 19, 2013, 07:13:40 PM
Same error if I run with /dev/sda or /dev/sda1 or /dev/sdaX... "Can't open /dev/sda, check the path or try as root" ...
But with the old version of pywallet, I ran it on /dev/sda and it worked well. In fact, the old version works on /dev/sda or any other, /dev/sdax
I just tried again the old version :
My partition table is currently a clusterfuck but it shouldn't be the reason, since with old pywallet I can scan /dev/sda directly. It's really strange, I can't understand.
But with the old version of pywallet, I ran it on /dev/sda and it worked well. In fact, the old version works on /dev/sda or any other, /dev/sdax
I just tried again the old version :
Code:
[root@manjaro Documents]# python2 pywalletOld.py --recover --recov_device /dev/sda --recov_size 30Gio --recov_outputdir /home/manjaro/Documents/
0.00/32.21 Go
ETA: 07:00:09
0.01/32.21 Go
ETA: 01:04:14
0.02/32.21 Go
ETA: 01:04:14
My partition table is currently a clusterfuck but it shouldn't be the reason, since with old pywallet I can scan /dev/sda directly. It's really strange, I can't understand.
July 19, 2013, 05:49:17 PM
Thanks for the kind words+tips guys
Praxis: Try with a specific partition, like /dev/sda1
I never tried the whole disk sda so I'm not sure it works
And changing the LiveCD shouldn't change anything
Praxis: Try with a specific partition, like /dev/sda1
I never tried the whole disk sda so I'm not sure it works
Is it because I run it with "python2 pywallet.py" instead of "./pywallet.py"
NopeAnd changing the LiveCD shouldn't change anything
July 19, 2013, 05:42:43 PM
Works now, it asks me for all the passphrases, I typed all the passes that I remember - I'm sure about the passes for the most important wallets - ... after all this, it gives me this:
Which is odd, since I am running this as root, and /dev/sda is the right path:
Is it because I run it with "python2 pywallet.py" instead of "./pywallet.py" - I think it shouldn't matter, I still ask
Otherwise I'll try a different Linux LiveCD. Sorry for so many questions. As Kouye has said you deserve fat tips for your work, when I get my hands on the lost coins I will donate a significant amount of my coins.
Code:
Starting recovery.
Can't open /dev/sda, check the path or try as root
[root@manjaro Code]#
Which is odd, since I am running this as root, and /dev/sda is the right path:
Code:
[root@manjaro Code]# fdisk -l
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
Disk /dev/sda: 640.1 GB, 640135028736 bytes, 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
# Start End Size Type Name
1 162 1241514017 592G unknown
2 1243977728 1250263023 3G Linux swap
3 1250263074 1250263689 308K unknown
Is it because I run it with "python2 pywallet.py" instead of "./pywallet.py" - I think it shouldn't matter, I still ask
Otherwise I'll try a different Linux LiveCD. Sorry for so many questions. As Kouye has said you deserve fat tips for your work, when I get my hands on the lost coins I will donate a significant amount of my coins.
July 19, 2013, 05:35:05 PM
Agreed, I had to install, had pywallet working - I didn't have python on my computer, and understand how to use it...
Was a lot of fun, even more since I managed to google for it from scratch, and finally succedeed.
Great tool, I agree with D&T it's a shame jackjack didn't receive more tips for it. Sending one (small tip, I'm pooooor!!!) now, in memory of this precious moment where it worked.
Was a lot of fun, even more since I managed to google for it from scratch, and finally succedeed.
Great tool, I agree with D&T it's a shame jackjack didn't receive more tips for it. Sending one (small tip, I'm pooooor!!!) now, in memory of this precious moment where it worked.
July 19, 2013, 05:24:22 PM
I just tried
and it works!!
Going to run the recover now
This is quite the adventure. I'd never thought something like this could be fun, but it actually is in a strange way , even though real money is at stake ... !
Fingers crossed now
Code:
sudo python2 ./pywallet.py
and it works!!
Going to run the recover now
This is quite the adventure. I'd never thought something like this could be fun, but it actually is in a strange way , even though real money is at stake ... !
Fingers crossed now
July 19, 2013, 05:22:17 PM
Yeah sorry I'll put a specific error about that... You need python 2.*, pywallet can't run with python 3
oh, thanks for the fast reply!! Got it! Let me retry with python2
July 19, 2013, 05:20:53 PM
Yeah sorry I'll put a specific error about that... You need python 2.*, pywallet can't run with python 3
July 19, 2013, 05:18:57 PM
I'm having some problems running it. I'm currently in a Linux LiveCD environment (running Manjaro which is a Arch-linux based distro, from an USB key). I tried to run the py with ./sudo pywallet.py after having chmod +x it, and it gives me this:
I thought it was a problem of me not having the bsddb that you write is a requirement, so I installed it, but it's still the same.
Within the list of modules, I see a long list, the relevant part is here:
If I try to run it like this, I get the following error:
What do you think could be the issue? Should I load Ubuntu on the USB instead?
Code:
[manjaro@manjaro Code]$ ls
bsddb3-6.0.0/ pywallet.py* pywallet.py~
[manjaro@manjaro Code]$ sudo ./pywallet.py
: No such file or directory
I thought it was a problem of me not having the bsddb that you write is a requirement, so I installed it, but it's still the same.
Code:
[manjaro@manjaro Code]$ python --version
Python 3.3.2
[manjaro@manjaro Code]$ python
Python 3.3.2 (default, May 21 2013, 15:40:45)
[GCC 4.8.0 20130502 (prerelease)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> help('modules')
Please wait a moment while I gather a list of all available modules...
Within the list of modules, I see a long list, the relevant part is here:
Code:
[b]...[/b]
_bisect base64 ipaddress smtpd
_bz2 bdb itertools smtplib
_codecs binascii json sndhdr
_codecs_cn binhex keyword socket
_codecs_hk bisect lib2to3 socketserver
_codecs_iso2022 [b]bsddb3 [/b] linecache spwd
[b]...[/b]
If I try to run it like this, I get the following error:
Code:
[manjaro@manjaro Code]$ sudo python pywallet.py
File "pywallet.py", line 845
_p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
^
SyntaxError: invalid syntax
What do you think could be the issue? Should I load Ubuntu on the USB instead?
July 19, 2013, 03:37:31 PM
Ok, use pywallet 2.1.0b1: http://pastebin.com/raw.php?i=zU2x7amw
The recovery now runs with encrypted+unencrypted on linux+windows
The recovery now runs with encrypted+unencrypted on linux+windows
Wonderful! Going to try it now.
July 19, 2013, 01:43:51 PM
Ok, use pywallet 2.1.0b1: http://pastebin.com/raw.php?i=zU2x7amw
The recovery now runs with encrypted+unencrypted on linux+windows
The recovery now runs with encrypted+unencrypted on linux+windows
Jump to: