Love the mystery stuff, oh well - that's not the initial sync tho, it's the weekly catch-ups that had those issues. i don't use it 24/7, weekly sync usually.

Anyhow just wanted to share in case others also get stuck, disable the undervolting - and yes improving cooling is also great, in fact i have a very good Klim Coolpad when necessary now.

No, i am using Intel Extreme Tuning Utility, so software, nothing hardware at all. Don't care as i only use it when needing extra juice and on BTC core i know what to do.

The weird part is that only BTC core is affected. This laptop has been a workhorse since 5 years already, poor thing hehe.

hi guys,

I wanted to give an update on this issue...since this was last updated last year in Aug 2021.

So, this invalid block thing was happening quite often until i discovered something: I was always running my CPU with an undervolt flag for better temperature under heavy loads.

For some reason, at some point i disabled that flag while running Core, and again and again and i noticed that the issue with the invalid block NEVER happened again. I didn't change anything, i didn't change SSD drive, didn't format, didn't re-download the entire blockchain, nothing.

So i am quite happy i managed to find a solution that works. I still run the undervolt for other things and some other wallets but not for BTC core.

Still a mystery the reason why though ;-)

Best,
Gabrio

thanks for all tips!

thank you, i just let it do its thing while watching a movie and now it's cleared.... guess he had to catch up some blocks for good

hi there,

Just turned on my Core 0.23 (been about 30 mins) and i get

Fee Estimation failed . fallback fee is disabled. Wait a few blocks or enable -fallbackfee

Question: is mempool overloaded or there's something else going on? I've used it fine just 1 month ago and sent a transaction without that error almost right away after first sync.

Any tips? Just wait 1 hour and try again?

thanks

hi,

Well, it's very hard to say if it's the drive because, i ONLY use this ssd for crypto really, i have nothing else on it and it's also a very fast Samsung T7 SSD (1 gb/sec write and read) with built in encryption etc (which i am not using though).

Now, yes this happened many times now and i am quite clueless on why, I have never lost data on this ssd on other occasions. I am not mining at the moment but was helping the network with open port, etc. I have 2 others privacy coins and one of those also experienced same thing, reindex then now fine, the other one instead never had this issue,

I am gonna live with this, not ideal and again, the reason i am having this on external SSD is that i wanted a drive that does not stay on continuously like my "main" normal SSD where i do other stuff and my work, etc. As we all know these drives have an X lifespan and if they're on 24/7 that will get shortened every day.

Still, that's way bizarre so i am gonna send Samsung a message, maybe they can help or maybe this type of SSD is not suitable for crypto in general, hence the errors.

thanks for ideas and feedback anyway

it happened again, used reconsiderblock and that's that - it's really strange though. oh well moving on - thought the reindex corrected the issue but apparently didn't. i cannot keep this plugged in all the time so that'll do.

in the end it works, i can operate when i need to. thanks all

ok thanks but i figured it out myself, i did a -reindex and it finished, took 17 hours, let's see if it happens again now.

ok, this happened again - i will take the plunge and do a rescan / reindex most likely taking a week...... something similar happened on a smaller chain and it fixed the issue

what's the command? is that - reindex something via command like?

can anybody help on this please?

thank you,
Gabrio

ha! i talked too soon.... while doing a sync just now, again i got the same thing, this time with only BTC core running, i guess i need to rescan o re-do the whole blockchain at some point soon.... that will need 1 week or so though... arghhh again invalid block.

this time was a bit weird, it started doing the sync, was a good point and only 369 blocks left

any tips to do a full rescan or complete blockchain sync again? of course i just ignored the block again and it worked again.

it's actually not bad. on average if you do the BTC core sync once a week, it takes only 10-15 mins to sync with my system and this SSD. 

yeah that's right, and they all have full blockchains running - i am gonna run only one at a time, finish what i have to do, close then run the other one, etc.

The private ones actually are much more intense but bitcoin always triggers the highest CPU usage and I/O on the hard disk....this is a fast Samsung SSD T7 but then at the same time, maybe that's too much.

anyway time will tell

thanks guys - on the hard disk i don't completely agree with that, as in the USB port of the laptop, i think is something else, read below:

Now, what i think it could be is the fact that i am running simultaneously also 2 other crypto CORES which will be remain unknown for now so it's very well possible that sometimes slips out.

Power delivery issue i don't think so, it's plugged straight to the usb-c to the laptop and always with AC on.

I will try running only BTC core alone when i do the sync and not the 2 other chains as well - they never had this issue, though.

with that exclude command executed i can then transact, everything works normally, and if i need to do it ever 2-3 months is not a huge deal.

As i said, i don't think that's an issue with the USB port of the laptop but due to the setup i have - where i basically do my weekly sync for 3 CORE blockchains together (not always but quite often because the machine and the SSD is capable enough), that i think could lead to some minimal data corruption with the amount of I/O happening at the same time. And given that BTC is the "biggest" whale, i will let it go on his own only now.

time will tell

thanks again,
Gabrio

hello,

resurrecting a thread of a little while ago, it happened again i had to launch a "reconsiderblock" was wasn't syncing.. are these rogue blocks or something?

i mean i don't mind doing this but ideally shouldn't happen right? then picked up again and works now again. just like last time.

didnt have any unclean shutdowns, etc

thanks

nope, i am using an asus S15 Vivobook slightly pimped

Yes indeed but i find it better and safer having the data stored on an external hard disk, although the occasional problem like this may occur.

i just did extended mem testing all night over 8 hours, plus basic and standard testing, all no errors.

and frankly, i never never get any blue screen here which is usually RAM, since i installed this and i have a high performance Ram.

yeah you are right, you are like Sherlock Holmes hehe looks like i had that problem before.

and no, i am on Win10 64x.

only thing i can think of is that i have BTC core on ext usb 3.1 SSD drive (at that time it was not SSD tho). this one is faster now.

it's fully synced now. closed BTC.

checked disk, ran a CHKDSK no errors, ran a disk check from win10 also all good.

launched BTC core again, fully working this time instantly.