Topic: wallet problem (Read 4952 times)
well, i tried this tool. It found only 85 keys.. i will keep this drive until tool will support cryptographed wallets.
Tryed to do as you said, but there is same errors. Seems like wallet.dat corrupted... And i have not any other backups.
Anyway thanks for help.
Anyway thanks for help.
I know you already tried fixwallet.py, as described here:
[GUIDE] Simple wallet recovery using bitcointools
- https://bitcointalksearch.org/topic/guide-simple-wallet-recovery-using-bitcointools-11331
There is a tool that searches a disk device for strings that are bitcoin private keys.
I'm not sure if it will access a wallet.dat directly.
So maybe the file isn't readable as a BDB database but perhaps enough of the data inside is still instact and the private keys could be discovered:
Bitcoin private key/wallet.dat data recovery tool!
- https://bitcointalksearch.org/topic/bitcoin-private-keywalletdat-data-recovery-tool-25091
Tryed to do as you said, but there is same errors. Seems like wallet.dat corrupted... And i have not any other backups.
Anyway thanks for help.
Anyway thanks for help.
trying to do what client says. deleted all files and dirs except wallet.dat
Just to exclude the chance that a separate -datadir wasn't tested with -salvagewallet,
rename your
C:\Users\n.belenkov\AppData\Roaming\Bitcoin
to something else (e.g., Bitcoin.old)
Then create a new, empty
C:\Users\n.belenkov\AppData\Roaming\Bitcoin
and then in there place your wallet.dat from the backup
and then try to do the following (without -datadir):
bitcoin-qt.exe -salvagewallet
If that gives the same thing (unexpected file type or format) then that wallet.dat just does not seem to be readable.
Do you have any older backups of it?
trying to do what client says. deleted all files and dirs except wallet.dat
Logs are:
db.log
Code:
c:\Program Files (x86)\Bitcoin>bitcoin-qt.exe -datadir=d:\222 -salvagewallet
client blinking with small red window and crashes without any errors.Logs are:
db.log
Code:
__db_meta_setup: d:\222\wallet.dat: unexpected file type or format
debug.logCode:
Bitcoin version v0.7.1-beta (2012-10-09 13:22:09 -0400)
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 11/27/12 13:22:16
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Used data directory .lock
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
Failed to rename wallet.dat to wallet.1354022536.bak
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 11/27/12 13:22:16
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Used data directory .lock
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
Failed to rename wallet.dat to wallet.1354022536.bak
Also, worst case scenario ... v0.7.1 has a "-salvagewallet"
client started with window Code:
---------------------------
Bitcoin
---------------------------
Error initializing database environment .lock! To recover, BACKUP THAT DIRECTORY, then remove everything from it except for wallet.dat.
---------------------------
OK
---------------------------
Logs are:Bitcoin
---------------------------
Error initializing database environment .lock! To recover, BACKUP THAT DIRECTORY, then remove everything from it except for wallet.dat.
---------------------------
OK
---------------------------
db.log
Code:
Ignoring log file: d:\222\database\log.0000027152: magic number 3937372f, not 40988
Invalid log file: log.0000027152: Invalid argument
PANIC: Invalid argument
process-private: unable to find environment
Invalid log file: log.0000027152: Invalid argument
PANIC: Invalid argument
process-private: unable to find environment
debug.log
Code:
Bitcoin version v0.7.1-beta (2012-10-09 13:22:09 -0400)
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 11/27/12 13:17:27
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Used data directory .lock
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
ERROR: CDB() : error DB_RUNRECOVERY: Fatal error, run database recovery (-30974) opening database environment
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 11/27/12 13:17:27
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Used data directory .lock
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
ERROR: CDB() : error DB_RUNRECOVERY: Fatal error, run database recovery (-30974) opening database environment
run
db.log
debug.log
Code:
D:\bitcoin-0.6.3-win32>bitcoin-qt.exe -datadir=d:\222 -detachdb=1
logsdb.log
Code:
Ignoring log file: d:\222\database\log.0000027153: magic number bb3f3ce9, not 40988
Invalid log file: log.0000027153: Invalid argument
PANIC: Invalid argument
unable to join the environment
Invalid log file: log.0000027153: Invalid argument
PANIC: Invalid argument
unable to join the environment
debug.log
Code:
Bitcoin version v0.6.3-beta (2012-06-19 16:44:55 -0400)
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
************************
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
D:\bitcoin-0.6.3-win32\bitcoin-qt.exe in Runaway exception
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
************************
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
D:\bitcoin-0.6.3-win32\bitcoin-qt.exe in Runaway exception
seems like log file is corrupted?
Well it looks like it is trying to load the DB from Bitcoin directory and the log from 222. Which means it looks like the -detachdb isn't doing its job. Which, looks to be correct because I gave the wrong syntax. Should be "-detachdb=1", sorry.
Can you try that again?
Also, worst case scenario ... v0.7.1 has a "-salvagewallet"
* -salvagewallet command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.
if i run without -detachdb client crashes too. logs showing:
debug.log
db.log:
debug.log
Code:
Bitcoin version v0.6.3-beta (2012-06-19 16:44:55 -0400)
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
Loaded 0 addresses
addresses 344ms
Loading block index...
000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b
CBlock(hash=000000000019d6689c08, ver=1, hashPrevBlock=00000000000000000000, hashMerkleRoot=4a5e1e4baa, nTime=1231006505, nBits=1d00ffff, nNonce=2083236893, vtx=1)
CTransaction(hash=4a5e1e4baa, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 04ffff001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f72206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73)
CTxOut(nValue=50.00000000, scriptPubKey=04678afdb0fe5548271967f1a67130)
vMerkleTree: 4a5e1e4baa
SetBestChain: new best=000000000019d6689c08 height=0 work=4295032833
block index 264ms
Loading wallet...
************************
EXCEPTION: 11DbException
Db::open: Invalid argument
D:\bitcoin-0.6.3-win32\bitcoin-qt.exe in Runaway exception
EnvShutdown exception: DbEnv::close: Invalid argument (22)
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
Loaded 0 addresses
addresses 344ms
Loading block index...
000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b
CBlock(hash=000000000019d6689c08, ver=1, hashPrevBlock=00000000000000000000, hashMerkleRoot=4a5e1e4baa, nTime=1231006505, nBits=1d00ffff, nNonce=2083236893, vtx=1)
CTransaction(hash=4a5e1e4baa, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 04ffff001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f72206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73)
CTxOut(nValue=50.00000000, scriptPubKey=04678afdb0fe5548271967f1a67130)
vMerkleTree: 4a5e1e4baa
SetBestChain: new best=000000000019d6689c08 height=0 work=4295032833
block index 264ms
Loading wallet...
************************
EXCEPTION: 11DbException
Db::open: Invalid argument
D:\bitcoin-0.6.3-win32\bitcoin-qt.exe in Runaway exception
EnvShutdown exception: DbEnv::close: Invalid argument (22)
db.log:
Code:
__db_meta_setup: d:\222\wallet.dat: unexpected file type or format
Database handles still open at environment close
Open database handle: blkindex.dat/main
Open database handle: addr.dat/main
Database handles still open at environment close
Open database handle: blkindex.dat/main
Open database handle: addr.dat/main
Well, hopefully you have made (yet another) backup of the wallet and the logs so that no matter what happens you can get back to the point you are at right now.
But just launch bitcoin-qt from the command line and see if it can start. If not, debug.log will give info that will help determine what to do next.
Maybe detachdb might be needed.
$ Bitcoin-Qt -detachdb
Yes i have backups now But just launch bitcoin-qt from the command line and see if it can start. If not, debug.log will give info that will help determine what to do next.
Maybe detachdb might be needed.
$ Bitcoin-Qt -detachdb
run admin-cmd:
Code:
D:\bitcoin-0.6.3-win32>bitcoin-qt.exe -datadir=d:\222 -detachdb
client crashes. Logs showing:debug.log:
Code:
Bitcoin version v0.6.3-beta (2012-06-19 16:44:55 -0400)
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
************************
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
D:\bitcoin-0.6.3-win32\bitcoin-qt.exe in Runaway exception
Default data directory C:\Users\n.belenkov\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open LogDir=d:\222\database ErrorFile=d:\222\db.log
************************
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
D:\bitcoin-0.6.3-win32\bitcoin-qt.exe in Runaway exception
db.log:
Code:
Ignoring log file: d:\222\database\log.0000027153: magic number bb3f3ce9, not 40988
Invalid log file: log.0000027153: Invalid argument
PANIC: Invalid argument
unable to join the environment
Invalid log file: log.0000027153: Invalid argument
PANIC: Invalid argument
unable to join the environment
seems like log file is corrupted?
which command should i use? -rescan? or -salvagewallet?
Well, hopefully you have made (yet another) backup of the wallet and the logs so that no matter what happens you can get back to the point you are at right now.
But just launch bitcoin-qt from the command line and see if it can start. If not, debug.log will give info that will help determine what to do next.
Maybe detachdb might be needed.
$ Bitcoin-Qt -detachdb=1 [Edited]
wallet.dat (size 183Kb)
database\log.0000027152 (size 10Mb)
database\log.0000027153 (size 10Mb)
database\log.0000027152 (size 10Mb)
database\log.0000027153 (size 10Mb)
Yes, try launching bitcoin-qt (from the comand line) with those three files. If there is a problem the debug.log should give more info.
wallet.dat (size 183Kb)
database\log.0000027152 (size 10Mb)
database\log.0000027153 (size 10Mb)
database\log.0000027152 (size 10Mb)
database\log.0000027153 (size 10Mb)
Yes, try launching bitcoin-qt (from the comand line) with those three files. If there is a problem the debug.log should give more info.
is there problems with that my wallet was locked by passphrase?
After renaming successfully, if that error appears it might mean that the DB hadn't shut down properly, and now without the log files it cannot recover. But it isn't even getting past the rename it looks like.
I don't know Windows 8 ..., is there such a thing as an "admin account" ?
i have restored from old system:
wallet.dat (size 183Kb)
database\log.0000027152 (size 10Mb)
database\log.0000027153 (size 10Mb)
it these are logfiles of db?
is there problems with that my wallet was locked by passphrase?
After renaming successfully, if that error appears it might mean that the DB hadn't shut down properly, and now without the log files it cannot recover. But it isn't even getting past the rename it looks like.
I don't know Windows 8 ..., is there such a thing as an "admin account" ?
The log says that it was trying to rename the file. Check your permissions on the wallet.dat file, and possibly the directory. You should have full control of C:\Users\user\AppData\Roaming\Bitcoin\ but readable by no other user.
yes, i have all permissions on file and dir.db.log
Quote
Page 0: metadata page corrupted
[Edit: Did you launch which -detachdb first? I'm not sure if a new machine with the same name is the same as moving to a new directory but it won't hurt to try -detachdb.]
That doesn't look good though. Do you have any other backups (even older backups would have the keys for the next 100 transactions that were made)?
If not, you may want to try loading using the v0.6.x client and see if the problem persists with that release as well.
and i cant run -detachdb because client wont start.is there problems with that my wallet was locked by passphrase?
The log says that it was trying to rename the file. Check your permissions on the wallet.dat file, and possibly the directory. You should have full control of C:\Users\user\AppData\Roaming\Bitcoin\ but readable by no other user.
db.log
Quote
Page 0: metadata page corrupted
[Edit: Did you launch which -detachdb first? I'm not sure if a new machine with the same name is the same as moving to a new directory but it won't hurt to try -detachdb.]
That doesn't look good though. Do you have any other backups (even older backups would have the keys for the next 100 transactions that were made)?
If not, you may want to try loading using the v0.6.x client and see if the problem persists with that release as well.
i cant boot onto my old system. i have only wallet.dat
let the new version create a new wallet.
boot with win7 and send the funds to you new address(new wallet).
boot with win7 and send the funds to you new address(new wallet).
Jump to: