Bitcoin Forum
June 22, 2018, 03:52:20 PM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Bitcoin core doesnt see existing blockchain  (Read 109 times)
Teeruk
Newbie
*
Offline Offline

Activity: 12
Merit: 2


View Profile
February 22, 2018, 05:42:22 AM
Merited by DannyHamilton (2)
 #1

Hello!

It was working fine.
Then I update it to 0.15.1 from 0.14.x and it doesnt recognise blockchain that is already on my harddrive(folder blocks 16x gb, not in a default folder, but on a separate disc).
It tries to download the whole blockchain again, but doesnt succeed as well(connecting to peers for hours with no visible progress).
I tried to use -datadir=<dir> and reinstall the client. Doesnt help even though it sees my wallet.dat(I can see my addresses).

What should I do to fix that?
TIA!)
1529682740
Hero Member
*
Offline Offline

Posts: 1529682740

View Profile Personal Message (Offline)

Ignore
1529682740
Reply with quote  #2

1529682740
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1529682740
Hero Member
*
Offline Offline

Posts: 1529682740

View Profile Personal Message (Offline)

Ignore
1529682740
Reply with quote  #2

1529682740
Report to moderator
1529682740
Hero Member
*
Offline Offline

Posts: 1529682740

View Profile Personal Message (Offline)

Ignore
1529682740
Reply with quote  #2

1529682740
Report to moderator
1529682740
Hero Member
*
Offline Offline

Posts: 1529682740

View Profile Personal Message (Offline)

Ignore
1529682740
Reply with quote  #2

1529682740
Report to moderator
achow101
Moderator
Legendary
*
Offline Offline

Activity: 1442
Merit: 1352


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
February 22, 2018, 06:42:34 AM
 #2

Post the contents of your debug.log file.

Teeruk
Newbie
*
Offline Offline

Activity: 12
Merit: 2


View Profile
February 22, 2018, 08:44:01 AM
 #3

Post the contents of your debug.log file.
It seems to get f...ed up on the previous version, even before update.

Sorry for the long post, dunno how to put under the spoiler.

Thats for first two after f..k up for 0.14.2

2018-02-22 01:24:36 Bitcoin version v0.14.2
2018-02-22 01:24:36 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-02-22 01:24:36 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2018-02-22 01:24:36 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core ещё не завершился безопасно..."
2018-02-22 01:24:37 Default data directory C:\Users\MyPC\AppData\Roaming\Bitcoin
2018-02-22 01:24:37 Using data directory F:\work\Bitcoin core
2018-02-22 01:24:37 Using config file F:\work\Bitcoin core\bitcoin.conf
2018-02-22 01:24:37 Using at most 125 automatic connections (2048 file descriptors available)
2018-02-22 01:24:37 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2018-02-22 01:24:37 Using 2 threads for script verification
2018-02-22 01:24:37 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-02-22 01:24:37 Using wallet wallet.dat
2018-02-22 01:24:37 scheduler thread start
2018-02-22 01:24:37 init message: Проверка бумажника...
2018-02-22 01:24:37 CDBEnv::Open: LogDir=F:\work\Bitcoin core\database ErrorFile=F:\work\Bitcoin core\db.log
2018-02-22 01:24:37 Bound to [::]:8333
2018-02-22 01:24:37 Bound to 0.0.0.0:8333
2018-02-22 01:24:37 Cache configuration:
2018-02-22 01:24:37 * Using 2.0MiB for block index database
2018-02-22 01:24:37 * Using 8.0MiB for chain state database
2018-02-22 01:24:37 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-02-22 01:24:37 init message: Загрузка индекса блоков...
2018-02-22 01:24:37 Opening LevelDB in F:\work\Bitcoin core\blocks\index
2018-02-22 01:24:37 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\001215.ldb: The request failed due to a fatal device hardware error.


2018-02-22 01:24:41 init message: Загрузка индекса блоков...
2018-02-22 01:24:41 Wiping LevelDB in F:\work\Bitcoin core\blocks\index
2018-02-22 01:24:41 Opening LevelDB in F:\work\Bitcoin core\blocks\index
2018-02-22 01:24:41 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.


2018-02-22 01:24:42 scheduler thread interrupt
2018-02-22 01:24:42 Shutdown: In progress...
2018-02-22 01:24:42 Shutdown: done
2018-02-22 01:24:42 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2018-02-22 01:24:48



2018-02-22 01:24:48 Bitcoin version v0.14.2
2018-02-22 01:24:48 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-02-22 01:24:48 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2018-02-22 01:24:48 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core ещё не завершился безопасно..."
2018-02-22 01:24:48 Default data directory C:\Users\MyPC\AppData\Roaming\Bitcoin
2018-02-22 01:24:48 Using data directory F:\work\Bitcoin core
2018-02-22 01:24:48 Using config file F:\work\Bitcoin core\bitcoin.conf
2018-02-22 01:24:48 Using at most 125 automatic connections (2048 file descriptors available)
2018-02-22 01:24:48 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2018-02-22 01:24:48 Using 2 threads for script verification
2018-02-22 01:24:48 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-02-22 01:24:48 Using wallet wallet.dat
2018-02-22 01:24:48 scheduler thread start
2018-02-22 01:24:48 init message: Проверка бумажника...
2018-02-22 01:24:48 CDBEnv::Open: LogDir=F:\work\Bitcoin core\database ErrorFile=F:\work\Bitcoin core\db.log
2018-02-22 01:24:48 Bound to [::]:8333
2018-02-22 01:24:48 Bound to 0.0.0.0:8333
2018-02-22 01:24:48 Cache configuration:
2018-02-22 01:24:48 * Using 2.0MiB for block index database
2018-02-22 01:24:48 * Using 8.0MiB for chain state database
2018-02-22 01:24:48 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-02-22 01:24:48 init message: Загрузка индекса блоков...
2018-02-22 01:24:48 Opening LevelDB in F:\work\Bitcoin core\blocks\index
2018-02-22 01:24:48 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.


2018-02-22 01:24:49 init message: Загрузка индекса блоков...
2018-02-22 01:24:49 Wiping LevelDB in F:\work\Bitcoin core\blocks\index
2018-02-22 01:24:49 Opening LevelDB in F:\work\Bitcoin core\blocks\index
2018-02-22 01:24:49 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.


2018-02-22 01:24:50 scheduler thread interrupt
2018-02-22 01:24:50 Shutdown: In progress...
2018-02-22 01:24:50 Shutdown: done
2018-02-22 03:10:54




And thats the last one for 0.15.1

2018-02-22 05:29:49 Bitcoin version v0.15.1
2018-02-22 05:29:49 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-02-22 05:29:49 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2018-02-22 05:29:49 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a
2018-02-22 05:29:49 Using the 'standard' SHA256 implementation
2018-02-22 05:29:49 Using RdRand as an additional entropy source
2018-02-22 05:29:50 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core ещё не завершился безопасно..."
2018-02-22 05:29:50 Default data directory C:\Users\MyPC\AppData\Roaming\Bitcoin
2018-02-22 05:29:50 Using data directory F:\work\Bitcoin core
2018-02-22 05:29:50 Using config file F:\work\Bitcoin core\bitcoin.conf
2018-02-22 05:29:50 Using at most 125 automatic connections (2048 file descriptors available)
2018-02-22 05:29:50 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-02-22 05:29:50 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-02-22 05:29:50 Using 2 threads for script verification
2018-02-22 05:29:50 init message: Verifying wallet(s)...
2018-02-22 05:29:50 scheduler thread start
2018-02-22 05:29:50 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-02-22 05:29:50 Using wallet wallet.dat
2018-02-22 05:29:50 CDBEnv::Open: LogDir=F:\work\Bitcoin core\database ErrorFile=F:\work\Bitcoin core\db.log
2018-02-22 05:29:50 Cache configuration:
2018-02-22 05:29:50 * Using 2.0MiB for block index database
2018-02-22 05:29:50 * Using 8.0MiB for chain state database
2018-02-22 05:29:50 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-02-22 05:29:50 init message: Загрузка индекса блоков...
2018-02-22 05:29:50 Opening LevelDB in F:\work\Bitcoin core\blocks\index
2018-02-22 05:29:50 Opened LevelDB successfully
2018-02-22 05:29:50 Using obfuscation key for F:\work\Bitcoin core\blocks\index: 0000000000000000
2018-02-22 05:29:50 LoadBlockIndexDB: last block file = 0
2018-02-22 05:29:50 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=6, size=1688, heights=0...1, time=2009-01-03...2009-01-09)
2018-02-22 05:29:50 Checking all blk files are present...
2018-02-22 05:29:50 LoadBlockIndexDB: transaction index disabled
2018-02-22 05:29:50 Opening LevelDB in F:\work\Bitcoin core\chainstate
2018-02-22 05:29:50 Opened LevelDB successfully
2018-02-22 05:29:50 Using obfuscation key for F:\work\Bitcoin core\chainstate: 7950d64377ab6d1e
2018-02-22 05:29:50 Loaded best chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03 18:15:05 progress=0.000000
2018-02-22 05:29:50 init message: Перемотка блоков...
2018-02-22 05:29:50 init message: Проверка блоков...
2018-02-22 05:29:50  block index             265ms
2018-02-22 05:29:50 init message: Загрузка бумажника...
2018-02-22 05:29:50 nFileVersion = 150100
2018-02-22 05:29:50 Keys: 0 plaintext, 209 encrypted, 209 w/ metadata, 209 total
2018-02-22 05:29:50  wallet                   16ms
2018-02-22 05:29:50 setKeyPool.size() = 99
2018-02-22 05:29:50 mapWallet.size() = 6
2018-02-22 05:29:50 mapAddressBook.size() = 10
2018-02-22 05:29:50 mapBlockIndex.size() = 20000
2018-02-22 05:29:50 nBestHeight = 0
2018-02-22 05:29:50 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2018-02-22 05:29:50 torcontrol thread start
2018-02-22 05:29:50 Bound to [::]:8333
2018-02-22 05:29:50 Bound to 0.0.0.0:8333
2018-02-22 05:29:50 init message: Loading P2P addresses...
2018-02-22 05:29:50 Loaded 63179 addresses from peers.dat  326ms
2018-02-22 05:29:50 init message: Загрузка банлиста...
2018-02-22 05:29:50 init message: Запускаем сетевые потоки...
2018-02-22 05:29:50 net thread start
2018-02-22 05:29:50 dnsseed thread start
2018-02-22 05:29:50 addcon thread start
2018-02-22 05:29:50 opencon thread start
2018-02-22 05:29:50 msghand thread start
2018-02-22 05:29:50 init message: Загрузка завершена
2018-02-22 05:29:50 GUI: Platform customization: "windows"
2018-02-22 05:29:50 GUI: PaymentServer::LoadRootCAs: Loaded  54  root certificates
2018-02-22 05:29:57 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510354, us=58.11.31.241:52940, peer=0
2018-02-22 05:29:58 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:29:58 ERROR: invalid header received
2018-02-22 05:29:58 ProcessMessages(headers, 162003 bytes) FAILED peer=0
2018-02-22 05:30:01 Loading addresses from DNS seeds (could take a while)
2018-02-22 05:30:03 117 addresses found from DNS seeds
2018-02-22 05:30:03 dnsseed thread exit
2018-02-22 05:30:31 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:52959, peer=1
2018-02-22 05:30:32 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:30:32 ERROR: invalid header received
2018-02-22 05:30:32 ProcessMessages(headers, 162003 bytes) FAILED peer=1
2018-02-22 05:30:38 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:52961, peer=2
2018-02-22 05:30:38 receive version message: /Satoshi:0.16.0/: version 70015, blocks=510354, us=58.11.31.241:52962, peer=3
2018-02-22 05:30:40 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:30:40 ERROR: invalid header received
2018-02-22 05:30:40 ProcessMessages(headers, 162003 bytes) FAILED peer=2
2018-02-22 05:30:41 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:30:41 ERROR: invalid header received
2018-02-22 05:30:41 ProcessMessages(headers, 162003 bytes) FAILED peer=3
2018-02-22 05:30:50 receive version message: /Satoshi:0.14.2/: version 70015, blocks=510354, us=58.11.31.241:52968, peer=5
2018-02-22 05:30:51 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510354, us=58.11.31.241:52969, peer=6
2018-02-22 05:30:52 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510354, us=35.160.112.82:8333, peer=7
2018-02-22 05:30:53 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:30:53 ERROR: invalid header received
2018-02-22 05:30:53 ProcessMessages(headers, 162003 bytes) FAILED peer=5
2018-02-22 05:30:54 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:30:54 ERROR: invalid header received
2018-02-22 05:30:54 ProcessMessages(headers, 162003 bytes) FAILED peer=6
2018-02-22 05:30:55 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:30:55 ERROR: invalid header received
2018-02-22 05:30:55 ProcessMessages(headers, 162003 bytes) FAILED peer=7
2018-02-22 05:30:59 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510354, us=54.169.12.231:8333, peer=9
2018-02-22 05:30:59 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:30:59 ERROR: invalid header received
2018-02-22 05:30:59 ProcessMessages(headers, 162003 bytes) FAILED peer=9
2018-02-22 05:31:05 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:52975, peer=10
2018-02-22 05:31:07 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:31:07 ERROR: invalid header received
2018-02-22 05:31:07 ProcessMessages(headers, 162003 bytes) FAILED peer=10
2018-02-22 05:31:11 receive version message: /Satoshi:0.13.2/: version 70015, blocks=510354, us=58.11.31.241:52979, peer=11
2018-02-22 05:31:28 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510354, us=58.11.31.241:52985, peer=12
2018-02-22 05:31:29 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:52986, peer=13
2018-02-22 05:31:30 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510354, us=54.254.177.190:8333, peer=14
2018-02-22 05:31:30 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:31:30 ERROR: invalid header received
2018-02-22 05:31:30 ProcessMessages(headers, 162003 bytes) FAILED peer=12
2018-02-22 05:31:32 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:31:32 ERROR: invalid header received
2018-02-22 05:31:32 ProcessMessages(headers, 162003 bytes) FAILED peer=13
2018-02-22 05:31:33 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:31:33 ERROR: invalid header received
2018-02-22 05:31:33 ProcessMessages(headers, 162003 bytes) FAILED peer=14
2018-02-22 05:31:58 receive version message: /Satoshi:0.14.2/: version 70015, blocks=510354, us=58.11.31.241:52994, peer=15
2018-02-22 05:32:00 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:32:00 ERROR: invalid header received
2018-02-22 05:32:00 ProcessMessages(headers, 162003 bytes) FAILED peer=15
2018-02-22 05:32:04 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:52996, peer=16
2018-02-22 05:32:06 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:32:06 ERROR: invalid header received
2018-02-22 05:32:06 ProcessMessages(headers, 162003 bytes) FAILED peer=16
2018-02-22 05:32:21 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:53000, peer=17
2018-02-22 05:32:22 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:32:22 ERROR: invalid header received
2018-02-22 05:32:22 ProcessMessages(headers, 162003 bytes) FAILED peer=17
2018-02-22 05:32:22 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:53001, peer=18
2018-02-22 05:32:23 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:53002, peer=19
2018-02-22 05:32:24 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:32:24 ERROR: invalid header received
2018-02-22 05:32:24 ProcessMessages(headers, 162003 bytes) FAILED peer=18
2018-02-22 05:32:25 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:32:25 ERROR: invalid header received
2018-02-22 05:32:25 ProcessMessages(headers, 162003 bytes) FAILED peer=19
2018-02-22 05:32:29 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:53004, peer=20
2018-02-22 05:32:31 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:32:31 ERROR: invalid header received
2018-02-22 05:32:31 ProcessMessages(headers, 162003 bytes) FAILED peer=20
2018-02-22 05:32:47 receive version message: /Satoshi:0.14.99/: version 70015, blocks=510354, us=58.11.31.241:53012, peer=21
2018-02-22 05:32:47 receive version message: /Satoshi:0.15.0/: version 70015, blocks=510354, us=58.11.31.241:53013, peer=22
2018-02-22 05:32:49 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:32:49 ERROR: invalid header received
2018-02-22 05:32:49 ProcessMessages(headers, 162003 bytes) FAILED peer=21
2018-02-22 05:32:50 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:32:50 ERROR: invalid header received
2018-02-22 05:32:50 ProcessMessages(headers, 162003 bytes) FAILED peer=22
2018-02-22 05:33:22 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2018-02-22 05:33:42 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=52.14.133.108:8333, peer=24
2018-02-22 05:33:43 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:33:43 ERROR: invalid header received
2018-02-22 05:33:43 ProcessMessages(headers, 162003 bytes) FAILED peer=24
2018-02-22 05:33:53 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=58.11.31.241:53033, peer=25
2018-02-22 05:33:55 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:33:55 ERROR: invalid header received
2018-02-22 05:33:55 ProcessMessages(headers, 162003 bytes) FAILED peer=25
2018-02-22 05:34:21 receive version message: /Satoshi:0.15.0/: version 70015, blocks=510355, us=58.11.31.241:53040, peer=26
2018-02-22 05:34:23 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53041, peer=27
2018-02-22 05:34:23 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:34:23 ERROR: invalid header received
2018-02-22 05:34:23 ProcessMessages(headers, 162003 bytes) FAILED peer=26
2018-02-22 05:34:29 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=88.99.172.114:8333, peer=28
2018-02-22 05:34:35 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:34:35 ERROR: invalid header received
2018-02-22 05:34:35 ProcessMessages(headers, 162003 bytes) FAILED peer=27
2018-02-22 05:34:35 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53045, peer=29
2018-02-22 05:34:36 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:34:36 ERROR: invalid header received
2018-02-22 05:34:36 ProcessMessages(headers, 162003 bytes) FAILED peer=28
2018-02-22 05:34:37 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:34:37 ERROR: invalid header received
2018-02-22 05:34:37 ProcessMessages(headers, 162003 bytes) FAILED peer=29
2018-02-22 05:35:09 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=104.199.160.111:8333, peer=30
2018-02-22 05:35:11 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:35:11 ERROR: invalid header received
2018-02-22 05:35:11 ProcessMessages(headers, 162003 bytes) FAILED peer=30
2018-02-22 05:35:21 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53062, peer=31
2018-02-22 05:35:22 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:35:22 ERROR: invalid header received
2018-02-22 05:35:22 ProcessMessages(headers, 162003 bytes) FAILED peer=31
2018-02-22 05:36:01 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53074, peer=33
2018-02-22 05:36:01 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53075, peer=34
2018-02-22 05:36:02 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:36:02 ERROR: invalid header received
2018-02-22 05:36:02 ProcessMessages(headers, 162003 bytes) FAILED peer=33
2018-02-22 05:36:02 receive version message: /Satoshi:0.15.1(bitcore)/: version 70015, blocks=510355, us=[::]:0, peer=35
2018-02-22 05:36:03 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=46.101.200.194:8333, peer=36
2018-02-22 05:36:03 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:36:03 ERROR: invalid header received
2018-02-22 05:36:03 ProcessMessages(headers, 162003 bytes) FAILED peer=34
2018-02-22 05:36:04 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:36:04 ERROR: invalid header received
2018-02-22 05:36:04 ProcessMessages(headers, 162003 bytes) FAILED peer=35
2018-02-22 05:36:06 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:36:06 ERROR: invalid header received
2018-02-22 05:36:06 ProcessMessages(headers, 162003 bytes) FAILED peer=36
2018-02-22 05:36:08 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510343, us=104.198.94.212:8333, peer=32
2018-02-22 05:36:15 receive version message: /Satoshi:0.16.0/: version 70015, blocks=510355, us=58.11.31.241:53082, peer=37
2018-02-22 05:36:16 receive version message: /Satoshi:0.13.1/: version 70014, blocks=510355, us=58.11.31.241:53083, peer=38
2018-02-22 05:36:38 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:36:38 ERROR: invalid header received
2018-02-22 05:36:38 ProcessMessages(headers, 162003 bytes) FAILED peer=32
2018-02-22 05:36:40 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:36:40 ERROR: invalid header received
2018-02-22 05:36:40 ProcessMessages(headers, 162003 bytes) FAILED peer=37
2018-02-22 05:36:42 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:36:42 ERROR: invalid header received
2018-02-22 05:36:42 ProcessMessages(headers, 162003 bytes) FAILED peer=38
2018-02-22 05:37:11 receive version message: /Satoshi:0.15.99/: version 70015, blocks=510355, us=58.11.31.241:53111, peer=39
2018-02-22 05:37:13 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:37:13 ERROR: invalid header received
2018-02-22 05:37:13 ProcessMessages(headers, 162003 bytes) FAILED peer=39
2018-02-22 05:37:18 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53137, peer=40
2018-02-22 05:37:21 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:37:21 ERROR: invalid header received
2018-02-22 05:37:21 ProcessMessages(headers, 162003 bytes) FAILED peer=40
2018-02-22 05:37:26 ProcessMessages(version, 106 bytes) FAILED peer=41
2018-02-22 05:38:21 receive version message: /Satoshi:0.16.0/: version 70015, blocks=510355, us=58.11.31.241:53187, peer=42
2018-02-22 05:38:24 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:38:24 ERROR: invalid header received
2018-02-22 05:38:24 ProcessMessages(headers, 162003 bytes) FAILED peer=42
2018-02-22 05:38:33 receive version message: /Satoshi:0.15.99/: version 70015, blocks=510355, us=58.11.31.241:53190, peer=43
2018-02-22 05:38:34 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:38:34 ERROR: invalid header received
2018-02-22 05:38:34 ProcessMessages(headers, 162003 bytes) FAILED peer=43
2018-02-22 05:38:44 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510355, us=52.77.235.168:8333, peer=44
2018-02-22 05:38:45 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:38:45 ERROR: invalid header received
2018-02-22 05:38:45 ProcessMessages(headers, 162003 bytes) FAILED peer=44
2018-02-22 05:38:45 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2018-02-22 05:39:19 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53201, peer=46
2018-02-22 05:39:25 receive version message: /Satoshi:0.15.1(NO2X)/: version 70015, blocks=510355, us=58.11.31.241:53203, peer=47
2018-02-22 05:39:28 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:39:28 ERROR: invalid header received
2018-02-22 05:39:28 ProcessMessages(headers, 162003 bytes) FAILED peer=46
2018-02-22 05:39:29 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:39:29 ERROR: invalid header received
2018-02-22 05:39:29 ProcessMessages(headers, 162003 bytes) FAILED peer=47
2018-02-22 05:39:54 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=88.99.190.205:8333, peer=48
2018-02-22 05:39:54 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2018-02-22 05:39:55 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:39:55 ERROR: invalid header received
2018-02-22 05:39:55 ProcessMessages(headers, 162003 bytes) FAILED peer=48
2018-02-22 05:39:55 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53213, peer=50
2018-02-22 05:39:56 receive version message: /Satoshi:0.15.1(UASF-SegWit-BIP148)/: version 70015, blocks=510355, us=58.11.31.241:53214, peer=51
2018-02-22 05:39:57 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:39:57 ERROR: invalid header received
2018-02-22 05:39:57 ProcessMessages(headers, 162003 bytes) FAILED peer=50
2018-02-22 05:39:58 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:39:58 ERROR: invalid header received
2018-02-22 05:39:58 ProcessMessages(headers, 162003 bytes) FAILED peer=51
2018-02-22 05:40:03 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53218, peer=53
2018-02-22 05:40:04 receive version message: /Satoshi:0.16.0/: version 70015, blocks=510355, us=58.11.31.241:53219, peer=54
2018-02-22 05:40:04 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510354, us=107.167.187.47:8333, peer=52
2018-02-22 05:40:04 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:40:04 ERROR: invalid header received
2018-02-22 05:40:04 ProcessMessages(headers, 162003 bytes) FAILED peer=53
2018-02-22 05:40:14 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:40:14 ERROR: invalid header received
2018-02-22 05:40:14 ProcessMessages(headers, 162003 bytes) FAILED peer=52
2018-02-22 05:40:16 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:40:16 ERROR: invalid header received
2018-02-22 05:40:16 ProcessMessages(headers, 162003 bytes) FAILED peer=54
2018-02-22 05:40:27 receive version message: /Satoshi:0.14.2/: version 70015, blocks=510355, us=58.11.31.241:53226, peer=56
2018-02-22 05:40:29 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:40:29 ERROR: invalid header received
2018-02-22 05:40:29 ProcessMessages(headers, 162003 bytes) FAILED peer=56
2018-02-22 05:40:33 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53229, peer=57
2018-02-22 05:40:35 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:40:35 ERROR: invalid header received
2018-02-22 05:40:35 ProcessMessages(headers, 162003 bytes) FAILED peer=57
2018-02-22 05:40:40 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53231, peer=58
2018-02-22 05:40:41 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=88.99.189.17:8333, peer=59
2018-02-22 05:40:42 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:40:42 ERROR: invalid header received
2018-02-22 05:40:42 ProcessMessages(headers, 162003 bytes) FAILED peer=58
2018-02-22 05:40:43 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:40:43 ERROR: invalid header received
2018-02-22 05:40:43 ProcessMessages(headers, 162003 bytes) FAILED peer=59
2018-02-22 05:40:47 receive version message: /Satoshi:0.15.99/: version 70015, blocks=510355, us=58.11.31.241:53234, peer=60
2018-02-22 05:40:48 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:40:48 ERROR: invalid header received
2018-02-22 05:40:48 ProcessMessages(headers, 162003 bytes) FAILED peer=60
2018-02-22 05:40:59 receive version message: /Satoshi:0.14.2/: version 70015, blocks=510355, us=58.11.31.241:53237, peer=61
2018-02-22 05:41:00 receive version message: /Satoshi:0.14.2/: version 70015, blocks=510355, us=58.11.31.241:53238, peer=62
2018-02-22 05:41:02 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:02 ERROR: invalid header received
2018-02-22 05:41:02 ProcessMessages(headers, 162003 bytes) FAILED peer=61
2018-02-22 05:41:15 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:15 ERROR: invalid header received
2018-02-22 05:41:15 ProcessMessages(headers, 162003 bytes) FAILED peer=62
2018-02-22 05:41:33 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53245, peer=63
2018-02-22 05:41:34 receive version message: /Satoshi:0.13.2/: version 70015, blocks=510355, us=58.11.31.241:53246, peer=64
2018-02-22 05:41:35 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:35 ERROR: invalid header received
2018-02-22 05:41:35 ProcessMessages(headers, 162003 bytes) FAILED peer=63
2018-02-22 05:41:38 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:38 ERROR: invalid header received
2018-02-22 05:41:38 ProcessMessages(headers, 162003 bytes) FAILED peer=64
2018-02-22 05:41:46 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53250, peer=65
2018-02-22 05:41:48 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53252, peer=67
2018-02-22 05:41:48 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:48 ERROR: invalid header received
2018-02-22 05:41:48 ProcessMessages(headers, 162003 bytes) FAILED peer=65
2018-02-22 05:41:48 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510355, us=58.11.31.241:53251, peer=66
2018-02-22 05:41:49 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:49 ERROR: invalid header received
2018-02-22 05:41:49 ProcessMessages(headers, 162003 bytes) FAILED peer=67
2018-02-22 05:41:53 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510355, us=54.169.34.94:8333, peer=68
2018-02-22 05:41:54 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:54 ERROR: invalid header received
2018-02-22 05:41:54 ProcessMessages(headers, 162003 bytes) FAILED peer=68
2018-02-22 05:41:54 receive version message: /Satoshi:0.15.1(NO2X)/: version 70015, blocks=510355, us=58.11.31.241:53255, peer=69
2018-02-22 05:41:55 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53256, peer=70
2018-02-22 05:41:56 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:56 ERROR: invalid header received
2018-02-22 05:41:56 ProcessMessages(headers, 162003 bytes) FAILED peer=69
2018-02-22 05:41:57 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:41:57 ERROR: invalid header received
2018-02-22 05:41:57 ProcessMessages(headers, 162003 bytes) FAILED peer=70
2018-02-22 05:42:01 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510355, us=54.254.177.190:8333, peer=71
2018-02-22 05:42:02 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:42:02 ERROR: invalid header received
2018-02-22 05:42:02 ProcessMessages(headers, 162003 bytes) FAILED peer=71
2018-02-22 05:42:13 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53261, peer=72
2018-02-22 05:42:16 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:42:16 ERROR: invalid header received
2018-02-22 05:42:16 ProcessMessages(headers, 162003 bytes) FAILED peer=72
2018-02-22 05:42:19 receive version message: /Satoshi:0.14.1/: version 70015, blocks=510355, us=58.11.31.241:53263, peer=73
2018-02-22 05:42:21 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:42:21 ERROR: invalid header received
2018-02-22 05:42:21 ProcessMessages(headers, 162003 bytes) FAILED peer=73
2018-02-22 05:42:30 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=35.185.146.52:8333, peer=74
2018-02-22 05:42:46 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:42:46 ERROR: invalid header received
2018-02-22 05:42:46 ProcessMessages(headers, 162003 bytes) FAILED peer=74
2018-02-22 05:43:05 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2018-02-22 05:43:06 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53275, peer=76
2018-02-22 05:43:07 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510355, us=54.179.161.154:8333, peer=78
2018-02-22 05:43:08 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53281, peer=79
2018-02-22 05:43:09 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:43:09 ERROR: invalid header received
2018-02-22 05:43:09 ProcessMessages(headers, 162003 bytes) FAILED peer=76
2018-02-22 05:43:09 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:43:09 ERROR: invalid header received
2018-02-22 05:43:09 ProcessMessages(headers, 162003 bytes) FAILED peer=78
2018-02-22 05:43:12 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:43:12 ERROR: invalid header received
2018-02-22 05:43:12 ProcessMessages(headers, 162003 bytes) FAILED peer=79
2018-02-22 05:43:20 receive version message: /Satoshi:0.15.1(UASF-SegWit-BIP148)/: version 70015, blocks=510355, us=58.11.31.241:53285, peer=80
2018-02-22 05:43:22 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:43:22 ERROR: invalid header received
2018-02-22 05:43:22 ProcessMessages(headers, 162003 bytes) FAILED peer=80
2018-02-22 05:44:04 receive version message: /Satoshi:0.14.99/: version 70015, blocks=510355, us=58.11.31.241:53328, peer=81
2018-02-22 05:44:06 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53329, peer=82
2018-02-22 05:44:09 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510355, us=52.221.216.10:8333, peer=84
2018-02-22 05:44:27 ProcessMessages(version, 111 bytes) FAILED peer=85
2018-02-22 05:44:34 receive version message: /Satoshi:0.14.1/: version 70015, blocks=510355, us=58.11.31.241:53346, peer=86
2018-02-22 05:44:43 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:44:43 ERROR: invalid header received
2018-02-22 05:44:43 ProcessMessages(headers, 162003 bytes) FAILED peer=81
2018-02-22 05:44:47 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:44:47 ERROR: invalid header received
2018-02-22 05:44:47 ProcessMessages(headers, 162003 bytes) FAILED peer=82
2018-02-22 05:44:53 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:44:53 ERROR: invalid header received
2018-02-22 05:44:53 ProcessMessages(headers, 162003 bytes) FAILED peer=84
2018-02-22 05:44:54 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:44:54 ERROR: invalid header received
2018-02-22 05:44:54 ProcessMessages(headers, 162003 bytes) FAILED peer=86
2018-02-22 05:45:02 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=510355, us=58.11.31.241:53370, peer=87
2018-02-22 05:45:03 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53371, peer=88
2018-02-22 05:45:05 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:45:05 ERROR: invalid header received
2018-02-22 05:45:05 ProcessMessages(headers, 162003 bytes) FAILED peer=87
2018-02-22 05:45:07 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:45:07 ERROR: invalid header received
2018-02-22 05:45:07 ProcessMessages(headers, 162003 bytes) FAILED peer=88
2018-02-22 05:45:09 receive version message: /Satoshi:0.15.0/: version 70015, blocks=510355, us=58.11.31.241:53374, peer=89
2018-02-22 05:45:10 receive version message: /Satoshi:0.14.2/: version 70015, blocks=510355, us=58.11.31.241:53377, peer=90
2018-02-22 05:45:11 receive version message: /Satoshi:0.13.2/: version 70015, blocks=510355, us=58.11.31.241:53378, peer=91
2018-02-22 05:45:11 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:45:11 ERROR: invalid header received
2018-02-22 05:45:11 ProcessMessages(headers, 162003 bytes) FAILED peer=89
2018-02-22 05:45:12 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:45:12 ERROR: invalid header received
2018-02-22 05:45:12 ProcessMessages(headers, 162003 bytes) FAILED peer=90
2018-02-22 05:45:13 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:45:13 ERROR: invalid header received
2018-02-22 05:45:13 ProcessMessages(headers, 162003 bytes) FAILED peer=91
2018-02-22 05:45:34 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53385, peer=92
2018-02-22 05:45:35 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:45:35 ERROR: invalid header received
2018-02-22 05:45:35 ProcessMessages(headers, 162003 bytes) FAILED peer=92
2018-02-22 05:45:40 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2018-02-22 05:45:46 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53392, peer=94
2018-02-22 05:45:49 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:45:49 ERROR: invalid header received
2018-02-22 05:45:49 ProcessMessages(headers, 162003 bytes) FAILED peer=94
2018-02-22 05:46:15 ProcessMessages(version, 102 bytes) FAILED peer=96
2018-02-22 05:46:16 receive version message: /Satoshi:0.15.0/: version 70015, blocks=510355, us=58.11.31.241:53404, peer=97
2018-02-22 05:46:17 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:46:17 ERROR: invalid header received
2018-02-22 05:46:17 ProcessMessages(headers, 162003 bytes) FAILED peer=97
2018-02-22 05:46:22 receive version message: /Satoshi:0.15.1/: version 70015, blocks=510355, us=58.11.31.241:53406, peer=98
2018-02-22 05:46:24 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:46:24 ERROR: invalid header received
2018-02-22 05:46:24 ProcessMessages(headers, 162003 bytes) FAILED peer=98
2018-02-22 05:46:44 tor: Thread interrupt
2018-02-22 05:46:44 opencon thread exit
2018-02-22 05:46:44 torcontrol thread exit
2018-02-22 05:46:44 addcon thread exit
2018-02-22 05:46:44 scheduler thread interrupt
2018-02-22 05:46:44 Shutdown: In progress...
2018-02-22 05:46:44 net thread exit
2018-02-22 05:46:44 msghand thread exit
2018-02-22 05:46:44 Dumped mempool: 0s to copy, 0.007019s to dump
2018-02-22 05:46:44 Shutdown: done
bob123
Sr. Member
****
Offline Offline

Activity: 602
Merit: 441



View Profile
February 22, 2018, 09:45:47 AM
 #4

Code:
2018-02-22 01:24:37 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\001215.ldb: The request failed due to a fatal device hardware error.
..
2018-02-22 01:24:41 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.
..
2018-02-22 01:24:42 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
...
2018-02-22 01:24:48 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.
...
2018-02-22 01:24:49 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.

It seems like your hard drive is somehow broken and this led to your data getting corrupted.
Did you already check whether your HD is working as intended?
You could try to read out the S.M.A.R.T values of your HD and see if everything works as it should. [1]

My guess would be that your HD got corrupted during v0.14.2 and core wasn't able to read those files after updating to 0.15.1

[1] Tools to read out S.M.A.R.T. values: https://en.wikipedia.org/wiki/Comparison_of_S.M.A.R.T._tools

Teeruk
Newbie
*
Offline Offline

Activity: 12
Merit: 2


View Profile
February 22, 2018, 03:08:06 PM
 #5

Code:
2018-02-22 01:24:37 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\001215.ldb: The request failed due to a fatal device hardware error.
..
2018-02-22 01:24:41 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.
..
2018-02-22 01:24:42 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
...
2018-02-22 01:24:48 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.
...
2018-02-22 01:24:49 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.

It seems like your hard drive is somehow broken and this led to your data getting corrupted.
Did you already check whether your HD is working as intended?
You could try to read out the S.M.A.R.T values of your HD and see if everything works as it should. [1]

My guess would be that your HD got corrupted during v0.14.2 and core wasn't able to read those files after updating to 0.15.1

[1] Tools to read out S.M.A.R.T. values: https://en.wikipedia.org/wiki/Comparison_of_S.M.A.R.T._tools

I doubt smth wrong with the drive... As far as I running plenty of virtual machines on the same drive.
It's a T1 with built-in encryption. Maybe something wrong with that...

But anyway, what should I do to fix it now?
I dont want to download 16x gb again lol
Teeruk
Newbie
*
Offline Offline

Activity: 12
Merit: 2


View Profile
February 22, 2018, 04:19:03 PM
 #6

Will "bitcoin-qt -reindex" help me?
Foxpup
Legendary
*
Offline Offline

Activity: 2212
Merit: 1060



View Profile
February 22, 2018, 04:20:09 PM
Merited by DannyHamilton (2), Jet Cash (1)
 #7

2018-02-22 05:29:58 ERROR: AcceptBlockHeader: block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 is marked invalid
2018-02-22 05:29:58 ERROR: invalid header received
2018-02-22 05:29:58 ProcessMessages(headers, 162003 bytes) FAILED peer=0
Your chainstate is corrupt; that block is in fact valid. File corruption in conjunction with IO errors suggests strongly that your hard drive is not quite as healthy as you believe. After copying the surviving data to a known-good drive, run with -reindex-chainstate to repair the database (this will take some time, so be patient).

Will pretend to do unverifiable things (while actually eating an enchilada-style burrito) for bitcoins: 1K6d1EviQKX3SVKjPYmJGyWBb1avbmCFM4
Jet Cash
Hero Member
*****
Online Online

Activity: 924
Merit: 928


Lets Talk Merit


View Profile WWW
February 22, 2018, 07:20:41 PM
 #8

Just a small tip to anyone copying their blockchain onto another drive. Make sure that you spell the directory correctly. I had a bit of a hiccup when I was setting up my Linux node. I'd spelt Bitcoin with a capital "B" instead of lower case ( or the other way round). I ought to know better after all the years I've been in computing. Smiley

Crypto Press Kit .com ++++ > What a great domain name for anyone advising bounty or ICO managers
Click here to buy it now for Bitcoin or US dollars
Teeruk
Newbie
*
Offline Offline

Activity: 12
Merit: 2


View Profile
February 22, 2018, 07:38:59 PM
 #9

After copying the surviving data to a known-good drive, run with -reindex-chainstate to repair the database (this will take some time, so be patient).
Done it. It starts download all the blocks from the very first one after reindexing still((
Teeruk
Newbie
*
Offline Offline

Activity: 12
Merit: 2


View Profile
February 23, 2018, 02:12:18 PM
 #10

Is there any way to make it recognise existing blocks?
Or I should download it all again?
HCP
Hero Member
*****
Offline Offline

Activity: 644
Merit: 814

<insert witty quote here>


View Profile
February 23, 2018, 06:31:01 PM
 #11

If it is downloading from the beginning, it is likely that your data has become too corrupted for it to trust what you've got. Unfortunately, it looks like you're going to need to redownload the entire blockchain again Sad

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!