Create or edit the existing file named bitcoin.conf
Add this line in that file:
checklevel=2
Topic: All Bitcoind / Bitcoin-qt nodes failing to come up. Workaround inside! (Read 17468 times)
September 22, 2015, 04:41:36 PM
September 22, 2015, 02:59:20 AM
i dont have that file inside the bitcoin folder
That's okay, you can just create it and add the line gmaxwell mentioned.
https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File
it worked thank you so much!! i had such a headache trying to figure out why my client keep crashing.
forgive me for my ignorance but how do i "just create it and add the line gmaxwell mentioned"
thank you in advance
June 11, 2015, 04:52:55 PM
Faced same problem in latest core ver 0.10.2
Solved by Setting Right Time and date.
Solved by Setting Right Time and date.
June 05, 2014, 03:46:50 AM
Sorry but i've same problem with 0.8.6 daemon (on centos).
I've tried to run "./bitcoind -checklevel=2" but problem still remains
How can i fix it?
I've already try with "./bitcoind -checklevel=1" and deamon start but block chain not update (still remain on "300712"
)
I've tried to run "./bitcoind -checklevel=2" but problem still remains
How can i fix it?
I've already try with "./bitcoind -checklevel=1" and deamon start but block chain not update (still remain on "300712"
) January 21, 2014, 09:07:41 AM
I ran the wallet again this time with -debug option and checked the debug.log
2014-01-21 13:01:14 ERROR: bool CBlock::ReadFromDisk(const CDiskBlockPos&)() : deserialize or I/O error
2014-01-21 13:01:14 ERROR: VerifyDB() : *** block.ReadFromDisk failed at 281326, hash=00000000000000012149f5c1268c481778811d7e83ce7a496bc478bfc31cd3aa
2014-01-21 13:01:21 Shutdown : In progress...
Is there anything I can do to circumvent this?
Thanks
2014-01-21 13:01:14 ERROR: bool CBlock::ReadFromDisk(const CDiskBlockPos&)() : deserialize or I/O error
2014-01-21 13:01:14 ERROR: VerifyDB() : *** block.ReadFromDisk failed at 281326, hash=00000000000000012149f5c1268c481778811d7e83ce7a496bc478bfc31cd3aa
2014-01-21 13:01:21 Shutdown : In progress...
Is there anything I can do to circumvent this?
Thanks
January 21, 2014, 08:36:44 AM
I would like to report that this problem occurs to me on the 0.8.6 client.
I have used the checklevel param to no avail and reindex my client twice (2 long days). Short of redownloading 17gb worth of block chain, I don't know what else to do.
Any ray of light in this pitch dark cave will be most welcome.
This is my bitcoin.conf
rpcuser=rpc
rpcpassword=xxxx
server=1
daemon=1
txindex=1
I have used the checklevel param to no avail and reindex my client twice (2 long days). Short of redownloading 17gb worth of block chain, I don't know what else to do.
Any ray of light in this pitch dark cave will be most welcome.
This is my bitcoin.conf
rpcuser=rpc
rpcpassword=xxxx
server=1
daemon=1
txindex=1
September 15, 2013, 07:13:00 AM
Okay. I'll set it to 7 then. 7 is lucky. hehe. Or 4. I won 4th place in an online poker tourney just now.
Quote
System: Dabs finishes tournament in place #4 and wins 2 chips
September 15, 2013, 06:11:12 AM
I remember now, I set my checkblocks to 1 I think. Maybe I should bump it to 2 or 3. I don't think I need 6, in the same way that I can probably accept most transactions with only 1 confirmation.
I will eat my hat if you can notice the difference in speed. You really should have it turned up a bit so that the data checked will at least cross several erase blocks. September 15, 2013, 05:35:42 AM
What's the harm in a lower checklevel? I tried lower checklevels because I don't keep my QT running all the time. And it grabs the current blockchain from the network anyway and verifies it. It makes QT start up much faster too.
It means you are more likely to suffer from undetected corruption that could potentially be somewhat harmful to your peers. if you're trying to reduce your startup time, setting checkblocks to 6 would be a much better idea than reducing the checklevel.I remember now, I set my checkblocks to 1 I think. Maybe I should bump it to 2 or 3. I don't think I need 6, in the same way that I can probably accept most transactions with only 1 confirmation.
September 15, 2013, 05:13:10 AM
What's the harm in a lower checklevel? I tried lower checklevels because I don't keep my QT running all the time. And it grabs the current blockchain from the network anyway and verifies it. It makes QT start up much faster too.
It means you are more likely to suffer from undetected corruption that could potentially be somewhat harmful to your peers. if you're trying to reduce your startup time, setting checkblocks to 6 would be a much better idea than reducing the checklevel. September 15, 2013, 05:08:18 AM
What's the harm in a lower checklevel? I tried lower checklevels because I don't keep my QT running all the time. And it grabs the current blockchain from the network anyway and verifies it. It makes QT start up much faster too.
September 15, 2013, 04:58:06 AM
I had to delete my block chain after installing 8.5 on mac
September 14, 2013, 11:07:06 PM
Mine is not asking to rebuild. Mine is just simply frozen and will not go passed the 23 behind. It says that its synchronizing with network, but its not doing anything.
Try just leaving it alone, sometimes it takes another block to trigger progress. If its not throwing any warnings at you it should continue.Shouldn't it only need to rebuild it once though? What do you suggest? Just delete the program and reinstall?
Correct, assuming you let it go all the way through and then shut it down cleanly. Is it failing at every start for you even after letting it finish? 
September 14, 2013, 10:23:58 PM
I upgraded to 0.8.5 and tried to -checklevel=2 method. It's still asking to rebuild.
If your database is actually corrupted then thats an unrelated issue. Database corruption can happen for many reasons unrelated to this.Shouldn't it only need to rebuild it once though? What do you suggest? Just delete the program and reinstall?
September 14, 2013, 09:40:06 PM
I upgraded to 0.8.5 and tried to -checklevel=2 method. It's still asking to rebuild.
Mine is not asking to rebuild. Mine is just simply frozen and will not go passed the 23 behind. It says that its synchronizing with network, but its not doing anything.
I had 0.8.1 this morning when I realized it was beginning to reload the whole block chain again. I got scared because I thought some virus screwed up my computer and I stopped the syncing. Then I saw someone suggested that to up grade to 0.8.5. This was a mistake because now nothing is happening and its frozen at 23 weeks behind.
I have done the -checklevel=2 in the conf file. It did nothing. Then I put it in the properties of the start up ... still nothing.
So, my question is ... of course, what do I do? delete everything except the wallet.dat file and reinstall?
September 14, 2013, 08:06:22 PM
I upgraded to 0.8.5 and tried to -checklevel=2 method. It's still asking to rebuild.
If your database is actually corrupted then thats an unrelated issue. Database corruption can happen for many reasons unrelated to this. September 14, 2013, 09:03:34 AM
I upgraded to 0.8.5 and tried to -checklevel=2 method. It's still asking to rebuild.
September 13, 2013, 11:55:18 PM
Just got this message with Qt: "Corrupted Blockchain Detected do you want to rebuild". Advice please. TIA
Click "Abort" and upgrade to Bitcoin-Qt 0.8.5 before restarting the app. That sorted the problem for me.
Thanks for the reply and I should have read this thread before posting.
One more question: When this first occurred, I selected the option to begin re-indexing. Then decided I'd better research this matter before continuing and aborted the re-index at about 67 weeks remaining. I have now downloaded and installed 0.8.5. When I run the new version it is continuing the re-indexing from the abort point. Any problem, risk with allowing this to continue? Thank you, I really appreciate your help.
I didn't go this route myself, but it sounds fine. It'll just take a good long while until it completes, so the "Abort" option would have been faster. Anyhow, one ought to always keep a backup copy of the wallet.dat file somewhere else, and with that in hand there's not much reason to worry; in the worst case you can always start over.
Thanks again for the excellent info.
Best
September 13, 2013, 10:58:54 PM
Just got this message with Qt: "Corrupted Blockchain Detected do you want to rebuild". Advice please. TIA
Click "Abort" and upgrade to Bitcoin-Qt 0.8.5 before restarting the app. That sorted the problem for me.
Thanks for the reply and I should have read this thread before posting.
One more question: When this first occurred, I selected the option to begin re-indexing. Then decided I'd better research this matter before continuing and aborted the re-index at about 67 weeks remaining. I have now downloaded and installed 0.8.5. When I run the new version it is continuing the re-indexing from the abort point. Any problem, risk with allowing this to continue? Thank you, I really appreciate your help.
I didn't go this route myself, but it sounds fine. It'll just take a good long while until it completes, so the "Abort" option would have been faster. Anyhow, one ought to always keep a backup copy of the wallet.dat file somewhere else, and with that in hand there's not much reason to worry; in the worst case you can always start over.
September 13, 2013, 10:54:14 PM
Just got this message with Qt: "Corrupted Blockchain Detected do you want to rebuild". Advice please. TIA
Click "Abort" and upgrade to Bitcoin-Qt 0.8.5 before restarting the app. That sorted the problem for me.
Thanks for the reply and I should have read this thread before posting.
One more question: When this first occurred, I selected the option to begin re-indexing. Then decided I'd better research this matter before continuing and aborted the re-index at about 67 weeks remaining. I have now downloaded and installed 0.8.5. When I run the new version it is continuing the re-indexing from the abort point. Any problem, risk with allowing this to continue? Thank you, I really appreciate your help.
Jump to: