Topic: 0.13.1 sync problems, nearly finished, but stopped up several times - page 2. (Read 5113 times)

I'm 1 year and 46 weeks behind now. Nearest I come during my other attempt was around 39 weeks behind. I was also making a backup wallet that time, so I have 5 backups now

One of the forum members here warned me to send backup file to other.

You're trying to say that you can't sync up with the backup wallet, but with the original wallet it works?

You can open it, you just need better software to do so.

Good. As mentioned earlier, someone could extract your money from the backup one if needed.

I exite wallet first before rename wallet.dat to wallet.dat_original, then copied my backup, lommebok.dat, to BitCoinDat folder and renamed it to wallet.dat.
Debug.log was so huge that it was not possible to open it.
Right now sync my Bitcoin Core 0.13.1 with the network, but without my wallet backup.

What exactly did you do? Hopefully you did not attempt to alter any files during the synchronization itself? Check the debug log and post the latest (or most relevant) part of it.

After replaced wallet.dat with my bacup wallet the sync stopped up. No program error, but a huge debug list, around 600 000 bytes.

I'm trying to fix the problem. After closed Norton Firewall and opened Windows Defender (with the exemption) it seems that the wallet sync better. I'm now waiting for it to finish.

Answer the following question for yourself before you continue: Do you want to run a full node on this machine? If so, lets try and fix the problem with core. If not, lets try and get your keys off there safely.

I'm using Norton Firewall. Not sure how to use the exemption list there, so I closed it, and using Windows Defender now. Set bitcoin-qt. exe fil  to exemption and the folder i:BitCoinDate on exemption.

Yes, I have:

https://bitcointalksearch.org/topic/m.16736510

That tells us absolutely nothing. Again, have you run diagnostics on your hardware? Have you tried using another drive (perhaps an internal one) for storing the blockchain?

The windows reporting Runtime Error! is "Microsoft Visual C++ Runtime Library

You could upload it somewhere, or make a copy and cut out the unimportant stuff (e.g. clean block processing).

You can, either shorena or me (I'm usually online longer, in case that you miss them). Make sure that you keep in mind the concerns raised by them.

Could be a cable/port problem in that case. USB 3.0 is really flaky, and I've had this happen 2-3 times myself (the port on the laptop was not as stable as the one in my USB Hub which I've used afterwards). Fixing this required several reindexing attempts (during diagnostic time).

Might be the way the disk is connected? Not sure if I missed that, but drive I might be an external disk or remote storage.


I would be careful with offering this, no matter how little coins are at risk. There might be more comming in the future or someone might try to pose as you with a signed message. If you want to risk this regardless, you can send the file to [email protected]. Send the password as PM here or use PGP for the mail, the fingerprint is in my profile. Im online for a bit longer or later tonight.

Did you add the data directory to your Antivirus's exemptions list? Did you add it to Windows Defender's exemption list?

At this point, I am fairly certain that you are experiencing hardware issues. Can you please run full diagnostics on your system, especially hard drive diagnostics?

Can I send my wallet.dat to you? It's only a few satoshi. I have another wallet to send to.

The logfile so long that it was not possible to post it here.

Started from scratch again, with no backup file, but it stopped again.

Here is the beginning of debug file:

2016-11-01 10:19:02 Bitcoin version v0.13.1
2016-11-01 10:19:02 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2016-11-01 10:19:02 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2016-11-01 10:19:02 Default data directory C:\Users\Pc\AppData\Roaming\Bitcoin
2016-11-01 10:19:02 Using data directory I:\BitCoinData
2016-11-01 10:19:02 Using config file I:\BitCoinData\bitcoin.conf
2016-11-01 10:19:02 Using at most 125 connections (2048 file descriptors available)
2016-11-01 10:19:02 Using 2 threads for script verification
2016-11-01 10:19:02 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-11-01 10:19:02 scheduler thread start
2016-11-01 10:19:02 Using wallet wallet.dat
2016-11-01 10:19:02 init message: Verifiserer lommebok...
2016-11-01 10:19:02 CDBEnv::Open: LogDir=I:\BitCoinData\database ErrorFile=I:\BitCoinData\db.log
2016-11-01 10:19:02 Bound to [::]:8333
2016-11-01 10:19:02 Bound to 0.0.0.0:8333
2016-11-01 10:19:02 Cache configuration:
2016-11-01 10:19:02 * Using 2.0MiB for block index database
2016-11-01 10:19:02 * Using 8.0MiB for chain state database
2016-11-01 10:19:02 * Using 290.0MiB for in-memory UTXO set
2016-11-01 10:19:02 init message: Laster blokkindeks...
2016-11-01 10:19:02 Opening LevelDB in I:\BitCoinData\blocks\index
2016-11-01 10:19:03 Opened LevelDB successfully
2016-11-01 10:19:03 Using obfuscation key for I:\BitCoinData\blocks\index: 0000000000000000
2016-11-01 10:19:03 Opening LevelDB in I:\BitCoinData\chainstate
2016-11-01 10:19:03 Opened LevelDB successfully
2016-11-01 10:19:03 Wrote new obfuscate key for I:\BitCoinData\chainstate: 9de17794bb6078e4

And the ending:

2016-11-01 12:18:23 UpdateTip: new best=0000000000000016fb5d54cda09dc9cb258e7732ea53dba00d63813326a0c2d3 height=260223 version=0x00000002 log2_work=72.230796 tx=24462164 date='2013-09-26 11:25:15' progress=0.077040 cache=219.2MiB(298597tx)
2016-11-01 12:18:23 Pre-allocating up to position 0x600000 in rev00083.dat
2016-11-01 12:18:23 UpdateTip: new best=0000000000000009937df8908628d423f44f19a97b2087f1227c1a04f131d4c8 height=260224 version=0x00000002 log2_work=72.230963 tx=24462190 date='2013-09-26 11:26:00' progress=0.077040 cache=219.2MiB(298610tx)
2016-11-01 12:18:23 LevelDB read failure: Corruption: block checksum mismatch
2016-11-01 12:18:23 Corruption: block checksum mismatch
2016-11-01 12:21:08 Error reading from database: Database corrupted

Log files please (again).

I'm assuming this has to do with how you installed the data on a separate drive.  If you believe the application is the reason why you are having these issues and not your hardware, you could alternatively try downloading the blockchain over the torrent network.

If you really want to just extract your wallet and not bother with it anymore, you could give someone the wallet.dat (make sure they're trusted) and install Electrum (SPV client). They can then send you the funds.

There's no *support team*. Usually the way to get help is either this board, IRC or the issues page on Github (I see that you've already created an issue).