Bitcoin Forum
September 23, 2018, 03:38:54 AM *
News: ♦♦ New info! Bitcoin Core users absolutely must upgrade to previously-announced 0.16.3 [Torrent]. All Bitcoin users should temporarily trust confirmations slightly less. More info.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Setting up a Node - fatal internal error  (Read 157 times)
Zaphod69
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
November 21, 2017, 11:43:39 PM
 #1

Complete noob here wanting to run a full node but having errors.

Bitcoin Core: v0.151
Operating System: Windows 7 Ultimate 64bit
PC: Intel Core2Duo 2Ghz, 4Gb RAM, C:\ 14.3Gb free, D:\ 255Gb free, E:\ (DVDROM), F:\ 353Gb free (External USB - Bitcoin Core and data are installed on this drive), G:\ 809Gb free (External USB drive)
Problem: dialogue box "Error: A fatal error occurred, see debug.log for details"

This error came up one first run of the software when synching the blockchain. It has come up again after re-booting and restarting.

First run debug.log from line above the error:

2017-11-20 11:24:40 UpdateTip: new best=000000000000032d104f1fa188e72b67a1b770a11491206722ea31122295c2d8 height=223170 version=0x00000002 log2_work=69.461951 tx=13424315 date='2013-02-26 05:36:08' progress=0.049206 cache=542.7MiB(4142562txo)
2017-11-20 11:24:40 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=44, nPos=48392052)
2017-11-20 11:24:40 *** Failed to read block
2017-11-20 11:26:27 UPnP Port Mapping successful.
2017-11-20 11:46:28 UPnP Port Mapping successful.
2017-11-20 12:06:29 UPnP Port Mapping successful.
2017-11-20 12:26:30 UPnP Port Mapping successful.
2017-11-20 12:46:31 UPnP Port Mapping successful.
2017-11-20 13:06:32 UPnP Port Mapping successful.
2017-11-20 13:26:33 UPnP Port Mapping successful.
2017-11-20 13:46:34 UPnP Port Mapping successful.
2017-11-20 14:06:35 UPnP Port Mapping successful.
2017-11-20 14:26:36 UPnP Port Mapping successful.
2017-11-20 14:46:37 UPnP Port Mapping successful.
2017-11-20 15:06:38 UPnP Port Mapping successful.
2017-11-20 15:26:39 UPnP Port Mapping successful.
2017-11-20 15:46:40 UPnP Port Mapping successful.
2017-11-20 16:06:41 UPnP Port Mapping successful.
2017-11-20 16:26:42 UPnP Port Mapping successful.
2017-11-20 16:46:43 UPnP Port Mapping successful.
2017-11-20 17:06:44 UPnP Port Mapping successful.
2017-11-20 17:26:45 UPnP Port Mapping successful.
2017-11-20 17:46:46 UPnP Port Mapping successful.
2017-11-20 18:06:47 UPnP Port Mapping successful.
2017-11-20 18:26:48 UPnP Port Mapping successful.
2017-11-20 18:46:49 UPnP Port Mapping successful.
2017-11-20 19:06:50 UPnP Port Mapping successful.
2017-11-20 19:26:51 UPnP Port Mapping successful.
2017-11-20 19:46:52 UPnP Port Mapping successful.
2017-11-20 20:06:53 UPnP Port Mapping successful.
2017-11-20 20:26:54 UPnP Port Mapping successful.
2017-11-20 20:46:55 UPnP Port Mapping successful.
2017-11-20 21:06:56 UPnP Port Mapping successful.
2017-11-20 21:26:57 UPnP Port Mapping successful.
2017-11-20 21:46:58 UPnP Port Mapping successful.
2017-11-20 22:06:59 UPnP Port Mapping successful.
2017-11-20 22:27:00 UPnP Port Mapping successful.
2017-11-20 22:47:01 UPnP Port Mapping successful.
2017-11-20 23:07:02 UPnP Port Mapping successful.
2017-11-20 23:27:03 UPnP Port Mapping successful.
2017-11-20 23:31:14 socket sending timeout: 43596s
2017-11-20 23:31:14 socket sending timeout: 43596s
2017-11-20 23:31:14 socket sending timeout: 43596s
2017-11-20 23:31:14 socket sending timeout: 43604s
2017-11-20 23:31:14 socket sending timeout: 43596s
2017-11-20 23:31:14 socket sending timeout: 43596s
2017-11-20 23:31:14 socket sending timeout: 43596s
2017-11-20 23:31:14 socket sending timeout: 43596s
2017-11-20 23:31:14 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-11-20 23:31:14 receive version message: /bitnodes.earn.com:0.1/: version 70015, blocks=495232, us=210.10.185.21:8333, peer=44
2017-11-20 23:31:15 tor: Thread interrupt
2017-11-20 23:31:15 opencon thread exit
2017-11-20 23:31:15 addcon thread exit
2017-11-20 23:31:15 torcontrol thread exit
2017-11-20 23:31:15 net thread exit
2017-11-20 23:31:15 msghand thread exit
2017-11-20 23:31:15 scheduler thread interrupt
2017-11-20 23:31:15 Shutdown: In progress...
2017-11-20 23:31:15 UPNP_DeletePortMapping() returned: 0
2017-11-20 23:31:15 upnp thread interrupt
2017-11-20 23:31:15 Dumped mempool: 0.035002s to copy, 0.008s to dump
2017-11-20 23:32:24 Shutdown: done
2017-11-21 23:16:13


Debug.log from second run:

2017-11-21 23:16:13 Bitcoin version v0.15.1
2017-11-21 23:16:13 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-11-21 23:16:24 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2017-11-21 23:16:24 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a
2017-11-21 23:16:24 Using the 'standard' SHA256 implementation
2017-11-21 23:16:32 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-11-21 23:16:34 Default data directory C:\Users\Kodi\AppData\Roaming\Bitcoin
2017-11-21 23:16:34 Using data directory F:\Program Files (x86)\New folder\Bitcoin\data
2017-11-21 23:16:34 Using config file F:\Program Files (x86)\New folder\Bitcoin\data\bitcoin.conf
2017-11-21 23:16:34 Using at most 125 automatic connections (2048 file descriptors available)
2017-11-21 23:16:34 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2017-11-21 23:16:34 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2017-11-21 23:16:34 Using 2 threads for script verification
2017-11-21 23:16:34 scheduler thread start
2017-11-21 23:16:34 init message: Verifying wallet(s)...
2017-11-21 23:16:35 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-11-21 23:16:35 Using wallet wallet.dat
2017-11-21 23:16:35 CDBEnv::Open: LogDir=F:\Program Files (x86)\New folder\Bitcoin\data\database ErrorFile=F:\Program Files (x86)\New folder\Bitcoin\data\db.log
2017-11-21 23:16:43 Cache configuration:
2017-11-21 23:16:43 * Using 2.0MiB for block index database
2017-11-21 23:16:43 * Using 8.0MiB for chain state database
2017-11-21 23:16:43 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-11-21 23:16:43 init message: Loading block index...
2017-11-21 23:16:43 Opening LevelDB in F:\Program Files (x86)\New folder\Bitcoin\data\blocks\index
2017-11-21 23:16:43 Opened LevelDB successfully
2017-11-21 23:16:43 Using obfuscation key for F:\Program Files (x86)\New folder\Bitcoin\data\blocks\index: 0000000000000000
2017-11-21 23:17:26 LoadBlockIndexDB: last block file = 44
2017-11-21 23:17:26 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=418, size=69010985, heights=222610...223277, time=2013-02-22...2013-02-26)
2017-11-21 23:17:26 Checking all blk files are present...
2017-11-21 23:17:26 LoadBlockIndexDB: transaction index disabled
2017-11-21 23:17:26 Opening LevelDB in F:\Program Files (x86)\New folder\Bitcoin\data\chainstate
2017-11-21 23:17:31 Opened LevelDB successfully
2017-11-21 23:17:31 Using obfuscation key for F:\Program Files (x86)\New folder\Bitcoin\data\chainstate: 06911acb89e21a50
2017-11-21 23:17:32 Loaded best chain: hashBestChain=000000000000032d104f1fa188e72b67a1b770a11491206722ea31122295c2d8 height=223170 date=2013-02-26 05:36:08 progress=0.049134
2017-11-21 23:17:32 init message: Rewinding blocks...
2017-11-21 23:17:37 init message: Verifying blocks...
2017-11-21 23:17:37 Verifying last 6 blocks at level 3
2017-11-21 23:17:37 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-11-21 23:30:35 No coin database inconsistencies in last 7 blocks (3679 transactions)
2017-11-21 23:30:35  block index          832887ms
2017-11-21 23:30:36 init message: Loading wallet...
2017-11-21 23:30:40 nFileVersion = 150100
2017-11-21 23:30:40 Keys: 2002 plaintext, 0 encrypted, 2002 w/ metadata, 2002 total
2017-11-21 23:30:40  wallet                 4475ms
2017-11-21 23:30:40 setKeyPool.size() = 2000
2017-11-21 23:30:40 mapWallet.size() = 0
2017-11-21 23:30:40 mapAddressBook.size() = 1
2017-11-21 23:30:40 mapBlockIndex.size() = 495229
2017-11-21 23:30:40 nBestHeight = 223170
2017-11-21 23:30:40 torcontrol thread start
2017-11-21 23:30:40 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=44, nPos=48392052)
2017-11-21 23:30:41 upnp thread start
2017-11-21 23:30:41 Bound to [::]:8333
2017-11-21 23:30:41 Bound to 0.0.0.0:8333
2017-11-21 23:30:41 init message: Loading P2P addresses...
2017-11-21 23:30:41 *** Failed to read block
2017-11-21 23:30:42 Loaded 12738 addresses from peers.dat  743ms
2017-11-21 23:30:42 init message: Loading banlist...
2017-11-21 23:30:42 init message: Starting network threads...
2017-11-21 23:30:42 net thread start
2017-11-21 23:30:42 dnsseed thread start
2017-11-21 23:30:42 addcon thread start
2017-11-21 23:30:42 opencon thread start
2017-11-21 23:30:42 msghand thread start
2017-11-21 23:30:42 init message: Done loading
2017-11-21 23:30:44 UPnP: ExternalIPAddress = 210.10.185.21
2017-11-21 23:30:44 AddLocal(210.10.185.21:8333,3)
2017-11-21 23:30:44 UPnP Port Mapping successful.
2017-11-21 23:30:53 Loading addresses from DNS seeds (could take a while)
2017-11-21 23:30:55 142 addresses found from DNS seeds
2017-11-21 23:30:55 dnsseed thread exit
2017-11-21 23:38:44 Failed to connect best blockImported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2017-11-21 23:38:44 tor: Thread interrupt
2017-11-21 23:38:44 opencon thread exit
2017-11-21 23:38:44 torcontrol thread exit
2017-11-21 23:38:44 addcon thread exit
2017-11-21 23:38:44 msghand thread exit
2017-11-21 23:38:44 scheduler thread interrupt
2017-11-21 23:38:44 Shutdown: In progress...
2017-11-21 23:38:44 net thread exit
2017-11-21 23:38:45 UPNP_DeletePortMapping() returned: 0
2017-11-21 23:38:45 upnp thread interrupt
2017-11-21 23:38:45 Corruption: block checksum mismatch
2017-11-21 23:38:45 *** System error while flushing: Database corrupted
2017-11-21 23:38:48 Corruption: block checksum mismatch
2017-11-21 23:38:48 *** System error while flushing: Database corrupted
2017-11-21 23:38:52 Shutdown: done

Any suggestions?

Thanks in advance Smiley
1537673934
Hero Member
*
Offline Offline

Posts: 1537673934

View Profile Personal Message (Offline)

Ignore
1537673934
Reply with quote  #2

1537673934
Report to moderator
1537673934
Hero Member
*
Offline Offline

Posts: 1537673934

View Profile Personal Message (Offline)

Ignore
1537673934
Reply with quote  #2

1537673934
Report to moderator
1537673934
Hero Member
*
Offline Offline

Posts: 1537673934

View Profile Personal Message (Offline)

Ignore
1537673934
Reply with quote  #2

1537673934
Report to moderator
Make a difference with your Ether.
Donate Ether for the greater good.
SPRING.WETRUST.IO
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
HCP
Hero Member
*****
Offline Offline

Activity: 728
Merit: 923

<insert witty quote here>


View Profile
November 22, 2017, 12:41:56 AM
 #2

Quote
2017-11-20 11:24:40 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=44, nPos=48392052)
2017-11-20 11:24:40 *** Failed to read block
...
2017-11-21 23:30:40 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=44, nPos=48392052)
Seems the Bitcoin Core is having trouble reading a particular block from your drive... possibly a corrupted database file, or your disk might be faulty.

Delete the blocks folder from here: F:\Program Files (x86)\New folder\Bitcoin\data

And try starting Bitcoin Core again... if you get the same issue occurring, it is most likely going to be a hardware fault.

Zaphod69
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
November 22, 2017, 01:44:29 AM
 #3

Thank you. I've deleted the data as per suggestion and restarted but the error happens again - much quicker this time.

I'm currently running chkdsk on the external USB drives but suspect you're correct. If it's a hardware fault I'll get it sorted asap as I want a node up and running.

Cheers Smiley
Zaphod69
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
November 22, 2017, 08:18:51 AM
 #4

USB drive has bad blocks. Will replace the drives.

Cheers
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!