"error: a fatal internal error occurred. see debug.log for details"

Newar

legendary

Activity: 1358

Merit: 1001

https://gliph.me/hUF

Quote from: manselr on July 28, 2015, 01:24:38 PM

I wonder how long does it take to reindex the database? [...]

It depends on your hardware.

manselr

legendary

Activity: 868

Merit: 1006

Quote from: achow101 on July 28, 2015, 10:14:18 AM

You need to reindex the database. That will take some time but it WON"T download the entire blockchain again. As long as you don't delete the .blk files.

I wonder how long does it take to reindex the database? I had the same problem or similar, i've used the -reindex cvar and it has been like 5 hours and the bar is not even halfway through. Jesus Christ this is annoying. I expected it would be faster but it's not. It says "reindexing blocks on disk" and still 1 year and 6 weeks behind.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

You need to reindex the database. That will take some time but it WON"T download the entire blockchain again. As long as you don't delete the .blk files.

AtheistAKASaneBrain

hero member

Activity: 770

Merit: 509

Have you tried running -reindex to see if it fixes it? You can also try deleting the latest blk files (not sure if you would need to download the latest files with different extensions too)

orsotheysaid

full member

Activity: 153

Merit: 100

Followed by

"error: failed to connect best block"

Then "bitcoin-qt has failed".. etc, windows error. After closing I checked debug.log:

2015-07-28 11:16:21 Corruption: block checksum mismatch
2015-07-28 11:16:21 *** System error while flushing: Database corrupted
2015-07-28 11:20:59 Shutdown: In progress...
2015-07-28 11:20:59 StopNode()
2015-07-28 11:20:59 Corruption: block checksum mismatch
2015-07-28 11:20:59 *** System error while flushing: Database corrupted

Before this its just all "2015-07-28 11:16:18 UpdateTip: new best=".... type of lines.

What can I do? No way im going to re-download the entire thing again.. HDD is new and in good condition, same for RAM.

Im using 0.10.2 (was too lazy to update to 0.11 to be honest)

Topic: "error: a fatal internal error occurred. see debug.log for details" (Read 2471 times)