my btc blockchain stucks at "~25117 blocks remaining"

[bitcool]

again    delete the index, retry...

Makes me like Litecoin even more. Light, fast, full of libidos.

[1714785518]

1714785518

[1714785518]

1714785518

[K1773R]

again    delete the index, retry...

Makes me like Litecoin even more. Light, fast, full of libidos.

delete ur peers.

[bitcool]

again    delete the index, retry...

Makes me like Litecoin even more. Light, fast, full of libidos.

delete ur peers.

should restart bitcoin-qt refresh peers?

[K1773R]

again    delete the index, retry...

Makes me like Litecoin even more. Light, fast, full of libidos.

delete ur peers.

should restart bitcoin-qt refresh peers?

no, peers are being saved in ~/.bitcoin/peers.dat

[bitcool]

Well, deleting peers.dat does help.... for a while. then it started slowing again.

now it's 18,550 blocks remaining.... it's painful to watch it receiving one block at a time...

am I the only one whining about this?

[DannyHamilton]

am I the only one whining about this?

No.  But many people that become frustrated with the blockchain synchronization eventually switch to a "lightweight" client such as Electrum or Multibit.  Others just opt for the web hosted wallet solution provided by https://blockchain.info/wallet

[bitcool]

am I the only one whining about this?

No.  But many people that become frustrated with the blockchain synchronization eventually switch to a "lightweight" client such as Electrum or Multibit.  Others just opt for the web hosted wallet solution provided by https://blockchain.info/wallet

nice to know. ty.

[bitcoinBull]

am I the only one whining about this?

No.  But many people that become frustrated with the blockchain synchronization eventually switch to a "lightweight" client such as Electrum or Multibit.  Others just opt for the web hosted wallet solution provided by https://blockchain.info/wallet

blockchain.info is unconnected to the bitcoin network right now (down, basically). I don't use it a lot, but such problems as now are not uncommon for me. Which sucks, because I like blockchain.info a lot.

[zvs]

Well, deleting peers.dat does help.... for a while. then it started slowing again.

now it's 18,550 blocks remaining.... it's painful to watch it receiving one block at a time...

am I the only one whining about this?

if it's just receiving one block at a time at regular intervals then it's probably just your system is slow?

fastest way to get blockchain all finished is to make a 7 gig or so ramdrive then connect to just 1 peer

[Rygon]

Question: How do you connect to just one peer? I'm having the same issue, and I get the warning about the wallet version being incorrect. I think that means I'm connecting to a peer that has an out-of-date version, so it's messing me up with downloading the blockchain?

[bitcool]

Well, deleting peers.dat does help.... for a while. then it started slowing again.

now it's 18,550 blocks remaining.... it's painful to watch it receiving one block at a time...

am I the only one whining about this?

if it's just receiving one block at a time at regular intervals then it's probably just your system is slow?

fastest way to get blockchain all finished is to make a 7 gig or so ramdrive then connect to just 1 peer

watching it "receiving one block at a time" is actually the best case scenario (rarely it jumps a few blocks at a time),  most of the time it just sits there doing nothing, so no, I am pretty sure cpu or ram is not the bottleneck.

[bitcool]

Question: How do you connect to just one peer?

I read somewhere you can do "addnode" in bitcoind command to specify a peer, but not sure if this can be done with bitcoin-qt.

[DannyHamilton]

. . . most of the time it just sits there doing nothing, so no, I am pretty sure cpu or ram is not the bottleneck.

It most likely isn't "doing nothing".  It is probably validating all the transactions in the block that it just received, which involves tracing back all the previous transaction hashes in the blockchain.  This is a lot of disk access and processing.

[bitcool]

. . . most of the time it just sits there doing nothing, so no, I am pretty sure cpu or ram is not the bottleneck.

It most likely isn't "doing nothing".  It is probably validating all the transactions in the block that it just received, which involves tracing back all the previous transaction hashes in the blockchain.  This is a lot of disk access and processing.

nah, the cpu usage seems to be too low.

[bitcool]

Finally the btc blockchain is in sync, it took a grand total of 3 days 6 hours to complete, with 600MB repeated.

I must be living on the remote edge of the Internet 

[Rygon]

I'm about ready to give up on bitcoin-qt. In the past few days I've tried everything from deleting peers, deleting the blockchain files, completely uninstalling and reinstalling, and connecting only to one "super node" in order to download faster and hopefully get non-corrupted data. Yet I've had it get stuck at certain blocks, freeze 12.04 Ubuntu to the point it forced a hard restart, corrupted block index file, and even a corrupted wallet file (Glad I kept backups from several months prior). I don't know why the big problem now, I'd been running the bitcoin-qt client for almost a year now with no issues. I would like to run a node for the greater good of the network, and I've got the bandwidth to do it, but this is ridiculous. Time to switch to blockchain.info wallet or Electrum.

[K1773R]

Finally the btc blockchain is in sync, it took a grand total of 3 days 6 hours to complete, with 600MB repeated.

I must be living on the remote edge of the Internet 

just winblows + NTFS + slow HD

[zvs]

I'm about ready to give up on bitcoin-qt. In the past few days I've tried everything from deleting peers, deleting the blockchain files, completely uninstalling and reinstalling, and connecting only to one "super node" in order to download faster and hopefully get non-corrupted data. Yet I've had it get stuck at certain blocks, freeze 12.04 Ubuntu to the point it forced a hard restart, corrupted block index file, and even a corrupted wallet file (Glad I kept backups from several months prior). I don't know why the big problem now, I'd been running the bitcoin-qt client for almost a year now with no issues. I would like to run a node for the greater good of the network, and I've got the bandwidth to do it, but this is ridiculous. Time to switch to blockchain.info wallet or Electrum.

i always DL from the same node.. but on this node I have the buffers set so high that it also tends to flood people off.  i'm not sure if that's considered misbehavior or not, but it may ban the node.  it gets the socket receive flood detected message