Show Posts
|
Pages: « 1 [2] 3 4 5 »
|
well all i can think of is that i keep BTC core on an external fast ssd, i will check that one for corruption, etc once finished
thanks again
|
|
|
more connections now - 15 and i see the 4 little arrows filled... in log i have now:
2021-04-06T10:46:15Z UpdateTip: new best=0000000000000000000b818d87315f69398aa6ba886d869f8c403a41f509e7f7 height=676881 version=0x20000000 log2_work=92.771642 tx=629219354 date='2021-03-29T18:50:42Z' progress=0.996321 cache=19.4MiB(144694txo) 2021-04-06T10:46:17Z New outbound peer connected: version: 70015, blocks=677998, peer=789 (full-relay) 2021-04-06T10:46:18Z New outbound peer connected: version: 70015, blocks=677998, peer=791 (full-relay) 2021-04-06T10:46:30Z New outbound peer connected: version: 70015, blocks=677998, peer=794 (full-relay) 2021-04-06T10:47:09Z New outbound peer connected: version: 70015, blocks=677998, peer=800 (full-relay) 2021-04-06T10:47:11Z New outbound peer connected: version: 70015, blocks=677998, peer=801 (full-relay) 2021-04-06T10:47:38Z New outbound peer connected: version: 70015, blocks=677998, peer=805 (full-relay) 2021-04-06T10:47:45Z New outbound peer connected: version: 70015, blocks=677998, peer=806 (full-relay) 2021-04-06T10:47:45Z New outbound peer connected: version: 70016, blocks=677998, peer=807 (full-relay) 2021-04-06T10:47:47Z New outbound peer connected: version: 70015, blocks=677998, peer=808 (full-relay) 2021-04-06T10:47:47Z New outbound peer connected: version: 70016, blocks=677998, peer=809 (full-relay)
no more notes about the block being invalid, let's give it some time. thanks for now....
YEEEEEEEEEEE it picked up blocks now!!! CPU is flying again thank youuuuuuuu
|
|
|
Go to Window>Console and type this: reconsiderblock 0000000000000000000b818d87315f69398aa6ba886d869f8c403a41f509e7f7
If it doesn't solve the problem, then your database is corrupted and you need to reindex. It can happen due to hardware failures; would be good if you could test your RAM for any inconsistencies. argh ((( everything is perfect here and last sync was without errors, so that's odd. something similar happened other times when say i unplugged the hard disk without disconnecting or pulling the cable by mistake etc. this time not. everything was always done proper.
|
|
|
thanks, this is what he spit back to me:
12:46:15  null
is that the intended output?
best, Gab
|
|
|
hi there guys,
I just launched Core earlier this morning - usually things are very fast on my SSD but for some reason it's stuck, connections with the little 4 dots come and go and it's still stuck on "Unknown, syncing headers 676880 99.8%"
I didn't have any crashes or unclean shutdown, all perfectly normal, no odd restarts or cable unplugs on the hdd.
I tried to shut it down cleanly once then relaunch and same thing. it's about 30 minutes there now - usually very fast to sync like 10-15 mins max.
Is there something going on the network?
I am syncing monero core and that one is going well.
On the log i can see several of these:
2021-04-06T09:50:14Z Disconnecting and discouraging peer 163! 2021-04-06T09:50:23Z New outbound peer connected: version: 70016, blocks=677993, peer=181 (full-relay) 2021-04-06T09:50:35Z New outbound peer connected: version: 70015, blocks=677993, peer=182 (full-relay) 2021-04-06T09:50:44Z ERROR: AcceptBlockHeader: block 0000000000000000000b818d87315f69398aa6ba886d869f8c403a41f509e7f7 is marked invalid 2021-04-06T09:50:44Z Disconnecting and discouraging peer 181! 2021-04-06T09:50:45Z ERROR: AcceptBlockHeader: block 0000000000000000000b818d87315f69398aa6ba886d869f8c403a41f509e7f7 is marked invalid 2021-04-06T09:50:45Z Disconnecting and discouraging peer 182! 2021-04-06T09:50:46Z New outbound peer connected: version: 70015, blocks=677993, peer=184 (full-relay) 2021-04-06T09:50:58Z New outbound peer connected: version: 70015, blocks=677993, peer=188 (full-relay) 2021-04-06T09:51:43Z New outbound peer connected: version: 70016, blocks=677993, peer=193 (full-relay) 2021-04-06T09:51:50Z ERROR: AcceptBlockHeader: block 0000000000000000000b818d87315f69398aa6ba886d869f8c403a41f509e7f7 is marked invalid 2021-04-06T09:51:50Z Disconnecting and discouraging peer 188!
Apparently this block is marked invalid:
2021-04-06T09:29:32Z ERROR: AcceptBlockHeader: block 0000000000000000000b818d87315f69398aa6ba886d869f8c403a41f509e7f7 is marked invalid throughout
please let me know
thanks, Gabrio
|
|
|
did anyone try with the -upgradewallet option?
|
|
|
thanks for replies, i will check stackexchange as well.
|
|
|
thanks guys, i usually backup regularly, it's so fast operation anyway, when i send out or get in coins, i always do that. but if i wanted to..... (geek here), is there a step by step guide or something?
|
|
|
hi,
I have my btc core, all going well, etc... and i see "HD" key generation disabled... i think i created the wallet before this feature was existing, so does it make sense that i migrate to an HD wallet? what are the benefits?
i am quite happy with the way it works, and backup recently, etc.
thanks! Gabrio
|
|
|
[...] yeah but all things considered it's not a bad hdd since it's usb3 and peaks 100-120 mb/sec or 800-950 mbit.
If you are fine with the speed, no reason to change something. But an external drive will always be slower than an internal (HDD) one. The protocol overhead alone already makes a huge difference. In addition to that, you'll only achieve best results if you only have your drive attached to the USB root as other devices will definitely influence the speed. After all, the main issue with external drives is the stability. Core requires a constant connection which can not be guaranteed using external drives. But if you only very rarely encounter an error and are fine with the (relatively acceptable) consequences, there is no reason to change your setup. heheh yep, i was contemplating adding another HDD inside this laptop since there's a bay available, but it will add to the weight a bit ;-) but yeah for now is ok, in the end, as long as there's a backup there's hope hehehehe
|
|
|
How low is your dbcache size? If it's on default, increasing it to at least half your RAM will help a lot.
But do that after your current task since that "61%" would be a waste if you stop it now.
BTW dbcache size, under Options > Main is 450 MiB right now. i have 16gb of ram on this machine. is that the one you mentioned to change? Set a value depending on how much is left when your system's RAM usage is at peak, just make sure to give room for some spare space, half of 16 is a good amount. As I've said, set that after finishing the -reindex process since it should be done by now. But do not expect a lot of boost since you're using an external drive, it's the bottleneck. ok thanks i will try yep it's finished. yeah but all things considered it's not a bad hdd since it's usb3 and peaks 100-120 mb/sec or 800-950 mbit. actually on a normal day - when it doesn't crash, for 7 days to catch up new blocks, it takes around 30-40 mins max only. From 1 or 2 latest releases, core is much much faster to catch up. Downloads really well blocks first maxxing out my connection usually and then does the grunt work.
|
|
|
just as a quick update, 24 hours after, just 61% reprocessed lol, maybe it will really take a week.
yes of course internal would be best but i don't have 300GB on my SSD unfortunately.
How low is your dbcache size? If it's on default, increasing it to at least half your RAM will help a lot. But do that after your current task since that " 61%" would be a waste if you stop it now. BTW dbcache size, under Options > Main is 450 MiB right now. i have 16gb of ram on this machine. is that the one you mentioned to change?
|
|
|
just as a quick update, 24 hours after, just 61% reprocessed lol, maybe it will really take a week.
yes of course internal would be best but i don't have 300GB on my SSD unfortunately.
How low is your dbcache size? If it's on default, increasing it to at least half your RAM will help a lot. But do that after your current task since that " 61%" would be a waste if you stop it now. Interesting, finished sync and catchup new blocks, so it's finished. 173 blocks to go. i will check that. thanks
|
|
|
just as a quick update, 24 hours after, just 61% reprocessed lol, maybe it will really take a week.
yes of course internal would be best but i don't have 300GB on my SSD unfortunately.
|
|
|
got it, if i do "reindex" option on command prompt, is he gonna RE DOWNLOAD (which takes 1 week) or just re-index in fact, which i think is like 12 hours? sorry but want to be sure.
thanks!
No, according to this it will only rebuilds the two leveldb databases for the block index and the chainstate, using the block files saved on disk. Which means it doesn't need to redownload the whole blockchain and it will only rebuild the blocks that you already downloaded. if i just delete that bad block he pointed out, that won't work either?
No you still need to use reindex command if you want to fix this issue. thanks, it's re-indexing now, see you in 1 week 😁
|
|
|
if i just delete that bad block he pointed out, that won't work either?
|
|
|
got it, if i do "reindex" option on command prompt, is he gonna RE DOWNLOAD (which takes 1 week) or just re-index in fact, which i think is like 12 hours? sorry but want to be sure.
thanks!
|
|
|
i checked log :
2020-10-18T16:51:39Z Fatal LevelDB error: Corruption: block checksum mismatch: X:\XXXX\chainstate/513482.ldb 2020-10-18T16:51:39Z You can use -debug=leveldb to get more complete diagnostic messages 2020-10-18T16:51:39Z Fatal LevelDB error: Corruption: block checksum mismatch: X:\XXXX\chainstate/513482.ldb 2020-10-18T16:51:39Z : Error opening block database. Please restart with -reindex or -reindex-chainstate to recover. 2020-10-18T16:54:58Z Aborted block database rebuild. Exiting.
|
|
|
hi guys,
this morning i was doing the "usual" sync, then the hard disk started clicking, most likely dust or bad cables (it's external), anyway the hdd is fine, did a good check on it and now i wanted to resync the blockchain.
Classic, I get "Error opening block database" Do you want to rebuild the database now?
Earlier on i had to kill the hard disk and unplug it as it was stuck so most likely the last block didn't write up correctly a closing.
If i click OK is it gonna resync 300+ gig worth of stuff or is he so smart that he can simply roll back the bad blocks say OK let's resume from here and be relatively short?
Or otherwise is there another command prompt thingie or anything to launch?
i have a backup so not end of the world if i have to resync etc but not ideal
thanks so much, Gab
|
|
|
Ok, i took the plunge, panic mode ON and launched the command.... it worked! thanks guys! guess it happens when you sync sometimes, right? always learn something new! No, it never happens to me and this is first time i saw message " ERROR: AcceptBlockHeader: block [HASH] is marked invalid" without user doing anything. It's more often to receive the block corrupted and Bitcoin Core download the block from another node. it might have been lots of syncs on and off, disconnecting the hard disk on and off, oh well it's solved now. happy days.
|
|
|
|