Database error: DB_RUNRECOVERY: Fatal error, run database recovery

[RaTTuS]

1) JackJack knows what he's talking about
2) stop the client
- make sure the client is stopped and there are no bitcoin processes running
3) backup the .bitcoin directory
4) delete these
blk0001.dat 
blkindex.dat
db.log 
debug.log
__db.001
__db.002
__db.003
__db.004
__db.005
__db.006
5) restart the client with a rescan i.e.
bitcoin -rescan
6) wait until all blocks are downloaded [if you have blk0001.dat and blkindex.dat on another machine this can speed the issue up]

[haydent]

after upgrading to latest version and restarting a few times i got this error mentioned. reinstalling (without uninstall) worked but only till i restarted the client the next time.

then thought id try deleting the file in database folder, this worked too, and lasts client restarts

also using an older version pre qt worked too, infact i have them both in the saem install as i didnt uninstall pre-qt version b4 installing qt version.

there's something about seeing the confirm numbers ticking over as your block chain updates that i miss from the old client.... ;(

[zveda2000]

OK I just had this happen to me:

1. Power in house went out causing PC to switch off.
2. When power came back on and I restarted, the bitcoin database was corrupted and caused the machine to completely freeze on the "Loading Addresses" splash screen, since I set my bitcoin-qt to run as PC boots up. I tried restarting about 5-10 times til I realised it was bitcoin-qt that was doing it. It made the machine completely unusable. Couldn't even kill any processes. The log file was saying something about "PANIC" and to do database recovery. Very annoying. I know a corrupted bitcoin database is bad but I don't see why it should break the whole machine. Even ctrl-alt-backspace wouldn't work anymore.

So I deleted all the database files and now bitcoin-qt opens fine and starts syncing. However, if while it is syncing I go into options, don't change anything, and click OK, that causes it to immediately crash for some reason. 

I am running version 0.5.0.1 BTW with Linux Mint 11.

Hope it helps.

[haydent]

i spoke too soon, i still get these crashes een with old version though maybe not as much, but deleting the database folder still works for me atleast temporarily.