fredolin (OP)
Newbie
Offline
Activity: 7
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2016, 03:40:10 PM |
|
In 2013 I had several bitcoins in my wallet. The wallet is encrypted.
Now, years later, I am trying to bring the wallet back to life.
I installed the actual bitcoin core and I exchanged the wallet.dat with my old wallet.dat.
The blockchain is loading, but suddenly the application hangs with "internal error, see log file for details". I can restart the client, then it starts again but after some time this happens again.
The logfile says: ------------------------------------------------------------------------------------------------------------------------------------ 2016-10-16 15:19:40 *** System error while flushing: CDB: Error -30974, can't open database 2016-10-16 15:21:09 ERROR: ProcessNewBlock: ActivateBestChain failed 2016-10-16 15:21:10 tor: Thread interrupt 2016-10-16 15:21:10 opencon thread interrupt 2016-10-16 15:21:10 net thread interrupt 2016-10-16 15:21:10 scheduler thread interrupt 2016-10-16 15:21:10 addcon thread interrupt 2016-10-16 15:21:10 torcontrol thread exit 2016-10-16 15:21:10 msghand thread interrupt 2016-10-16 15:21:10 Shutdown: In progress... 2016-10-16 15:21:10 StopNode() 2016-10-16 15:21:10 UPNP_DeletePortMapping() returned: 0 2016-10-16 15:21:10 upnp thread interrupt 2016-10-16 15:21:11 *** System error while flushing: CDB: Error -30974, can't open database 2016-10-16 15:21:17 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery 2016-10-16 15:21:17 Shutdown: done --------------------------------------------------------------------------------------------------------------------------
I am not able to work with that wallet anymore.
If I use the empty wallet.dat, the complete blockchain loads, but if I am replacing the wallet with the old wallet, this error happens again. I tried another PC as well, I found no solution.
Any help is appreciated.
|
|
|
|
|
fredolin (OP)
Newbie
Offline
Activity: 7
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2016, 06:17:17 PM |
|
Thank you very much for you answer, but the same is happening again. It loads several weeks of blockchain. Then again error. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3486
Merit: 6824
Just writing some code
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2016, 06:20:56 PM |
|
Thank you very much for you answer, but the same is happening again. It loads several weeks of blockchain. Then again error. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Try again but with -salvagewallet instead. Can you also post the entire debug.log?
|
|
|
|
fredolin (OP)
Newbie
Offline
Activity: 7
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2016, 07:24:34 PM |
|
salvagewallet doesn't work at all. Thats the last part of the debug.log. Sorry, but I can see no possibility to add an attachement and the whole debug.log is too much text.
2016-10-16 19:19:12 Bitcoin version v0.13.0 2016-10-16 19:19:12 InitParameterInteraction: parameter interaction: -salvagewallet=1 -> setting -rescan=1 2016-10-16 19:19:12 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2016-10-16 19:19:12 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2016-10-16 19:19:14 Default data directory C:\Users\TuF\AppData\Roaming\Bitcoin 2016-10-16 19:19:14 Using data directory C:\Users\TuF\AppData\Roaming\Bitcoin 2016-10-16 19:19:14 Using config file C:\Users\TuF\AppData\Roaming\Bitcoin\bitcoin.conf 2016-10-16 19:19:14 Using at most 125 connections (2048 file descriptors available) 2016-10-16 19:19:14 Using 2 threads for script verification 2016-10-16 19:19:14 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2016-10-16 19:19:14 scheduler thread start 2016-10-16 19:19:14 Using wallet wallet.dat 2016-10-16 19:19:14 init message: Verifiziere Wallet... 2016-10-16 19:19:14 CDBEnv::Open: LogDir=C:\Users\TuF\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\TuF\AppData\Roaming\Bitcoin\db.log 2016-10-16 19:19:14 Renamed wallet.dat to wallet.1476645554.bak 2016-10-16 19:19:14 Salvage(aggressive) found 205 records 2016-10-16 19:19:14 Bound to [::]:8333 2016-10-16 19:19:14 Bound to 0.0.0.0:8333 2016-10-16 19:19:14 Cache configuration: 2016-10-16 19:19:14 * Using 2.0MiB for block index database 2016-10-16 19:19:14 * Using 8.0MiB for chain state database 2016-10-16 19:19:14 * Using 290.0MiB for in-memory UTXO set 2016-10-16 19:19:14 init message: Lade Blockindex... 2016-10-16 19:19:14 Opening LevelDB in C:\Users\TuF\AppData\Roaming\Bitcoin\blocks\index 2016-10-16 19:19:14 Opened LevelDB successfully 2016-10-16 19:19:14 Using obfuscation key for C:\Users\TuF\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000 2016-10-16 19:19:14 Opening LevelDB in C:\Users\TuF\AppData\Roaming\Bitcoin\chainstate 2016-10-16 19:19:14 Opened LevelDB successfully 2016-10-16 19:19:14 Using obfuscation key for C:\Users\TuF\AppData\Roaming\Bitcoin\chainstate: c43333cab3d5d360 2016-10-16 19:19:25 LoadBlockIndexDB: last block file = 81 2016-10-16 19:19:25 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=71, size=7994994, heights=256960...258007, time=2013-09-09...2013-09-14) 2016-10-16 19:19:25 Checking all blk files are present... 2016-10-16 19:19:25 LoadBlockIndexDB: transaction index disabled 2016-10-16 19:19:25 LoadBlockIndexDB: hashBestChain=000000000000000a152787fd64e5e892a14643c8075daa6949435007bb2e7b9d height=257763 date=2013-09-13 16:02:14 progress=0.075893 2016-10-16 19:19:25 init message: Rewinding blocks... 2016-10-16 19:19:28 init message: Verifiziere Blöcke... 2016-10-16 19:19:28 Verifying last 288 blocks at level 3 2016-10-16 19:19:28 [0%]...[10%]...[20%]...[30%]...[40%]...[50%]...[60%]...[70%]...[80%]...[90%]...[DONE]. 2016-10-16 19:20:42 No coin database inconsistencies in last 289 blocks (69670 transactions) 2016-10-16 19:20:42 block index 88442ms 2016-10-16 19:20:42 init message: Lade Wallet... 2016-10-16 19:20:42 nFileVersion = 130000 2016-10-16 19:20:42 Keys: 0 plaintext, 201 encrypted, 0 w/ metadata, 201 total 2016-10-16 19:20:42 Performing wallet upgrade to 60000 2016-10-16 19:20:42
************************ EXCEPTION: St13runtime_error CWallet::GenerateNewKey(): AddKey failed C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception
2016-10-16 19:21:28 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3486
Merit: 6824
Just writing some code
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 16, 2016, 07:49:03 PM |
|
It's failing to add a key to your wallet. Check your permissions on that wallet.dat file and make sure that your user can both read and write to it.
Also check that you have enough disk space and that the drive isn't full.
|
|
|
|
fredolin (OP)
Newbie
Offline
Activity: 7
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2016, 05:08:28 AM |
|
Thank you very much for your answers. I tried -upgradewallet and -salvagewallet. Same error as described above happens again. The wallet.dat file was stored on a internet server in 2013 and I moved it back to my computer. I enabled now this http://www.wintotal.de/images/tipps/eigenschaften.sicherheit.zulassen1.pngSame problems again. The disk is not full. warner, I will follow your suggestion today evening, thank you.
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3486
Merit: 6824
Just writing some code
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 17, 2016, 05:26:13 AM |
|
Did you check the file permissions? It should be under the "security" tab of the properties dialog. You need to make sure that your user account can write to that file.
|
|
|
|
fredolin (OP)
Newbie
Offline
Activity: 7
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 18, 2016, 07:26:00 PM |
|
I checked the permissions. The file is not write- or readprotected.
If I write in the console walletpassphrase ... 300
The answer is:
CWallet::GenerateNewKey(): AddKey failed (code -1)
What do I need to access to this file?
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3486
Merit: 6824
Just writing some code
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 18, 2016, 08:27:19 PM |
|
I checked the permissions. The file is not write- or readprotected.
If I write in the console walletpassphrase ... 300
The answer is:
CWallet::GenerateNewKey(): AddKey failed (code -1)
What do I need to access to this file?
At this point, I am not sure what exactly is wrong and how to fix it. The problem lies in the wallet and Bitcoin Core being unable to write to it. Can you post the contents of the db.log (not debug.log). There may be something useful in there.
|
|
|
|
cr1776
Legendary
Offline
Activity: 4144
Merit: 1307
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 19, 2016, 12:03:48 AM |
|
Before you continue, make a few backups. >"I checked the permissions. The file is not write- or readprotected."
1. What version of Windows is this? 2. a.If you check permissions for wallet.dat, you said it isn't read or write protected, did you mean it isn't set to "read only" in attributes? Did you check other permissions? b. Are you listed as the owner?
2. Do the attributes from the newly created wallet.dat match those of the old one?
|
|
|
|
fredolin (OP)
Newbie
Offline
Activity: 7
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 19, 2016, 07:46:49 PM |
|
System: Win7 I am listed as the owner
I checked all permissions indicated in the properties window and in the cmd-window (attrib command)
Everything seems ok.
From the db.log:
file wallet.dat has LSN 1/109756, past end of log at 1/333 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment DB_ENV->log_flush: LSN of 1/109756 past current end-of-log of 1/333 Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment PANIC: DB_RUNRECOVERY: Fatal error, run database recovery wallet.dat: unable to flush page: 7 txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3486
Merit: 6824
Just writing some code
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 19, 2016, 08:14:53 PM |
|
System: Win7 I am listed as the owner
I checked all permissions indicated in the properties window and in the cmd-window (attrib command)
Everything seems ok.
From the db.log:
file wallet.dat has LSN 1/109756, past end of log at 1/333 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment DB_ENV->log_flush: LSN of 1/109756 past current end-of-log of 1/333 Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment PANIC: DB_RUNRECOVERY: Fatal error, run database recovery wallet.dat: unable to flush page: 7 txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery
So that means that your wallet.dat file is corrupted. That means that while you were moving that file around something got corrupted. Try getting a copy of the file as close to the original from the server.
|
|
|
|
fredolin (OP)
Newbie
Offline
Activity: 7
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 26, 2016, 09:00:43 PM |
|
Thank you all for your answers. I was able to save all coins in the wallet. I installed python 2.7, then extracted all keys with pywallet.py. This was working somehow. Then transfered the key to electrum with keys-> sweep. ![Cool](https://bitcointalk.org/Smileys/default/cool.gif)
|
|
|
|
|