Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Pages:
Author

Topic: I've been fight the core download for months - page 2. (Read 624 times)

fxstrike
member
Activity: 238
Merit: 40
First Payment Gateway using GoldBacked cryptocurre
Re: I've been fight the core download for months
March 27, 2018, 12:01:23 AM
#14
Quote from: 66tbird on March 26, 2018, 09:43:23 PM
I guess downloading the bootstrap is what I'll have to donate to. My bitcoin-qt hasn't moved in 24 hours. No peers.  When this hobby worked it was enjoyable. I'm months into my btc wallet recovery and I just want to move my btc into something that works,, like eth which I'm mining now. I don't see much future for an unusable blockchain with high fees too boot.

I've got 99% of it. I had it synced a few months ago with the transaction (with fees) but it never finished. I'm open for suggestions.

Why don't just export the private key and use electrum to spend it, here is good guide to Transfer wallet from Armory to Bitcoin-Qt

If you still want to try syncing your client you can try download the blockchain using torrent here for free, I am not affiliated with any of this service and please do proper virus scanning of the file once you downloaded it from this sites

I think you should try doing scandisk on your drive, maybe its can help eliminate all the file corruption problem.
achow101
staff
Activity: 3458
Merit: 6793
Just writing some code
Re: I've been fight the core download for months
March 26, 2018, 11:45:33 PM
#13
The error with peer banning is happening because a block that it read is probably corrupted and that block is marked as invalid. Then Bitcoin Core will try to continue to sync from its peers, but those peers are sending it the block that it had marked invalid so it will ban those peers. Eventually it will ban everyone it could get a connection to. To fix the peers banning problem, stop Bitcoin Core, delete the file named peers.dat, and start Bitcoin Core again.

I suspect that you have a hard drive failure. You have experienced what appears to be two cases of corrupt blocks on your hard drive. I suggest that you run hardware diagnostics to see if it finds anything wrong with your hard drive. You should stop running Bitcoin Core for now as it won't be doing anything if it can't sync the blockchain.
66tbird
jr. member
Activity: 62
Merit: 3
Re: I've been fight the core download for months
March 26, 2018, 09:43:23 PM
#12
I guess downloading the bootstrap is what I'll have to donate to. My bitcoin-qt hasn't moved in 24 hours. No peers.  When this hobby worked it was enjoyable. I'm months into my btc wallet recovery and I just want to move my btc into something that works,, like eth which I'm mining now. I don't see much future for an unusable blockchain with high fees too boot.

I've got 99% of it. I had it synced a few months ago with the transaction (with fees) but it never finished. I'm open for suggestions.
fxstrike
member
Activity: 238
Merit: 40
First Payment Gateway using GoldBacked cryptocurre
Re: I've been fight the core download for months
March 25, 2018, 09:30:34 PM
#11
Have you try downloading the blockchain and bootstrap the client with it, if you worry about any malicious code or anything that comes with the blockchain download just use it as trial system to make sure your client is able to sync using your current network and computer system.
66tbird
jr. member
Activity: 62
Merit: 3
Re: I've been fight the core download for months
March 25, 2018, 07:48:01 PM
#10
Locked up at 99% so I shut it down properly to work on it later. Next morning I clicked to wrong batch file and did a -reindex. Heart sank, I'm an idiot.  Day later it stops at 16% and there is a banned peer list I've never seen before. So WTF is that? Besides the obvious that is.

Here is the log when it happened. Which seems to go on forever so I'll not post the repetitive.

11-18 00:17:22' progress=0.165000 cache=934.7MiB(6447495txo)
2018-03-25 23:04:53 ERROR: ConnectBlock: Consensus::CheckTxInputs: d76dd47992c797483ab9adcaaab8304a658fcef9b302e215612aa056f7368fb8, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent (code 16)
2018-03-25 23:04:53 Misbehaving: 49.64.33.169:8333 peer=189 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:04:53 InvalidChainFound: invalid block=00000000000000000e36ed730e90bbf609e51487fce7df2878c638c5ecb98f9f  height=330488  log2_work=81.488336  date=2014-11-18 00:24:05
2018-03-25 23:04:53 InvalidChainFound:  current best=00000000000000000bc2b7ad9b516a3b15ac2e04ceaa79e69336f6f79ca03641  height=330487  log2_work=81.488263  date=2014-11-18 00:17:22
2018-03-25 23:04:53 ERROR: ConnectTip(): ConnectBlock 00000000000000000e36ed730e90bbf609e51487fce7df2878c638c5ecb98f9f failed
2018-03-25 23:04:53 InvalidChainFound: invalid block=00000000000000000e36ed730e90bbf609e51487fce7df2878c638c5ecb98f9f  height=330488  log2_work=81.488336  date=2014-11-18 00:24:05
2018-03-25 23:04:53 InvalidChainFound:  current best=00000000000000000bc2b7ad9b516a3b15ac2e04ceaa79e69336f6f79ca03641  height=330487  log2_work=81.488263  date=2014-11-18 00:17:22
2018-03-25 23:05:04 New outbound peer connected: version: 70015, blocks=515158, peer=197
2018-03-25 23:05:08 Pre-allocating up to position 0x5000000 in blk00197.dat
2018-03-25 23:05:39 Pre-allocating up to position 0x6000000 in blk00197.dat
2018-03-25 23:06:17 ERROR: AcceptBlockHeader: prev block invalid
2018-03-25 23:06:17 Misbehaving: 198.199.85.118:8333 peer=196 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:06:17 ERROR: invalid header received
2018-03-25 23:06:17 ERROR: AcceptBlockHeader: prev block invalid
2018-03-25 23:06:17 Misbehaving: 218.253.67.85:8333 peer=197 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:06:17 ERROR: invalid header received
2018-03-25 23:06:17 ERROR: AcceptBlockHeader: prev block invalid
2018-03-25 23:06:17 Misbehaving: 162.243.174.208:8333 peer=188 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:06:17 ERROR: invalid header received
2018-03-25 23:06:17 ERROR: AcceptBlockHeader: prev block invalid
2018-03-25 23:06:17 Misbehaving: 174.138.4.91:8333 peer=190 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:06:17 ERROR: invalid header received
2018-03-25 23:06:17 ERROR: AcceptBlockHeader: prev block invalid
2018-03-25 23:06:17 Misbehaving: 90.253.111.189:8333 peer=191 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:06:17 ERROR: invalid header received
2018-03-25 23:06:17 ERROR: AcceptBlockHeader: prev block invalid
2018-03-25 23:06:17 Misbehaving: 137.74.206.67:8333 peer=193 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:06:17 ERROR: invalid header received
2018-03-25 23:06:17 ERROR: AcceptBlockHeader: prev block invalid
2018-03-25 23:06:17 Misbehaving: 58.208.14.173:8333 peer=194 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:06:17 ERROR: invalid header received
2018-03-25 23:06:17 ERROR: AcceptBlockHeader: prev block invalid
2018-03-25 23:06:17 Misbehaving: 70.29.131.211:8333 peer=195 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-25 23:06:17 ERROR: invalid header received
2018-03-25 23:06:18 New outbound peer connected: version: 70015, blocks=515159, peer=198
2018-03-25 23:06:18 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:06:18 ERROR: invalid header received
2018-03-25 23:06:19 New outbound peer connected: version: 70015, blocks=515159, peer=199
2018-03-25 23:06:19 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:06:19 ERROR: invalid header received
2018-03-25 23:06:25 New outbound peer connected: version: 70015, blocks=515159, peer=200
2018-03-25 23:06:25 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:06:25 ERROR: invalid header received
2018-03-25 23:06:26 New outbound peer connected: version: 70015, blocks=515159, peer=201
2018-03-25 23:06:26 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:06:26 ERROR: invalid header received
2018-03-25 23:06:26 New outbound peer connected: version: 70015, blocks=515159, peer=202
2018-03-25 23:06:26 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:06:26 ERROR: invalid header received
2018-03-25 23:06:32 New outbound peer connected: version: 70015, blocks=515159, peer=203
2018-03-25 23:06:33 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:06:33 ERROR: invalid header received
2018-03-25 23:07:12 New outbound peer connected: version: 70015, blocks=515159, peer=204
2018-03-25 23:07:12 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:12 ERROR: invalid header received
2018-03-25 23:07:29 New outbound peer connected: version: 70015, blocks=515159, peer=205
2018-03-25 23:07:29 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:29 ERROR: invalid header received
2018-03-25 23:07:35 New outbound peer connected: version: 70015, blocks=515159, peer=206
2018-03-25 23:07:35 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:35 ERROR: invalid header received
2018-03-25 23:07:36 New outbound peer connected: version: 70015, blocks=515159, peer=207
2018-03-25 23:07:36 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:36 ERROR: invalid header received
2018-03-25 23:07:42 New outbound peer connected: version: 70015, blocks=515159, peer=208
2018-03-25 23:07:42 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:42 ERROR: invalid header received
2018-03-25 23:07:48 New outbound peer connected: version: 70015, blocks=515159, peer=209
2018-03-25 23:07:48 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:48 ERROR: invalid header received
2018-03-25 23:07:49 New outbound peer connected: version: 70015, blocks=515159, peer=210
2018-03-25 23:07:49 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:49 ERROR: invalid header received
2018-03-25 23:07:49 New outbound peer connected: version: 70015, blocks=515159, peer=211
2018-03-25 23:07:49 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:49 ERROR: invalid header received
2018-03-25 23:07:55 New outbound peer connected: version: 70015, blocks=515159, peer=212
2018-03-25 23:07:56 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:07:56 ERROR: invalid header received
2018-03-25 23:08:01 New outbound peer connected: version: 70015, blocks=515159, peer=213
2018-03-25 23:08:01 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:08:01 ERROR: invalid header received
2018-03-25 23:08:08 New outbound peer connected: version: 70015, blocks=515159, peer=214
2018-03-25 23:08:08 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:08:08 ERROR: invalid header received
2018-03-25 23:08:08 New outbound peer connected: version: 70015, blocks=515159, peer=215
2018-03-25 23:08:09 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:08:09 ERROR: invalid header received
2018-03-25 23:08:14 New outbound peer connected: version: 70015, blocks=515159, peer=216
2018-03-25 23:08:14 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid
2018-03-25 23:08:14 ERROR: invalid header received
2018-03-25 23:08:15 New outbound peer connected: version: 70014, blocks=515159, peer=217
2018-03-25 23:08:15 ERROR: AcceptBlockHeader: block 00000000000000000022c6c463b57b714dd887713148ef4c569926113fcd68b0 is marked invalid  
fxstrike
member
Activity: 238
Merit: 40
First Payment Gateway using GoldBacked cryptocurre
Re: I've been fight the core download for months
March 24, 2018, 12:46:13 PM
#9
Quote from: Jet Cash on March 23, 2018, 05:08:22 AM
Do you think it would be better to rename the bad block rather than delete it? I'm not sure how SSDs work, but in the past when using HDDs, I've found it better to rename the file to prevent a bad sector on the disk being reused,
He have BTC blockchain's blocks that is bad it is a file that is corrupted during syncing, its not the block sector of the disk [SSD or HDD] that is becoming bad.
fxstrike
member
Activity: 238
Merit: 40
First Payment Gateway using GoldBacked cryptocurre
Re: I've been fight the core download for months
March 24, 2018, 12:40:51 PM
#8
Why don't download the BTC blockchain, so that you have less time waiting for the client to sync and make sure everything will be synced correctly in lesser time rather than waiting for the client to sync for so long and then getting error message after 1 month waiting and trying, join this Bitcoin Blockchain Download [bootstrap.dat] thread and download the blockchain there
66tbird
jr. member
Activity: 62
Merit: 3
Re: I've been fight the core download for months
March 24, 2018, 09:20:15 AM
#7
So far the deleted that block advice has worked and progress is steady though be it slow. By tonight I'll be at the dreaded 99% hurdle.
bob123
legendary
Activity: 1624
Merit: 2481
Re: I've been fight the core download for months
March 24, 2018, 04:41:32 AM
#6
Quote from: Jet Cash on March 23, 2018, 05:08:22 AM
Do you think it would be better to rename the bad block rather than delete it? I'm not sure how SSDs work, but in the past when using HDDs, I've found it better to rename the file to prevent a bad sector on the disk being reused
.
SSD's have a micro controller which manages the access to the memory cells. Broken cells won't be used anymore for storage.
SSD's have more cells than actually 'needed' to achieve the promised capacity. Those start getting used when old cells die.
Renaming the block instead of deleting it would just use space (unnecessarily).


for reference: a small picture of a 'typical' SSD controller:

starmyc
full member
Activity: 198
Merit: 130
Some random software engineer
Re: I've been fight the core download for months
March 23, 2018, 05:18:28 AM
#5
Quote from: Jet Cash on March 23, 2018, 05:08:22 AM
Do you think it would be better to rename the bad block rather than delete it? I'm not sure how SSDs work, but in the past when using HDDs, I've found it better to rename the file to prevent a bad sector on the disk being reused,

Modern hard drives detect by themselves bad sectors and make sure they are no longer used.
In OP's case, it is bad blocks wrote on its hard disk, that would be caused by a crash or misuse. Deleting the block file could help the client to redownload, I guess.
IMO, I would delete everything and download the whole chain again.
Jet Cash
legendary
Activity: 2814
Merit: 2472
https://JetCash.com
Re: I've been fight the core download for months
March 23, 2018, 05:08:22 AM
#4
Do you think it would be better to rename the bad block rather than delete it? I'm not sure how SSDs work, but in the past when using HDDs, I've found it better to rename the file to prevent a bad sector on the disk being reused,
66tbird
jr. member
Activity: 62
Merit: 3
Re: I've been fight the core download for months
March 22, 2018, 08:55:15 AM
#3
Thank you.  I will do that.
achow101
staff
Activity: 3458
Merit: 6793
Just writing some code
Re: I've been fight the core download for months
March 21, 2018, 11:55:19 PM
#2
Your copy of the blockchain contains a corrupted block. You will need to delete the corrupted block and reindex the blockchain which will take several hours. To do this first stop Bitcoin Core. Then go to blocks folder in the Bitcoin data directory (for you that is C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks) and delete the files blk00589.dat and rev0589.dat and any blk*.dat and rev*.dat files that have higher numbers. Then start Bitcoin Core again. It will tell you that it needs to reindex the blockchain, click Yes and let it do that. Once it finishes, it should resume syncing the rest of the blockchain. Note that the reindex will appear as if it is syncing the blockchain; it is not.
66tbird
jr. member
Activity: 62
Merit: 3
Re: I've been fight the core download for months
March 21, 2018, 10:28:20 PM
#1
I've had it, I've researched this inability to finish downloading the bitcoin core for a long time. I've rescanned, reindexed, removed and clean installed, mem checked, read lots of posts on similar issues. I'm ready to toss in the towel and just eat the ..05 bitcoin loss. It's in an Armory wallet btw and I'm using Bitcoin-Qt for the download. It's an i7 machine with 32Gb ram and an SSD not overclocked I guess it's my turn to post the last of the log file.  Please share your insight. Huh  Cry I'm going to bed. Undecided

2018-03-22 02:58:47 Using config file C:\Users\john-asus\AppData\Roaming\Bitcoin\bitcoin.conf
2018-03-22 02:58:47 Using at most 125 automatic connections (2048 file descriptors available)
2018-03-22 02:58:47 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-03-22 02:58:47 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-03-22 02:58:47 Using 7 threads for script verification
2018-03-22 02:58:47 scheduler thread start
2018-03-22 02:58:47 Using wallet directory C:\Users\john-asus\AppData\Roaming\Bitcoin\wallets
2018-03-22 02:58:47 init message: Verifying wallet(s)...
2018-03-22 02:58:47 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-03-22 02:58:47 Using wallet wallet.dat
2018-03-22 02:58:47 CDBEnv::Open: LogDir=C:\Users\john-asus\AppData\Roaming\Bitcoin\wallets\database ErrorFile=C:\Users\john-asus\AppData\Roaming\Bitcoin\wallets\db.log
2018-03-22 02:58:47 Cache configuration:
2018-03-22 02:58:47 * Using 2.0MiB for block index database
2018-03-22 02:58:47 * Using 8.0MiB for chain state database
2018-03-22 02:58:47 * Using 1490.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-03-22 02:58:47 init message: Loading block index...
2018-03-22 02:58:47 Opening LevelDB in C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks\index
2018-03-22 02:58:47 Opened LevelDB successfully
2018-03-22 02:58:47 Using obfuscation key for C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2018-03-22 02:58:51 LoadBlockIndexDB: last block file = 589
2018-03-22 02:58:51 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=21, size=17145808, heights=423442...423630, time=2016-08-03...2016-08-04)
2018-03-22 02:58:51 Checking all blk files are present...
2018-03-22 02:58:52 LoadBlockIndexDB: transaction index disabled
2018-03-22 02:58:52 Opening LevelDB in C:\Users\john-asus\AppData\Roaming\Bitcoin\chainstate
2018-03-22 02:58:52 Opened LevelDB successfully
2018-03-22 02:58:52 Using obfuscation key for C:\Users\john-asus\AppData\Roaming\Bitcoin\chainstate: b0ed7a711fbc1fa8
2018-03-22 02:58:52 Loaded best chain: hashBestChain=000000000000000003dbb864f4735aaff312c75a37f255f1b40393a94eb71d01 height=423509 date=2016-08-03 17:14:51 progress=0.470231
2018-03-22 02:58:52 init message: Rewinding blocks...
2018-03-22 02:58:53 Corruption: block checksum mismatch
2018-03-22 02:58:53 *** System error while flushing: Database corrupted
2018-03-22 02:59:00 Shutdown requested. Exiting.
2018-03-22 02:59:00 Shutdown: In progress...
2018-03-22 02:59:00 scheduler thread interrupt
2018-03-22 02:59:00 Corruption: block checksum mismatch
2018-03-22 02:59:00 *** System error while flushing: Database corrupted
Pages:
Bitcoin Forum>Bitcoin>Bitcoin Technical Support
Jump to: