Author

Topic: Corrupted Database: Is --reindex the only option? (Read 663 times)

sr. member
Activity: 318
Merit: 250
November 30, 2015, 09:52:22 AM
#4
Also, I do have the blocks and chainstate directories backed up as of a month ago. Would replacing the current directories (and only those two directories) with the backups be safe?

Yes, it would be safe and faster than -reindex but make sure to backup your wallet.dat before doing anything.
staff
Activity: 3458
Merit: 6793
Just writing some code
Also, I do have the blocks and chainstate directories backed up as of a month ago. Would replacing the current directories (and only those two directories) with the backups be safe?

Yes, that would be safe
full member
Activity: 185
Merit: 114
Also, I do have the blocks and chainstate directories backed up as of a month ago. Would replacing the current directories (and only those two directories) with the backups be safe?
full member
Activity: 185
Merit: 114
I've tried restarting with --rescan, but get this:

2015-11-30 13:34:22 Verifying last 288 blocks at level 3
2015-11-30 13:34:22 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2015-11-30 13:34:24 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2015-11-30 13:34:24 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2015-11-30 13:34:27 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2015-11-30 13:34:28 ERROR: DisconnectBlock() : undo data overwriting existing transaction
2015-11-30 13:34:29 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2015-11-30 13:34:30 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2015-11-30 13:35:27 ERROR: VerifyDB() : *** coin database inconsistencies found (last 7 blocks, 106434 good transactions before that)

2015-11-30 13:35:29 : Corrupted block database detected.


The last time I had to do a --reindex it took 4-5 days to complete, and that's a long time to be down. Any other options? Should --reindex take that long?

Jump to: