wallet.dat got corrupted

[feeleep75]

Hi,

I send ZEC from T to Z address and once received by Z address, daemon started to crashing and it was restarted by monitoring scripts. I took a backup then of wallet.dat but now I cannot recover in in any way. I tried -reindex and -salvagewallet but it does not help - I have only logs like this:

2016-10-28 20:44:42 CDBEnv::Salvage: Database salvage found errors, all data may not be recoverable. 2016-10-28 20:44:42 Salvage(aggressive) found no records in wallet.1477687482.bak. 2016-10-28 20:44:42 Shutdown: In progress...

I did an investigation with daira and we found following:

db.log:

BDB2506 file unknown has LSN 1/189046, past end of log at 1/1076
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
wallet.1477681161.bak: BDB0090 DB_VERIFY_BAD: Database verification failed
BDB1538 Program version 6.2 doesn't match environment version 5.3
BDB2506 file unknown has LSN 1/189046, past end of log at 1/1168
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
BDB0522 Page 0: metadata page corrupted
BDB0523 Page 0: could not check metadata page
wallet.dat: BDB0090 DB_VERIFY_BAD: Database verification failed
BDB2506 file unknown has LSN 1/189046, past end of log at 1/2216
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
wallet.1477687482.bak: BDB0090 DB_VERIFY_BAD: Database verification failed
BDB2506 file unknown has LSN 1/189046, past end of log at 1/2216
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
BDB2506 file unknown has LSN 1/189046, past end of log at 1/2216
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
BDB2506 file unknown has LSN 1/189046, past end of log at 1/2216
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
BDB2506 file unknown has LSN 1/189046, past end of log at 1/2308
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
BDB0522 Page 0: metadata page corrupted
BDB0523 Page 0: could not check metadata page
wallet.dat: BDB0090 DB_VERIFY_BAD: Database verification failed
BDB2506 file unknown has LSN 1/189046, past end of log at 1/3356
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
wallet.1477688722.bak: BDB0090 DB_VERIFY_BAD: Database verification failed

dpkg -l 'libdb*':

un  libdb4.6++-dev              <none>             <none>             (no description available)
un  libdb4.6-dev                <none>             <none>             (no description available)
un  libdb4.7++-dev              <none>             <none>             (no description available)
un  libdb4.7-dev                <none>             <none>             (no description available)
un  libdb4.8++-dev              <none>             <none>             (no description available)
un  libdb4.8-dev                <none>             <none>             (no description available)
ii  libdb5.1:amd64              5.1.29-7ubuntu1    amd64              Berkeley v5.1 Database Libraries [runtime]
ii  libdb5.1++:amd64            5.1.29-7ubuntu1    amd64              Berkeley v5.1 Database Libraries for C++ [runtime]
ii  libdb5.1++-dev              5.1.29-7ubuntu1    amd64              Berkeley v5.1 Database Libraries for C++ [development]
ii  libdb5.1-dev                5.1.29-7ubuntu1    amd64              Berkeley v5.1 Database Libraries [development]
ii  libdb5.3:amd64              5.3.28-3ubuntu3    amd64              Berkeley v5.3 Database Libraries [runtime]
ii  libdbus-1-3:amd64           1.6.18-0ubuntu4.3  amd64              simple interprocess messaging system (library)
ii  libdbus-glib-1-2:amd64      0.100.2-1          amd64              simple interprocess messaging system (GLib-based shared lib

[feeleep75]

this may be a serious bug but I finally made recovery:

1. compiled BDB version 6.2 and did a dump of wallet.dat
2. on separate machine i installed db-util ver 5.3 and loaded the dump
3. started daemon with -salvagewallet

[ebfull]

If people are encountering these issues with t-addrs, it is probably a BDB bug?

[blbradley]

I can confirm that this is still an issue (from using ZenCash). Except my log did not have this line:

BDB1538 Program version 6.2 doesn't match environment version 5.3

My wallet will not verify with 5.3 but will with 6.2.

$ db_verify wallet.dat
db_verify: BDB1009 wallet.dat: unsupported btree version: 10
db_verify: BDB0526 Page 0: unsupported DB version 10; extraneous errors may result
db_verify: BDB0547 Page 0: unsupported database version 10; extraneous errors may result
db_verify: BDB0547 Page 2: unsupported database version 10; extraneous errors may result
db_verify: wallet.dat: BDB0090 DB_VERIFY_BAD: Database verification failed
BDB5105 Verification of wallet.dat failed.
$ ~/lib/db-6.2.32/build_unix/db_verify wallet.dat
BDB5105 Verification of wallet.dat succeeded.

[rofllolomg]

This might seem silly, but would there be anywhere anyone could teach me how to do this to fix this problem? Have the same issue after trying to clear out the DB due to checksum mismatch, have this issue but afraid I'm terribly uninformed when it comes to this (i use Windows 10 and just made Debian VM)

[zzzman20]

Hello, I am having this same issue too. How can I fix the corrupted wallet or extract the private keys from it? Unfortunately I'm not very familiar with linux. I did not have my private keys backed up.

[nuttycom]

We need to add documentation for how to perform recovery on corrupted wallets.