Bitcoin Forum
May 04, 2024, 05:13:55 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: "error: a fatal internal error occurred. see debug.log for details"  (Read 2442 times)
orsotheysaid (OP)
Full Member
***
Offline Offline

Activity: 153
Merit: 100


View Profile
July 28, 2015, 01:32:29 PM
 #1

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)
1714842835
Hero Member
*
Offline Offline

Posts: 1714842835

View Profile Personal Message (Offline)

Ignore
1714842835
Reply with quote  #2

1714842835
Report to moderator
1714842835
Hero Member
*
Offline Offline

Posts: 1714842835

View Profile Personal Message (Offline)

Ignore
1714842835
Reply with quote  #2

1714842835
Report to moderator
1714842835
Hero Member
*
Offline Offline

Posts: 1714842835

View Profile Personal Message (Offline)

Ignore
1714842835
Reply with quote  #2

1714842835
Report to moderator
Bitcoin mining is now a specialized and very risky industry, just like gold mining. Amateur miners are unlikely to make much money, and may even lose money. Bitcoin is much more than just mining, though!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714842835
Hero Member
*
Offline Offline

Posts: 1714842835

View Profile Personal Message (Offline)

Ignore
1714842835
Reply with quote  #2

1714842835
Report to moderator
1714842835
Hero Member
*
Offline Offline

Posts: 1714842835

View Profile Personal Message (Offline)

Ignore
1714842835
Reply with quote  #2

1714842835
Report to moderator
AtheistAKASaneBrain
Hero Member
*****
Offline Offline

Activity: 770
Merit: 509


View Profile
July 28, 2015, 02:25:26 PM
 #2

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)
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6581


Just writing some code


View Profile WWW
July 28, 2015, 03:14:18 PM
 #3

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.

manselr
Legendary
*
Offline Offline

Activity: 868
Merit: 1004


View Profile
July 28, 2015, 06:24:38 PM
 #4

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.
Newar
Legendary
*
Offline Offline

Activity: 1358
Merit: 1000


https://gliph.me/hUF


View Profile
July 28, 2015, 06:25:54 PM
 #5

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

It depends on your hardware.

OTC rating | GPG keyid 1DC91318EE785FDE | Gliph: lightning bicycle tree music | Mycelium, a swift & secure Bitcoin client for Android | LocalBitcoins
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!