|
Title: wallet problem Post by: nikolaicheg on November 26, 2012, 08:13:53 AM Hello! i have a problem with wallet. I had win7 like main OS. And a few days ago I installed win8 onto new disk. Last bitcoin-qt was v0.6.2-beta. Wallet was locked py password.
I installed win8, installed last version of client. Put wallet.dat in to the bitcoin data dir, and client won't start. Logs showing: debug.log Quote 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/26/12 06:11:21 Default data directory C:\Users\user\AppData\Roaming\Bitcoin Used data directory C:\Users\user\AppData\Roaming\Bitcoin dbenv.open LogDir=C:\Users\user\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\user\AppData\Roaming\Bitcoin\db.log Failed to rename wallet.dat to wallet.1353910281.bak db.log Quote Page 0: metadata page corrupted Page 0: could not check metadata page wallet.dat: DB_VERIFY_BAD: Database verification failed __db_meta_setup: C:\Users\user\AppData\Roaming\Bitcoin\wallet.dat: unexpected file type or format I tried to use bitcointools: Quote D:\bitcointools-master>fixwallet.py The client is closed, there is no process in task manager. Tryed to use "-rescan" option, the same result.ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again. Tryed to do like here https://bitcointalk.org/index.php?topic=11331.0 - the result is the same... any ideas what to do? it willl be so sad to lose half year bitcoins...(( Title: Re: wallet problem Post by: 1Pakis on November 26, 2012, 08:23:59 AM let the new version create a new wallet.
boot with win7 and send the funds to you new address(new wallet). Title: Re: wallet problem Post by: nikolaicheg on November 26, 2012, 08:33:18 AM i cant boot onto my old system. i have only wallet.dat :(
Title: Re: wallet problem Post by: Stephen Gornick on November 26, 2012, 11:39:39 AM 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. Title: Re: wallet problem Post by: sdp on November 26, 2012, 11:51:32 AM 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.
Title: Re: wallet problem Post by: nikolaicheg on November 26, 2012, 12:08:08 PM 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. is there problems with that my wallet was locked by passphrase? Title: Re: wallet problem Post by: Stephen Gornick on November 26, 2012, 12:25:41 PM 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" ? Title: Re: wallet problem Post by: nikolaicheg on November 26, 2012, 12:53:44 PM 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? Title: Re: wallet problem Post by: Stephen Gornick on November 26, 2012, 09:50:10 PM wallet.dat (size 183Kb) 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. Title: Re: wallet problem Post by: nikolaicheg on November 27, 2012, 06:07:30 AM wallet.dat (size 183Kb) 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. Title: Re: wallet problem Post by: Stephen Gornick on November 27, 2012, 06:30:33 AM 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] Title: Re: wallet problem Post by: nikolaicheg on November 27, 2012, 06:48:46 AM 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. 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 debug.log: Code: Bitcoin version v0.6.3-beta (2012-06-19 16:44:55 -0400) db.log: Code: Ignoring log file: d:\222\database\log.0000027153: magic number bb3f3ce9, not 40988 seems like log file is corrupted? Title: Re: wallet problem Post by: nikolaicheg on November 27, 2012, 06:54:55 AM if i run without -detachdb client crashes too. logs showing:
debug.log Code: Bitcoin version v0.6.3-beta (2012-06-19 16:44:55 -0400) db.log: Code: __db_meta_setup: d:\222\wallet.dat: unexpected file type or format Title: Re: wallet problem Post by: Stephen Gornick on November 27, 2012, 11:23:35 AM 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. Title: Re: wallet problem Post by: nikolaicheg on November 27, 2012, 01:08:37 PM run
Code: D:\bitcoin-0.6.3-win32>bitcoin-qt.exe -datadir=d:\222 -detachdb=1 db.log Code: Ignoring log file: d:\222\database\log.0000027153: magic number bb3f3ce9, not 40988 debug.log Code: Bitcoin version v0.6.3-beta (2012-06-19 16:44:55 -0400) Title: Re: wallet problem Post by: nikolaicheg on November 27, 2012, 01:20:09 PM Also, worst case scenario ... v0.7.1 has a "-salvagewallet" client started with window Code: --------------------------- db.log Code: Ignoring log file: d:\222\database\log.0000027152: magic number 3937372f, not 40988 debug.log Code: Bitcoin version v0.7.1-beta (2012-10-09 13:22:09 -0400) Title: Re: wallet problem Post by: nikolaicheg on November 27, 2012, 01:23:20 PM trying to do what client says. deleted all files and dirs except wallet.dat
Code: c:\Program Files (x86)\Bitcoin>bitcoin-qt.exe -datadir=d:\222 -salvagewallet Logs are: db.log Code: __db_meta_setup: d:\222\wallet.dat: unexpected file type or format Code: Bitcoin version v0.7.1-beta (2012-10-09 13:22:09 -0400) Title: Re: wallet problem Post by: Stephen Gornick on November 27, 2012, 09:57:59 PM 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? Title: Re: wallet problem Post by: nikolaicheg on November 28, 2012, 06:38:02 AM 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. Title: Re: wallet problem Post by: Stephen Gornick on November 28, 2012, 07:45:24 AM 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. I know you already tried fixwallet.py, as described here: [GUIDE] Simple wallet recovery using bitcointools - http://bitcointalk.org/index.php?topic=11331.0 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! - http://bitcointalk.org/index.php?topic=25091.0 Title: Re: wallet problem Post by: nikolaicheg on November 29, 2012, 06:08:26 AM well, i tried this tool. It found only 85 keys.. i will keep this drive until tool will support cryptographed wallets.
|