Topic: Help "untrap" my btc (Read 2926 times)

If I may suggest a slightly different approach. Instead of dumpprivkey [your bitcoin address here] use dumpwallet filename

This will create a file with all your private keys you can easily import into electrum. You import into electrum via:

File -> New/Restore -> pick a name -> select Restore a wallet or import keys and Standard wallet. -> put your private keys in the box (one per line remove the comments that came with the export) and follow the rest of the steps (set a password, let it sync).

Electrum is here:
https://electrum.org/#home
(ONLY download from the official sites for any of the wallets, btw)

The Electrum sub-forum is here:
https://bitcointalk.org/index.php?board=98.0

Electrum itself is small - maybe 30MB depending on the version so it is quick to download electrum itself.

As far as exporting, this has some step by step instructions:
http://bitcoin.stackexchange.com/questions/4203/how-can-i-export-the-private-key-for-an-address-from-the-satoshi-client/5933#5933 :

Thank you for your quick response...If I decide to go with Electrum, can you provide me the link to download?
How do I export the private keys from the bitcoin core to electrum??

My system is old (vista OS). How long would you estimate the download of Electrum??

I hope to hear from you SOON!!!

You could try reindexing again. Or you could also just try a different wallet which doesn't require the full blockchain. If you go with another wallet, I recommend that you use Electrum. You will need to export your private keys from Bitcoin Core and import them to Electrum.

I am truly sad today...I was down to "2 weeks" indexing left. This is what happened. For some reason I couldn't
access a website I wanted. It was like a freeze up. So consequently, I just turned off my system (Vista OS).
then I rebooted the system.  I could locate the website now. Then After trying to open the Bitcoin-qt, I received  
an error message: "Error reading from database, shutting down."

I clicked ok. Second message: " Microsoft Visual Ctt Runtime Library
"This application has requested the runtime to terminate it in an unual way. Please contact
the application's support team for more information."

I clicked ok.

Microsoft windows pop-up appeared  message:
"Bitcoin-qt.exe has stopped working. a problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.

Click to close program

What do I do now (layman terms please)...Hopefully I will retreive my btc and it will take as long
as it has....Please I hope to hear from you very SOON!!!

What sort os system are you running, it must be pretty old?  downloading the block chain should really only take a few days.

Update:

My wallet is reindexing as we speak...So I guess I'm making some progress.
I will be overjoyed when I can finally get my trapped btc back. I know how to
show my appreciation via donation.

I will keep you updated. The indexing will most likely take 2 weeks.

Assuming that you have Windows and did not change the default directory, your Blocks folder should be located in %appdata%/Bitcoin. You can then see the blocks folder and find the file.

However, with the blocks deleted, Bitcoin Core will need to reindex the entire blockchain. It can take sometime for Bitcoin Core to verify all the blocks depending on your CPU and Harddisk speed. You just need to let it reindex.

I TRULY appreciate your time and PATIENCE!!!

How do I locate the data directory?? From what you said, once I get to the data directory I will click on the folder and search for the block folder.
Once there I will click that folder and then proceed to find the blk00333.dat file then delete it...Am I correct in this procedure?? If so, all I will need
to know is HOW to get to/locate the data directory...I hope to hear from you very SOON!!!

That file is located in the blocks folder in the data directory

OK...But how do I locate the blk00333.dat file to delete it ?? I'd rather be safe than sorry.
Is there any particular way I should delete it???

I hope to hear from you very soon.

So it looks like you have a corrupted block on your disk. You can delete blk00333.dat file which is causing the problems but doing so would require having to reindex again, and from it looks like, it will take you a really long time.

Another option, which would probably be faster for you, is to download someone else's fully indexed data directory. This thread: https://bitcointalksearch.org/topic/download-the-blockchain-here-updated-regularly-1310261 links to one that is fully indexed and ready to go, you just need to download and unzip the file. However, do so with care as I don't think it has been verified to be trusted yet (although it is probably safe to trust it). It is downloaded as a torrent.

2016-01-23 14:10:38 Shutdown: In progress...
2016-01-23 14:10:39 StopNode()
2016-01-23 14:10:39 Shutdown: done
2016-01-23 15:23:13 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2016-01-23 15:23:14



















2016-01-23 15:23:14 Bitcoin version v0.11.2 (2015-11-10 14:46:18 +0100)
2016-01-23 15:23:14 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2016-01-23 15:23:14 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-01-23 15:23:14 Default data directory C:\Users\Gateway\AppData\Roaming\Bitcoin
2016-01-23 15:23:14 Using data directory C:\Users\Gateway\AppData\Roaming\Bitcoin
2016-01-23 15:23:14 Using config file C:\Users\Gateway\AppData\Roaming\Bitcoin\bitcoin.conf
2016-01-23 15:23:14 Using at most 125 connections (2048 file descriptors available)
2016-01-23 15:23:14 Using 2 threads for script verification
2016-01-23 15:23:14 Using wallet wallet.dat
2016-01-23 15:23:14 scheduler thread start
2016-01-23 15:23:14 init message: Verifying wallet...
2016-01-23 15:23:14 CDBEnv::Open: LogDir=C:\Users\Gateway\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Gateway\AppData\Roaming\Bitcoin\db.log
2016-01-23 15:23:14 Bound to [::]:8333
2016-01-23 15:23:14 Bound to 0.0.0.0:8333
2016-01-23 15:23:14 Cache configuration:
2016-01-23 15:23:14 * Using 2.0MiB for block index database
2016-01-23 15:23:14 * Using 32.5MiB for chain state database
2016-01-23 15:23:14 * Using 65.5MiB for in-memory UTXO set
2016-01-23 15:23:14 init message: Loading block index...
2016-01-23 15:23:14 Opening LevelDB in C:\Users\Gateway\AppData\Roaming\Bitcoin\blocks\index
2016-01-23 15:23:14 Opened LevelDB successfully
2016-01-23 15:23:14 Opening LevelDB in C:\Users\Gateway\AppData\Roaming\Bitcoin\chainstate
2016-01-23 15:23:14 Opened LevelDB successfully
2016-01-23 15:23:35 LoadBlockIndexDB: last block file = 336
2016-01-23 15:23:35 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=169, size=121825162, heights=373986...374697, time=2015-09-11...2015-09-15)
2016-01-23 15:23:35 Checking all blk files are present...
2016-01-23 15:23:41 LoadBlockIndexDB: transaction index disabled
2016-01-23 15:23:41 LoadBlockIndexDB: hashBestChain=00000000000000000bb77d64329ac6d0cebc8c44250a64d2f9cc6c0af85ed74d height=374050 date=2015-09-11 13:49:40 progress=0.870328
2016-01-23 15:23:41 init message: Verifying blocks...
2016-01-23 15:23:41 Verifying last 288 blocks at level 3
2016-01-23 15:25:15 No coin database inconsistencies in last 11 blocks (8595 transactions)
2016-01-23 15:25:15  block index          121657ms
2016-01-23 15:25:16 init message: Loading wallet...
2016-01-23 15:25:16 nFileVersion = 110200
2016-01-23 15:25:16 Keys: 0 plaintext, 257 encrypted, 0 w/ metadata, 257 total
2016-01-23 15:25:16  wallet                  483ms
2016-01-23 15:25:16 init message: Activating best chain...
2016-01-23 15:25:16 ERROR: CheckProofOfWork(): nBits below minimum work
2016-01-23 15:25:16 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=333, nPos=89255871)
2016-01-23 15:25:16 *** Failed to read block
2016-01-23 15:25:25 scheduler thread interrupt
2016-01-23 15:25:25 Shutdown: In progress...
2016-01-23 15:25:25 StopNode()
2016-01-23 15:25:26 Shutdown: done

Paste the stuff from the last run. Scroll up from the bottom of the file until you reach a section with a lot of empty lines. Copy everything from that area down and paste that here.

I tried to paste the contents of the debug.log file, and I received an error message when I click post:
413 Request Entity too Large.
What do I do now???

Go to the data directory (os specific instructions here: https://en.bitcoin.it/wiki/Data_directory). Find the debug.log file. Post the contents here.

I need help again...I downloaded and ran the new Qt. (almost 2 weeks of running), it
gets down to 19 weeks. When I awoke the next day. I see an error message that says:
"fail to connect best block" , then another message that said "Error: A Fatal internal
error occured see debug lg for details". WTF happened?

I have my wallet.dat file saved on a flash drive from my original wallet. My passphase is
also saved on my flash drive. I tried to run the programs 4 or 5 times, then I immediately
downloaded another version (I didn't delete the old one). I ran the version just downloaded
and I received the SAME error message. What do I do now. If the program wont open
how can I get to the debug log. I wouldn't know what to do once I got there. Please help
me....(layman terms p-l-e-a-s-e). I hope to hear from you very soon!!!!

Bitcoin network needs 3 confirmation, when its done. I recommend http://www.coinmotion.com/

UPdate:

As we speak, the latest core is running the index process. I can see btcs pending. I also see in the "sent" section the btc that didn't make it over to my
blockchain online wallet. Once the new core finishes updating will it automatically put the btcs that are "trapped", back in my desktop wallet, in essence
will this new core configure everything on its own. I may have a copy of a backup on my computer, but I backed up the LATEST backup before this problem
happened, and I saved it on a flash drive. I do intend to move my btc to my blockchain online wallet then get a new computer.  I just want to retrieve my btc
on my desktop wallet first...I would like to hear from you (soon).

Beware if he removed 1644, someone could have copies of your private keys.  Your service guy could have copied your wallet, and a virus could have.  1644 doesn't do that in the variants of which I am aware, but there could have been others or it could be a different variant.

So, if it were me, I'd move my coins to be safe.  Even if your service guy is honest, there could've been other people around who were not.