Bitcoin version v0.12.1 crashing

mdance commented at 8:42 pm on July 23, 2016: none

I have been trying to sync of the blockchain after an extended period away. I have left my laptop on to sync for a few days now, and all of a sudden it is crashing everytime I try to open it:

Upon running the following from the command line, this is what I am getting in my console:

/Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -printtoconsole -debug

… 2016-07-23 20:37:45 init message: Verifying blocks… 2016-07-23 20:37:45 Verifying last 288 blocks at level 3 fish: ‘/Applications/Bitcoin-Qt.app/Co…’ terminated by signal SIGBUS (Misaligned address error)

jonasschnelli commented at 6:40 am on July 25, 2016: contributor

I think you have some corrupted data on your disk. You can try to do a -reindex (will take a couple of hours/days). Also, if we would have something like this (https://github.com/bitcoin/bitcoin/issues/8037) then we could rollback to the last periodic dump.

Also try to do a hardware test (https://support.apple.com/en-us/HT201257) to check if your memory is working correct.

jonasschnelli added the label Data corruption on Jul 25, 2016

laanwj commented at 12:26 pm on July 25, 2016: member

Misaligned address error? Wow - haven’t seen one of those in a while. Is this x86 or something else?

mdance commented at 3:02 pm on July 25, 2016: none

I am running a MacBook Pro (13-inch, Early 2011), due to the size of the blockchain, I’ve actually had to move everything to a portable hard drive, so not sure if thats to blame.

I was about 3 weeks behind and was syncing for several days trying to catch up it got about 3-5 days from being in sync and then this crash started happening.

sipa commented at 3:05 pm on July 25, 2016: member

I suggest you run in pruning mode instead of using a portable disk. For some reason we see a lot of problems with those.

mdance commented at 3:07 pm on July 25, 2016: none

Where can I read more about that?

mdance commented at 3:17 pm on July 26, 2016: none

I’ve just finished doing a -reindex and am getting the following error:

2016-07-26 13:22:06 UpdateTip: new best=000000000000000037ccc8716a9a69c846e5b98bf10a9210182fecc3f8b2623a height=309175 log2_work=79.539546 tx=41916198 date=2014-07-04 14:24:33 progress=0.219166 cache=52.3MiB(12238tx) 2016-07-26 13:22:06 - Connect postprocess: 4.85ms [437.21s] 2016-07-26 13:22:06 - Connect block: 4094.52ms [74108.20s] 2016-07-26 13:22:06 got inv: tx 7693f33ce073e27608e6765e9647c96e42cf0859fc474b3b629d9c1f88e4abcf new peer=741 2016-07-26 13:22:06 got inv: tx 202ee78892c959cb6e4e30596549a11922175d50f89496e07232ae2f685fcf81 new peer=741 2016-07-26 13:22:06 got inv: tx 5ee250668e06fbf4d20eea747380099e06188ba9301f4c24ad6d8037edb2ddee new peer=741 2016-07-26 13:22:06 25: For conf success > 0.95 need FeeRate >: 5209.2 from buckets 5559.92 - 6115.91 Cur Bucket stats 98.24% 159.7/(162.6+0 mempool) 2016-07-26 13:22:06 got inv: tx 4af38ab035084d5f79effafec7facf4b8d6c7dc552755329c190109da7f15d99 new peer=741 2016-07-26 13:22:06 got inv: tx a339199733ceafc0e7a0d3d3d2c98d89a174cf3afe9cbadec499a8a92b177168 new peer=741 2016-07-26 13:22:06 got inv: tx 12b5b5f9e88f92ab678a1963fcc31ade02e30a22dfdcb979df1a873ded8a9542 new peer=741 2016-07-26 13:22:06 got inv: tx 8285dd07d18c3adcda5fcccd8f0cff13e04a1e86caa5af5aa41cbcbf14bc5e42 new peer=741 2016-07-26 13:22:06 got inv: tx bfdedc908e0c3a518d1904e7b23afb5c81401cda0680675bfd81e2d8ffeed60f new peer=741 2016-07-26 13:22:06 got inv: tx 3298c55e20446d68648b513986c100fa240d7162c2596a47cf0d857b9dce6e01 new peer=741 2016-07-26 13:22:06 got inv: tx ca6c8b45c87d458b4e3a1bca05587f0b9d83b271f04a9f4e190cc7540ef3d43a new peer=741 2016-07-26 13:22:06 got inv: tx 512ef6bfb299979dad4bb2284b13fa2fee764766e8191c588d056a023673309d new peer=741 2016-07-26 13:22:06 received: inv (73 bytes) peer=744 2016-07-26 13:22:06 got inv: tx 4eec4fe768a92eb3d3e13ad1b7fc832d5db0e71ca834b5a31ca67ea512a7b174 new peer=744 2016-07-26 13:22:06 got inv: tx 15e505c2dac48b12757b2d2c5b8b740e5f546d477e5d443b52d87d6dfe1a4464 new peer=744 2016-07-26 13:22:06 received: inv (37 bytes) peer=751 2016-07-26 13:22:06 got inv: tx 9ee9f5c396c94bdd133be89d965aa5f3675618f18957bb79d83f9b4a5655c965 new peer=751 2016-07-26 13:22:06 received: ping (8 bytes) peer=773 2016-07-26 13:22:06 sending: pong (8 bytes) peer=773 2016-07-26 13:22:06 received: ping (8 bytes) peer=805 2016-07-26 13:22:06 sending: pong (8 bytes) peer=805 2016-07-26 13:22:06 received: ping (8 bytes) peer=823 2016-07-26 13:22:06 sending: pong (8 bytes) peer=823 2016-07-26 13:22:06 received: ping (8 bytes) peer=827 2016-07-26 13:22:06 sending: pong (8 bytes) peer=827 2016-07-26 13:22:06 received: inv (37 bytes) peer=8 2016-07-26 13:22:06 got inv: tx df97e9221a796853aa1d465fe382818c9e11eaae16f947a9ce3ab78f7b35dacd new peer=8 2016-07-26 13:22:06 received: inv (109 bytes) peer=15 2016-07-26 13:22:06 got inv: tx 4a8734cbd25eb1d761fad5512a0b2a2c2a2bb70628d2000ed8a49ccc04ef6470 new peer=15 2016-07-26 13:22:06 got inv: tx 36f71740fcc4875f6d2f4eb5d5ec20b6da54f869b6c269958156dd6f1e585367 new peer=15 2016-07-26 13:22:06 got inv: tx bab85b4ca222aa0ad67fc0cb084915d16a0dff59d660621c814963c420f56e0c new peer=15 2016-07-26 13:22:06 received: inv (37 bytes) peer=534 2016-07-26 13:22:06 got inv: tx e00bf657f0e0439af4fe28f1ae49f74e34d8bc0c01cc00f1788d72432c51ba2d new peer=534 2016-07-26 13:22:06 received: inv (37 bytes) peer=674 2016-07-26 13:22:06 got inv: tx 24818d24ca80fa676896b037a571f2eb9f753fb7343d1c9e8230a354384f678a new peer=674 2016-07-26 13:22:06 received: ping (8 bytes) peer=690 2016-07-26 13:22:06 sending: pong (8 bytes) peer=690 2016-07-26 13:22:06 received: inv (37 bytes) peer=736 2016-07-26 13:22:06 got inv: tx 0c6654d116e171e61c17c0426ece56b19752612bb2b558135c798b0d5e0e09eb new peer=736 2016-07-26 13:22:06 received: ping (8 bytes) peer=739 2016-07-26 13:22:06 sending: pong (8 bytes) peer=739 2016-07-26 13:22:06 received: ping (8 bytes) peer=740 2016-07-26 13:22:06 sending: pong (8 bytes) peer=740 2016-07-26 13:22:06 received: inv (37 bytes) peer=741 2016-07-26 13:22:06 got inv: tx 554ec936ef1932ec1cdb852f69d9e4bb225ab2dd4d1dfe56d715c3342c3a1dd2 new peer=741 2016-07-26 13:22:06 received: inv (37 bytes) peer=744 2016-07-26 13:22:06 got inv: tx f59600c12740a9abfa662e66578693895608d783418778a374edb5534db7daa3 new peer=744 2016-07-26 13:22:06 received: inv (37 bytes) peer=751 2016-07-26 13:22:06 got inv: tx 6ab6d856cc3afbda41475521662b2a658a030503c67bd0c4ccc0f651e0ab377b new peer=751 2016-07-26 13:22:06 received: ping (8 bytes) peer=773 2016-07-26 13:22:06 sending: pong (8 bytes) peer=773 2016-07-26 13:22:06 received: ping (8 bytes) peer=805 2016-07-26 13:22:06 sending: pong (8 bytes) peer=805 2016-07-26 13:22:06 received: ping (8 bytes) peer=823 2016-07-26 13:22:06 sending: pong 2016-07-26 13:22:06 - Load block from disk: 0.00ms [1.26s] 2016-07-26 13:22:06 - Sanity checks: 0.01ms [4.33s] 2016-07-26 13:22:06 (8 bytes) peer=823 2016-07-26 13:22:06 - Fork checks: 0.14ms [881.79s] 2016-07-26 13:22:06 received: ping (8 bytes) peer=827 2016-07-26 13:22:06 sending: pong (8 bytes) peer=827 2016-07-26 13:22:06 received: inv (37 bytes) peer=8 fish: ‘/Applications/Bitcoin-Qt.app/Co…’ terminated by signal SIGBUS (Misaligned address error)

mdance commented at 2:43 pm on August 15, 2016: none

I am still having this issue and unable to sync the blockchain, I cleared up hard drive space to attempt copying the bitcoin directory back onto my hard drive and received the following error:

The finder can’t complete the operation because some data in “XXXXXX.ldb” can’t be read or written. (Error code -36)

It looks like this happens with two files located in the chainstate folder.

Has anyone got an suggestions on what I can try?

laanwj commented at 9:32 am on August 16, 2016: member

The finder can’t complete the operation because some data in “XXXXXX.ldb” can’t be read or written. (Error code -36)

Sounds like a harddisk/file system issue, probably the one you’re copying from (though the error message is ambiguous in this regard). There’s nothing you can do besides discard the entire database if a few of the ldb files are corrupted.

mdance commented at 4:58 pm on August 16, 2016: none

To proceed safely, which files would I delete?

Bitcoin bitcoind.pid chainstate/ db.log fee_estimates.dat testnet3/ bitcoin.conf blocks/ database/ debug.log peers.dat wallet.dat

sipa commented at 5:03 pm on August 16, 2016: member

If you delete wallet.dat, your funds will be gone (but perhaps you have a backup, or you don’t have any funds).

bitcoind.pid shouldn’t exist unless bitcoind is running (in which case you shouldn’t delete anything).

MarcoFalke commented at 5:13 pm on August 16, 2016: member

I am still having this issue and unable to sync the blockchain, I cleared up hard drive space to attempt copying the bitcoin directory back onto my hard drive

So if the blocks are back on your disk, but the chainstate is corrupted you could try -reindex-chainstate (or -reindex on 0.12.1).

If you are almost out of diskspace, you might try setting a prune target. (https://bitcoin.stackexchange.com/questions/37496/how-can-i-run-bitcoind-in-pruning-mode)

mdance commented at 5:27 pm on August 16, 2016: none

If I am using Armory, is it still possible to use pruning?

achow101 commented at 5:29 pm on August 16, 2016: member

No. Armory doesn’t support pruning.

On August 16, 2016 1:27:45 PM Michael Dance notifications@github.com wrote:

If I am using Armory, is it still possible to use pruning?

You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #8395 (comment)

mdance commented at 1:45 am on August 23, 2016: none

How long should this -reindex take to complete? It has been running since MarcoFalke posted and its still going…

jonasschnelli commented at 6:30 am on August 23, 2016: contributor

@mdance with the default dbcache of 300MB it can take days (depending on your CPU and Disk). If you have enough ram, you should run with a larger -dbcache, If you have 4MB of RAM, you might want to run it with -dbcache=2500

mdance commented at 4:23 am on September 6, 2016: none

Running with the -reindex -dbcache=2500 has fixed the issue and I am now synced up

fanquake closed this on Oct 9, 2016

MarcoFalke locked this on Sep 8, 2021

Bitcoin version v0.12.1 crashing #8395