Bitcoin Forum
June 23, 2024, 04:30:23 AM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin-QT database corrupted  (Read 3137 times)
Valerian77 (OP)
Sr. Member
****
Offline Offline

Activity: 437
Merit: 255


View Profile
November 18, 2013, 10:49:21 AM
 #1

Hello

today the Bitcoin-QT suddenly stopped with the error message 'Database corrupted". The wallet is encrypted and it does not help to restore a formerly working backup of the wallet.dat.

How do I have to handle this?
BadAss.Sx
Legendary
*
Offline Offline

Activity: 1526
Merit: 1002


Bulletproof VPS/VPN/Email @ BadAss.Sx


View Profile WWW
November 18, 2013, 10:50:43 AM
 #2

Delete everything in you Bitcoin-Qt folder except the wallet.dat and start all over again. Watch out, this one takes days!
Valerian77 (OP)
Sr. Member
****
Offline Offline

Activity: 437
Merit: 255


View Profile
November 18, 2013, 11:37:23 AM
Last edit: November 18, 2013, 11:56:18 AM by Valerian77
 #3

Hmm -

is there any faster solution ?

here is the error from the debug.log:
Quote
init message: Verifiziere BlÃœcke...
Verifying last 288 blocks at level 3
No coin database inconsistencies in last 87 blocks (37317 transactions)
 block index           25330ms
init message: Lade Brieftasche...
nFileVersion = 80500
 wallet                   23ms
LevelDB read failure: Corruption: block checksum mismatch
*** Systemfehler: Database corrupted
init message: Lade Adressen...
Loaded 15462 addresses from peers.dat  99ms
Flush(false)
wallet.dat refcount=0
wallet.dat checkpoint
wallet.dat detach
wallet.dat closed
DBFlush(false) ended               7ms
StopNode()
Flushed 15462 addresses to peers.dat  54ms
Committing 40530 changed transactions to coin database...
Flush(true)
wallet.dat refcount=0
wallet.dat checkpoint
wallet.dat detach
wallet.dat closed
DBFlush(true) ended               7ms

the db.log file is empty.

The Bitcoin-QT version is v0.8.5-beta
wtogami
Sr. Member
****
Offline Offline

Activity: 263
Merit: 250



View Profile
November 18, 2013, 12:00:56 PM
 #4

This is Mac?

https://bitcointalk.org/index.php?topic=337294.0
You will want to read this.

If you appreciate my work please consider making a small donation.
BTC:  1LkYiL3RaouKXTUhGcE84XLece31JjnLc3      LTC:  LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9
GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
/dev/null
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250


View Profile
November 18, 2013, 12:03:07 PM
 #5

Import your wallet into some other client  like electrum,armory,blockchain and use it.
Thats the fastest way to access your coins.

Valerian77 (OP)
Sr. Member
****
Offline Offline

Activity: 437
Merit: 255


View Profile
November 18, 2013, 12:06:09 PM
 #6

OK I made the hard step and deleted everything except the wallet.dat.

Now the Bitcoin-QT client works again but has to reload 252 weeks of transaction history.

Not a very big issue. But I am little concerned about the appearance of this bug in this version on my system.
That is because
1. the client version is the most resent one
2. hard disc is a SSD 830 which should not create any read/write errors
3. the system (Asus N56VZ, 8GB RAM, I7 2610QM) should have enough capacity in any manner to handle the Bitcoin wallet

One weak point may be the operating system - Windows7 Home Premium. I use this because it was delivered with the laptop and it worked so far with all drivers.

I have no explanation for this serious bug.

From this experience I will definitely switch to cold paper wallets.
Valerian77 (OP)
Sr. Member
****
Offline Offline

Activity: 437
Merit: 255


View Profile
November 18, 2013, 12:36:26 PM
 #7

Maybe I got the root cause for the problem. Some time ago I started to use a RAM disc for all temporary files. This disc is limited in size (compared to the hard disc). I never really switch off the system. Probably the RAM disc was full. - I am not 100% sure but it seems to be the only possibility.

I do not know if this may be an issue for the Bitcoin-Qt behavior. But at least it should be considered in some kind of diagnosis information. Currently the only information available is the debug.log (this is not in a temporary location) is:
Quote
LevelDB read failure: Corruption: block checksum mismatch
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!