Pages:
Author

Topic: Formatted computer lost coins? (Read 4787 times)

hero member
Activity: 728
Merit: 500
165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g
July 12, 2012, 06:57:57 AM
#31
A zero wipe changes it from "here run this utility" to requiring an electron microscope to maybe POSSIBLY recover something (at modern drive densities it's debatable whether it's possible at all).  That's close enough for most people.
member
Activity: 111
Merit: 100
July 12, 2012, 06:53:26 AM
#30
this writes zeroes to all data areas of the hard drive, removing the option of recovery

A zero fill does not generally remove the option of recovery on spinning disks (if you only zero fill once). I'm not sure about SSDs, but it probably doesn't remove the option on those either.
hero member
Activity: 686
Merit: 564
July 10, 2012, 04:12:26 PM
#29
All payments sent Smiley thankyou all so much for all your help!!

i definitely wont be so careless next time! however another lesson learnt on how much shit is left on your computer after a format, and thank god for that.... this time anyway..
Yeah, I noticed your payment to me this morning - thanks! Glad to hear that it all worked out in the end and you managed to get your bitcoins back!
newbie
Activity: 47
Merit: 0
July 09, 2012, 11:16:04 PM
#28
Oh yes, a bit of coin trading, and about two years of mining @ 2gh/s.

i turned all the rigs off now however, electricity was killing me and was pretty much break even.

now i have the coins back i can start trading a little again.. should sell my 5970's and pay the electricity bill too
legendary
Activity: 1834
Merit: 1019
July 09, 2012, 10:56:05 PM
#27
haha that was a fat wallet! glad you got your coins back instead of losing them forever the the aether Smiley
hero member
Activity: 728
Merit: 500
165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g
July 09, 2012, 09:53:57 PM
#26
Good to hear it worked out!  Always glad to help.

Yes, always wipe your hard drives...  AFTER you save your BTC.  Smiley
legendary
Activity: 1358
Merit: 1002
July 09, 2012, 04:43:31 AM
#25
Makomk deserves most of the love, but if there's any left over you can send it to 165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g .  Smiley

.cpp and .h are C source code.  Your wallet should just be called wallet.dat.  It will usually be in /home//.bitcoin .

Just to add a little detail. If you can't find the .bitcoin directory on your home dir press CTRL+H to unhide it Wink
hero member
Activity: 728
Merit: 500
165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g
July 09, 2012, 04:38:24 AM
#24
Makomk deserves most of the love, but if there's any left over you can send it to 165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g .  Smiley

.cpp and .h are C source code.  Your wallet should just be called wallet.dat.  It will usually be in /home//.bitcoin .
newbie
Activity: 47
Merit: 0
July 09, 2012, 04:21:59 AM
#23
beautiful.. thankyou so much..

whats your bitcoin address..

as soon as i can transfer them i will send you some too. along with the creator of that program if he ever sends me his address..

where would the wallet.dat file be located on my linux desktop usb?? is it called wallet.cpp or wallet.h on linux?
hero member
Activity: 728
Merit: 500
165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g
July 09, 2012, 03:55:50 AM
#22
sudo cp new_wallet.db /media/usb_stick_name/
newbie
Activity: 47
Merit: 0
July 09, 2012, 03:54:42 AM
#21
permissions denied to open/copy that file still?
hero member
Activity: 728
Merit: 500
165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g
July 09, 2012, 02:50:17 AM
#20
Do you have another USB stick?  If so just put it in and then:

Find the USB stick's name:
ls /media

Copy the recovered wallet there:
cp new_wallet.db /media/usb_stick_name/
newbie
Activity: 47
Merit: 0
July 09, 2012, 02:34:42 AM
#19
Nope i thought i mentioned it wasnt encrypted..

anyway its now done, 110 keys found.. however in ubuntu i am having troubles copying the file that has been made.

it has a lock on it and i cant copy move or anything with this file.

i am using ubuntu desktop off a usb stick so its not installed? i have not created a persistent drive with this install also.. so when i restart the computer i am back to square one..

so i am running this again to get the 110 keys once more and will leave the computer on

can someone help me with this step?? seems to me like file permissions? says its owned by root?
legendary
Activity: 2506
Merit: 1010
July 09, 2012, 12:55:59 AM
#18
i am just running .3 now after being away all weekend.

This is still a crucial detail:

Was the wallet encrypted?  There's a note on that thread that the tool doesn't work with encrypted wallets.  If it was using the encrypted format then we may have to modify it a bit.
newbie
Activity: 47
Merit: 0
July 09, 2012, 12:45:54 AM
#17
Hey guys thanks for the extra help and advice here, i am just running .3 now after being away all weekend.

i know a little about data recovery but have never really dove this far into it before.

i dont think i zero'd out data on the format, just did a quick format.

if this .3 tool fails to recover again i will be talking to cassicaus , and perhaps trying the quick script above.

but in the end if its gone i guess its gone Sad
legendary
Activity: 3472
Merit: 4801
July 08, 2012, 10:04:06 PM
#16
. . .When you have a wallet, make physical QR codes of the . . . private keys. . .
Perhaps you can offer some instruction on how to do this for those non-technical people who are using the standard bitcoin client?  It doesn't offer any buttons or menu options to do this, or even to see what your private key is.
donator
Activity: 994
Merit: 1000
July 08, 2012, 12:54:41 PM
#15
to gain a bit more confidence on the restorability of the data you could do a deep scan for each one of the public keys. I appended a  bash script which does that for you. You need to modify the pubkey variable and redirect dd to the correct hard disc. the loop assumes that your hard disc is less than 2TB. Also, make sure you have root access to the drive...

If you find one public key on the disc that might be an indication that the restoration tool has failed you but the data is still there.

I don't know how much you know about data restoration but it may pay off to find someone to do it for you.
All depends on trust level and whether the amount is worth it....

good luck!

script:
===
#!/bin/bash

pubkey=1Nn3GoGpWj3UonxUq4VB432T8fxnBmec2b

for i in {0..2000000}; do
 dd if=/dev/sda2 of=block.dat bs=1M count=2 skip=$i &>/dev/null
 grep $pubkey block.dat &>/dev/null
 if [ $? -eq 0 ] ; then
  echo "public key found, block $i"
  break
 fi
done
full member
Activity: 166
Merit: 100
July 08, 2012, 12:04:10 PM
#14
A piece of advice (this won't help now, but it will later):

When you have a wallet, make physical QR codes of the public addresses AND private keys. Match them as well. Multiple copies of the keys in case one is damaged or lost. Then you can scan the code with your webcam (yes, tools exist that do that) and recover them. This has not been tested on encrypted wallets, but probably won't work on them.
legendary
Activity: 1512
Merit: 1036
July 07, 2012, 09:31:12 AM
#13
The key phrase in the first post is "fresh install", that the OS was reinstalled and used after the formatting too, drastically reducing the chance of recoverable data remaining in unwritten areas.

If you do a quick format, which takes just a few seconds, then the majority of the data areas may still have been intact (until the reinstallation of another OS). If however a full format was done (10 minutes to several hours depending on the drive size and tech), this writes zeroes to all data areas of the hard drive, removing the option of recovery. This depends on how the OSX formatter's (appropriately called "erase disk") security option was set:

legendary
Activity: 2506
Merit: 1010
July 06, 2012, 07:59:17 PM
#12
Was the wallet encrypted?  There's a note on that thread that the tool doesn't work with encrypted wallets.  If it was using the encrypted format then we may have to modify it a bit.

Also I see v0.3 which supports compressed public keys was just released, so if your scan was done with a version prior to 0.3, it wouldn't have detected anything if you are running Bitcoin v0.6.x, which uses compressed public keys.
Pages:
Jump to: