All Bitcoind / Bitcoin-qt nodes failing to come up. Workaround inside!

[Beans]

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?

[1714945928]

1714945928

[1714945928]

1714945928

[1714945928]

1714945928

[1714945928]

1714945928

[gmaxwell]

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?

[doof]

I had to delete my block chain after installing 8.5 on mac

[Dabs]

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.

[gmaxwell]

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.

[Dabs]

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.

[gmaxwell]

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.

[Dabs]

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.

System: Dabs finishes tournament in place #4 and wins 2 chips

[lonsharim]

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

[lonsharim]

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

[TheBomber999]

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" )

[PrivacyBTC]

Faced same problem in latest core ver 0.10.2

Solved by Setting Right Time and date.

[tomsw6]

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

[goodbc]

Create or edit the existing file named bitcoin.conf

Add this line in that file:

checklevel=2