Bitcoin Forum
November 18, 2017, 05:24:12 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Bitcoin core 15.0.1 corrupted database loop  (Read 482 times)
Borisz
Sr. Member
****
Offline Offline

Activity: 476



View Profile
October 29, 2017, 12:03:23 PM
 #1

Hi,

when I upgraded to bitcoin core 15.0.1 suddenly I got an error saying my database was corrupted. The client prompted for permission rebuilding the blockchain and started syncing.
Since then it keeps crashing with an error

Code:
2017-10-29 11:13:38 LevelDB read failure: Corruption: block checksum mismatch

If I restart, it syncs another few weeks of database, but crashes again.

Is there anyone getting a similar issue?

I keep restarting and will see if I manage to catch up eventually, I was just wondering if this is a one-off issue.
1510982652
Hero Member
*
Offline Offline

Posts: 1510982652

View Profile Personal Message (Offline)

Ignore
1510982652
Reply with quote  #2

1510982652
Report to moderator
1510982652
Hero Member
*
Offline Offline

Posts: 1510982652

View Profile Personal Message (Offline)

Ignore
1510982652
Reply with quote  #2

1510982652
Report to moderator
Transactions can optionally carry transaction fees. Whoever mines the block which ends up containing your transaction will get the fee. The Bitcoin client will sometimes force you to pay a fee when it thinks that no miner will accept your transaction otherwise.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1510982652
Hero Member
*
Offline Offline

Posts: 1510982652

View Profile Personal Message (Offline)

Ignore
1510982652
Reply with quote  #2

1510982652
Report to moderator
1510982652
Hero Member
*
Offline Offline

Posts: 1510982652

View Profile Personal Message (Offline)

Ignore
1510982652
Reply with quote  #2

1510982652
Report to moderator
1510982652
Hero Member
*
Offline Offline

Posts: 1510982652

View Profile Personal Message (Offline)

Ignore
1510982652
Reply with quote  #2

1510982652
Report to moderator
jackg
Hero Member
*****
Offline Offline

Activity: 826

1JRmjyGo3kpdXcQeAeTBmGtgkC1AomHKED


View Profile
October 29, 2017, 12:47:24 PM
 #2

What block does this happen at, is it always the same one?

What version were you running before? If you downgrade to that is there the same issue still.

If both wallets cause an issue, it may be necessary to delete the blocks and chainstate folder and try again cleanly. (Also, do you have any av software installed that could interfere with the core?

achow101
Moderator
Legendary
*
Offline Offline

Activity: 1218


17kKQppUsngUiByDsce4JXoZEjjpvX9bpR


View Profile WWW
October 29, 2017, 05:44:47 PM
 #3

Post your entire debug.log file. It is likely that you will need to reindex and possibly redownload the blockchain.

          ▄█████▄
        ▄█████████▄
      ▄████▀   ▀████▄
    ▄████▀   ▄ ▄█▀████▄
  ▄████▀   ▄███▀   ▀████▄
▄████▀   ▄███▀   ▄   ▀████▄
█████   ███▀   ▄███   █████
▀████▄   ▀██▄▄███▀   ▄████▀
  ▀████▄   ▀███▀   ▄████▀
    ▀████▄       ▄████▀
      ▀████▄   ▄████▀
        ▀███  ████▀
          ▀█▄███▀
.
|
.
|
          ▄█████▄
        ▄█████████▄
      ▄████▀   ▀████▄
    ▄████▀   ▄ ▄█▀████▄
  ▄████▀   ▄███▀   ▀████▄
▄████▀   ▄███▀   ▄   ▀████▄
█████   ███▀   ▄███   █████
▀████▄   ▀██▄▄███▀   ▄████▀
  ▀████▄   ▀███▀   ▄████▀
    ▀████▄       ▄████▀
      ▀████▄   ▄████▀
        ▀███  ████▀
          ▀█▄███▀
unthy
Borisz
Sr. Member
****
Offline Offline

Activity: 476



View Profile
October 30, 2017, 06:59:14 AM
 #4

In the meanwhile I already started re-downloading the blockchain. The question was more like if this is a one-off issue. Frankly, it's a bit of a pain to download the whole thing again after a wallet upgrade.

Thanks.
jackg
Hero Member
*****
Offline Offline

Activity: 826

1JRmjyGo3kpdXcQeAeTBmGtgkC1AomHKED


View Profile
October 30, 2017, 08:57:19 AM
 #5

In the meanwhile I already started re-downloading the blockchain. The question was more like if this is a one-off issue. Frankly, it's a bit of a pain to download the whole thing again after a wallet upgrade.

Thanks.

It shouldn't happen repeatedly.
Although I thought you said it gave that error every time you wanted to reindex, I .must have got confused somewhere.

A copy of the debug log would be helpful examining the issue still though.

Edit: ah I reread the OP. See if the reindexing issue finishes fine and if it reindexes with that error again, it might be a hard drive issue.

Borisz
Sr. Member
****
Offline Offline

Activity: 476



View Profile
November 06, 2017, 10:23:34 PM
 #6

Ok, so after downloading the blockchain and re-indexing a few times, I'm still stuck. The outputs below are after that I have reinstalled bitcoin core.

Code:
2017-11-06 19:37:05 UpdateTip: new best=0000000000000000032894a63a03884fc3fd4b5c98de5e2cc7066ce764dc447e height=445828 version=0x20000000 log2_work=85.748268 tx=183429132 date='2016-12-30 15:58:45' progress=0.681485 cache=325.9MiB(2116235txo)
2017-11-06 19:37:05 LevelDB read failure: Corruption: block checksum mismatch
2017-11-06 19:37:05 Corruption: block checksum mismatch
2017-11-06 19:38:07 Error reading from database: Database corrupted

On a clean wallet:
Code:
2017-11-06 20:02:45 UpdateTip: new best=000000000000000002e901d8303d43e8bbd4d8f76a66cf2f2da064e8fbb31dbe height=448192 version=0x20000000 log2_work=85.819278 tx=187733247 date='2017-01-14 21:07:23' progress=0.697464 cache=238.2MiB(1397685txo)
2017-11-06 20:02:45 LevelDB read failure: Corruption: block checksum mismatch
2017-11-06 20:02:45 Corruption: block checksum mismatch
2017-11-06 20:02:56 Error reading from database: Database corrupted

In addition, during syncing my wallet shows transactions with the wrong date. Transactions from 2013 show up as they were in 15/10/2017, which is definitely wrong (aka at 60% blockchain I seetransactions with 2017 datestamp). Re-indexing does not help this.
The drive is healthy, plenty of space and the error occurs regardless if I use Windows or Linux. (According to various scans, no bad sector, is present. The drive is ~6 monnths old, so statistically it should be the smallest "issue factor")
I have even went so far as to completely uninstall bitcoin core, create a fresh wallet and start downloading the blockchain. If I put back my own wallet, I get the error and the messed-up datestamps for transactions. If I let the fresh wallet, it also gives the error (as above).
Spendulus
Legendary
*
Offline Offline

Activity: 1694



View Profile
November 07, 2017, 02:41:46 AM
 #7

Ok, so after downloading the blockchain and re-indexing a few times, I'm still stuck. The outputs below are after that I have reinstalled bitcoin core.

Code:
2017-11-06 19:37:05 UpdateTip: new best=0000000000000000032894a63a03884fc3fd4b5c98de5e2cc7066ce764dc447e height=445828 version=0x20000000 log2_work=85.748268 tx=183429132 date='2016-12-30 15:58:45' progress=0.681485 cache=325.9MiB(2116235txo)
2017-11-06 19:37:05 LevelDB read failure: Corruption: block checksum mismatch
2017-11-06 19:37:05 Corruption: block checksum mismatch
2017-11-06 19:38:07 Error reading from database: Database corrupted

On a clean wallet:
Code:
2017-11-06 20:02:45 UpdateTip: new best=000000000000000002e901d8303d43e8bbd4d8f76a66cf2f2da064e8fbb31dbe height=448192 version=0x20000000 log2_work=85.819278 tx=187733247 date='2017-01-14 21:07:23' progress=0.697464 cache=238.2MiB(1397685txo)
2017-11-06 20:02:45 LevelDB read failure: Corruption: block checksum mismatch
2017-11-06 20:02:45 Corruption: block checksum mismatch
2017-11-06 20:02:56 Error reading from database: Database corrupted

In addition, during syncing my wallet shows transactions with the wrong date. Transactions from 2013 show up as they were in 15/10/2017, which is definitely wrong (aka at 60% blockchain I seetransactions with 2017 datestamp). Re-indexing does not help this.
The drive is healthy, plenty of space and the error occurs regardless if I use Windows or Linux. (According to various scans, no bad sector, is present. The drive is ~6 monnths old, so statistically it should be the smallest "issue factor")
I have even went so far as to completely uninstall bitcoin core, create a fresh wallet and start downloading the blockchain. If I put back my own wallet, I get the error and the messed-up datestamps for transactions. If I let the fresh wallet, it also gives the error (as above).
is it possible a virus checker has removed some blocks or modified them?
Borisz
Sr. Member
****
Offline Offline

Activity: 476



View Profile
November 07, 2017, 09:51:10 PM
 #8

Ok, so after downloading the blockchain and re-indexing a few times, I'm still stuck. The outputs below are after that I have reinstalled bitcoin core.

Code:
2017-11-06 19:37:05 UpdateTip: new best=0000000000000000032894a63a03884fc3fd4b5c98de5e2cc7066ce764dc447e height=445828 version=0x20000000 log2_work=85.748268 tx=183429132 date='2016-12-30 15:58:45' progress=0.681485 cache=325.9MiB(2116235txo)
2017-11-06 19:37:05 LevelDB read failure: Corruption: block checksum mismatch
2017-11-06 19:37:05 Corruption: block checksum mismatch
2017-11-06 19:38:07 Error reading from database: Database corrupted

On a clean wallet:
Code:
2017-11-06 20:02:45 UpdateTip: new best=000000000000000002e901d8303d43e8bbd4d8f76a66cf2f2da064e8fbb31dbe height=448192 version=0x20000000 log2_work=85.819278 tx=187733247 date='2017-01-14 21:07:23' progress=0.697464 cache=238.2MiB(1397685txo)
2017-11-06 20:02:45 LevelDB read failure: Corruption: block checksum mismatch
2017-11-06 20:02:45 Corruption: block checksum mismatch
2017-11-06 20:02:56 Error reading from database: Database corrupted

In addition, during syncing my wallet shows transactions with the wrong date. Transactions from 2013 show up as they were in 15/10/2017, which is definitely wrong (aka at 60% blockchain I seetransactions with 2017 datestamp). Re-indexing does not help this.
The drive is healthy, plenty of space and the error occurs regardless if I use Windows or Linux. (According to various scans, no bad sector, is present. The drive is ~6 monnths old, so statistically it should be the smallest "issue factor")
I have even went so far as to completely uninstall bitcoin core, create a fresh wallet and start downloading the blockchain. If I put back my own wallet, I get the error and the messed-up datestamps for transactions. If I let the fresh wallet, it also gives the error (as above).
is it possible a virus checker has removed some blocks or modified them?

It shouldn't be the case. Exactly for this reason I tried running the wallet under Linux as well, without luck.
I might now try to run put the datatbase to a NAS instead of the local drive, but I don't see how the drive could be the issue.
Borisz
Sr. Member
****
Offline Offline

Activity: 476



View Profile
November 10, 2017, 05:49:58 PM
 #9

My wallet finally got in sync after a few rescan and reindex attempts. I still have transactions though from 2013 that show up with 2017 timestap....
Balance looks OK so I'll leave this here.
jackg
Hero Member
*****
Offline Offline

Activity: 826

1JRmjyGo3kpdXcQeAeTBmGtgkC1AomHKED


View Profile
November 10, 2017, 06:23:41 PM
 #10

My wallet finally got in sync after a few rescan and reindex attempts. I still have transactions though from 2013 that show up with 2017 timestap....
Balance looks OK so I'll leave this here.

That's probably just an error with your computer. If the balance is accurate then it should be fine. You can always check the transactions on block explorers like blockchain.info just to check if they ae still standard transactions.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!