bitcoin-qt wallet crashes twice a month, database corrupted

induktor

hero member

Activity: 710

Merit: 502

Quote from: LFC_Bitcoin on November 22, 2016, 01:28:07 PM

Similar happened to me today, it's happened once before, around 6-8 months ago but my Core Wallet crashed again today, think Windows did something fucked up without my permission & when I got home the mouse pointer was stuck & nothing worked.

Now I've got to reindex again which will take me about 2-3 days.

Not happy.

Does this still happen with version 0.13.1

huh... not good Sad

, use this to reindex if you have 16GB of ram and at least a quad core processor.

bitcoin-qt --dbcache=8192 --reindex

it will speedup the rebuild a lot (in my machine usually the entire process take 30 hours, with this it only took 8 hours to do that but it will use about 10GB of ram and a lot of cpu time)

achow101 give me this recommendation (at the begining of the post) and worked fantastically, i can wait 8 hours, but not 30 hours!!!! hehe

hope it helps a little

inkt

LFC_Bitcoin

legendary

Activity: 3556

Merit: 9709

#1 VIP Crypto Casino

Similar happened to me today, it's happened once before, around 6-8 months ago but my Core Wallet crashed again today, think Windows did something fucked up without my permission & when I got home the mouse pointer was stuck & nothing worked.

Now I've got to reindex again which will take me about 2-3 days.

Not happy.

Does this still happen with version 0.13.1

induktor

hero member

Activity: 710

Merit: 502

Quote from: Abdussamad on November 19, 2016, 03:20:00 AM

are you indian? anyway if it's not the ssd then it could be ram. run mem test for a couple of hours.

South american (argentina) power utility here is probably far worse than india.

Not ram, i swapped by identical sticks from another machine, run Memtest86 for an entire day, perfect both.
also i have a better way to test memory (sometimes Memtest86+ miss some memory hiccups) using quickpar2
probably the most memory intensive app i know, i create the par2 files for a 4GB iso image for example and
then check the par2 against the file, and if it fails, memory is the problem 99% of the time.

the problem is that quickpar is quite old, and doesn't like windows7 or newer, and also doesn't like more than
3gb of ram, so i have to virtualize it in order to be able to run it, but still the most reliable memory tester i found so far.

my bet is that the primary cause of the issue is what achow101 said in his first post, i think he nailed it. that
defender is from time to time messing with the blocks on disk and fucking things up, i disabled defender, we'll see
but my bet is that defender was the problem.

Abdussamad

legendary

Activity: 3682

Merit: 1580

Quote from: induktor on November 18, 2016, 02:26:28 PM

Hello
I know that bitcoin-qt doesn't like when you shutdown the machine with the wallet running, i did it once and pay the price hehe Grin

This machine has a SSD Samsung 840 PRO 250GB which is a pretty good ssd drive!, very reliable.
also this machine is connected to a APC SMART 2200XLI with extended battery, so even in a power outage scenario i have hours of operation, and even then, i have a generator (honda inverter, very clean output)

hehe (yeah power utility in this country is a joke, you need to have all this crap to be able to work!) Roll Eyes

are you indian? anyway if it's not the ssd then it could be ram. run mem test for a couple of hours.

induktor

hero member

Activity: 710

Merit: 502

Hello
I know that bitcoin-qt doesn't like when you shutdown the machine with the wallet running, i did it once and pay the price hehe Grin

This machine has a SSD Samsung 840 PRO 250GB which is a pretty good ssd drive!, very reliable.
also this machine is connected to a APC SMART 2200XLI with extended battery, so even in a power outage scenario i have hours of operation, and even then, i have a generator (honda inverter, very clean output)

hehe (yeah power utility in this country is a joke, you need to have all this crap to be able to work!) Roll Eyes

Abdussamad

legendary

Activity: 3682

Merit: 1580

I can think of a few things that could cause this:

- Last I tried bitcoin core you had to manually shut it down before you shut down the computer i.e. it would not automatically shut down with the OS. If you didn't do this there would be DB corruption
- Like achow101 said DB corruption can be a sign of a hardware problem. In my experience it can be a sign of a failing hard drive.

If I was you I'd definitely make sure bitcoin core was shutting down correctly when you shut down your OS. If you live in an area with power cuts you have to get a UPS or this DB corruption will keep happening.

As for the second point you can run chkdsk to check your hard drive for bad sectors.

BTW electrum is one of the most widely used wallets. You shouldn't be afraid to use it.

induktor

hero member

Activity: 710

Merit: 502

Quote from: unamis76 on November 17, 2016, 09:35:39 AM

All right, so I guess the network isn't the issue. I asked because from my experience, even machines with quite a bit of RAM tend to see bitcoind crashing due to too many connections filling up all the RAM.

Oh yes i read that like a year ago, probably the reason why i have maxconnections=6 hehe, i think i did have that issue before, not recently though

it is good to know though that it can still be an issue, maxconnections will stay there

thanks!

unamis76

legendary

Activity: 1512

Merit: 1012

All right, so I guess the network isn't the issue. I asked because from my experience, even machines with quite a bit of RAM tend to see bitcoind crashing due to too many connections filling up all the RAM.

induktor

hero member

Activity: 710

Merit: 502

I have max connections set to 6
my ISP is shit, ADSL 3 MB download, 512K upload (and that is in a good day!)

I cannot order more speed because i am too far from the DSL base station and lost sync, so i had to go back to 3MB max.
if i choose cable provider (only second option to ADSL) it is 10 Mb down /1Mb up, but every cable company here throttle all P2P traffic, including bitcoin making it useless, it takes 20 times more to update the wallet using cable than using 3MB ADSL (since adsl does not do any P2P throttle).

so, unless i am willing to pay 10x more money to order a professional grade with SLA, i have to survive with ADSL until i move out Grin

i also have bandwidth capped bitcoin at the router level (mikrotik) so i can browse the web while i am updating the wallet, otherwise it would be impossible.

unamis76

legendary

Activity: 1512

Merit: 1012

What's your connection? Have you tried limiting the amount of acceptable incoming connections?

mindrust

legendary

Activity: 3276

Merit: 2442

Quote from: induktor on November 16, 2016, 07:51:58 AM

Quote from: mindrust on November 16, 2016, 06:30:50 AM

I also had the same problem with the core wallet. It gotten corrupted and started to fix itself after i delete a few blocks. It took days to make it work again.

I deleted it and using electrum now.

I felt like i was part of something while it was working but after it started to crap on me i realized that home users do not need to download 100gb of useless crap. Don't make any sense.

I don't trust electrum wallet, maybe is my lack of knowledge, or paranoia, but, for me, bitcoin is real money, and i need to be absolutely sure of the reliability of the wallet, that's why i use the official (full node) wallet, i also use the phone (android) wallet for petty change, but for the primary wallet i wanna be sure i can rely on it.

i don't care about 100 gb of data if i know that my money is secure, that i can do transactions reliably whenever i need to, if that takes 100gb, or 200gb or 300gb of ssd storage, i buy a bigger/faster ssd, i can live with that, that's why i did this thread because i was worried that i didn't know why the wallet get screwed up every now and then, thanks to achow101 here, i think he nailed it with the defender messing with the data blocks from time to time, causing the wallet to crash.

probably i should try electrum as a secondary wallet, it's been around a long time and if it has problems we probably already read them in the forum right? Grin

will give it a try

I also had suspicions like you. After i deleted the core wallet, there was a topic popped up in the forum saying that the electrum has trojan. (1/50 of the online antivirus showed that it has a malicious code inside, probably false positive) Deleted electrum went back to the core wallet. Then it have gotten corrupted again. I was mad again. Back to electrum Cheesy

induktor

hero member

Activity: 710

Merit: 502

Quote from: mindrust on November 16, 2016, 06:30:50 AM

I also had the same problem with the core wallet. It gotten corrupted and started to fix itself after i delete a few blocks. It took days to make it work again.

I deleted it and using electrum now.

I felt like i was part of something while it was working but after it started to crap on me i realized that home users do not need to download 100gb of useless crap. Don't make any sense.

I don't trust electrum wallet, maybe is my lack of knowledge, or paranoia, but, for me, bitcoin is real money, and i need to be absolutely sure of the reliability of the wallet, that's why i use the official (full node) wallet, i also use the phone (android) wallet for petty change, but for the primary wallet i wanna be sure i can rely on it.

i don't care about 100 gb of data if i know that my money is secure, that i can do transactions reliably whenever i need to, if that takes 100gb, or 200gb or 300gb of ssd storage, i buy a bigger/faster ssd, i can live with that, that's why i did this thread because i was worried that i didn't know why the wallet get screwed up every now and then, thanks to achow101 here, i think he nailed it with the defender messing with the data blocks from time to time, causing the wallet to crash.

probably i should try electrum as a secondary wallet, it's been around a long time and if it has problems we probably already read them in the forum right? Grin

will give it a try

mindrust

legendary

Activity: 3276

Merit: 2442

I also had the same problem with the core wallet. It gotten corrupted and started to fix itself after i delete a few blocks. It took days to make it work again.

I deleted it and using electrum now.

I felt like i was part of something while it was working but after it started to crap on me i realized that home users do not need to download 100gb of useless crap. Don't make any sense.

Hanslo

sr. member

Activity: 263

Merit: 250

Quote from: induktor on November 16, 2016, 06:14:11 AM

Quote from: Hanslo on November 16, 2016, 03:19:41 AM

I had a similar problem a couple of times. Now I'm using Norton Firewall after a consultant from Norton helped me to make exception, and 0.13.1 running ok.

But after Windows update I got crash like you. I shut down my computer and startet again. Startet bitcoin-qt wallet and after a couple of minuts it was up and go.

Hi
usually if bitcoin-qt hangup due to a block corruption, it will work again, as long as it does not attempt to access that block, once that detects the fucked up block it will hangup again, so the only solution is to do a --reindex, which takes a very long time, and my main complain is that why, if it detects a damaged block, it does not redownload it, instead, it forces you to do a full disk reindex which is crazy!.

at least with the hyper-mega tip achow101 give me of use the --dbcache=hughememoryusenumber lowered the processing time a lot, but it still takes a long time (and i know my computer is two - three year old machine, i should get at least a 6th gen intel i5 with pci-e M2 SSD, will do as soon as i can get the money for it

that kind of hw is very expensive here in my area

)

the other way is to restore from backup, which i can do, i backup the entire blockchain to a 7z file once a month and keep three copies, but i wanted to find another solution to prevent this or solve it quickly.

3weeks behind... almost done!!

Here is how it looks for me:

Code:

2016-11-11 20:34:20 UpdateTip: new best=000000000000000001542e46acf8bd8901baae7dfa47f44950c48b139c88371a height=438440 version=0x20000000 log2_work=85.529235 tx=169959484 date='2016-11-11 20:15:51' progress=0.999995 cache=126.1MiB(62820tx)
2016-11-11 20:34:21 tor: Thread interrupt
2016-11-11 20:34:21 torcontrol thread exit
2016-11-11 20:34:21 scheduler thread interrupt
2016-11-11 20:34:21 addcon thread interrupt
2016-11-11 20:34:21 net thread interrupt
2016-11-11 20:34:21 opencon thread interrupt
2016-11-11 20:34:21 ProcessMessages: advertising address [2001:0:5ef5:79fd:24ba:1f45:a322:8ce1]:8333
2016-11-11 20:34:21 receive version message: /Satoshi:0.13.1/: version 70014, blocks=438444, us=92.221.115.30:59592, peer=5
2016-11-11 20:34:21 msghand thread interrupt
2016-11-11 20:34:21 Shutdown: In progress...
2016-11-11 20:34:21 StopNode()
2016-11-11 20:34:23 Corruption: block checksum mismatch
2016-11-11 20:34:23 *** System error while flushing: Database corrupted
2016-11-11 20:34:41 Shutdown: done

It did'nt reindex.

induktor

hero member

Activity: 710

Merit: 502

Quote from: Hanslo on November 16, 2016, 03:19:41 AM

I had a similar problem a couple of times. Now I'm using Norton Firewall after a consultant from Norton helped me to make exception, and 0.13.1 running ok.

But after Windows update I got crash like you. I shut down my computer and startet again. Startet bitcoin-qt wallet and after a couple of minuts it was up and go.

Hi
usually if bitcoin-qt hangup due to a block corruption, it will work again, as long as it does not attempt to access that block, once that detects the fucked up block it will hangup again, so the only solution is to do a --reindex, which takes a very long time, and my main complain is that why, if it detects a damaged block, it does not redownload it, instead, it forces you to do a full disk reindex which is crazy!.

at least with the hyper-mega tip achow101 give me of use the --dbcache=hughememoryusenumber lowered the processing time a lot, but it still takes a long time (and i know my computer is two - three year old machine, i should get at least a 6th gen intel i5 with pci-e M2 SSD, will do as soon as i can get the money for it

that kind of hw is very expensive here in my area

)

the other way is to restore from backup, which i can do, i backup the entire blockchain to a 7z file once a month and keep three copies, but i wanted to find another solution to prevent this or solve it quickly.

3weeks behind... almost done!!

induktor

hero member

Activity: 710

Merit: 502

I am still rebuilding (processing blocks on disk) since last night, but the --dbcache=8192 did a HUGE impact on processing speed, now bitcoin-qt is using 8GB of ram and 100% CPU and ssd is at 90% load, and i am just at 5 weeks away from completion, so it would take less then 8 hours (previously was 30 hours without the --dbcache parameter), freaking fantastic!.

btw: i still need to buy a faster computer though Grin

i want that number lowered to 4 hours (reindex && processing blocks on disk time).

Hanslo

sr. member

Activity: 263

Merit: 250

I had a similar problem a couple of times. Now I'm using Norton Firewall after a consultant from Norton helped me to make exception, and 0.13.1 running ok.

But after Windows update I got crash like you. I shut down my computer and startet again. Startet bitcoin-qt wallet and after a couple of minuts it was up and go.

induktor

hero member

Activity: 710

Merit: 502

Quote from: achow101 on November 15, 2016, 09:08:36 PM

Double check that Windows defender isn't messing with the blockchain. It tends to do that.

AHAAAAA!! that mother F&$*# of defender, disabled, done, it is very likely the issue!, i never thought about it!.

Quote from: induktor on November 15, 2016, 09:02:46 PM

starts a rescan, and the rescan is the process that takes more than a day to complete, and it is only using 20% CPU usage, and disk usage is also 20% so not really taking advantage of the machine capabilities.

You are incorrect. Rescanning does not happen after a reindex. A rescan takes place at startup during the splash window. After the splash window you see the normal wallet view. Reindexing happens there, and it looks a lot like resyncing the blockchain because of the progress bar at the bottom.

yep, my bad, you are right

, i meant after the reindexing it says processing blocks on disk, and that is the process that takes forever.

i bet that the issue was defender!.
thank you for taking the time to explain and help me

Topic: bitcoin-qt wallet crashes twice a month, database corrupted (Read 2490 times)