…022-07-18T10:56:59.419466Z INFO Init: main: Still rescanning. At block 1725843. Progress=0.990314
2022-07-18T10:59:37.506414Z INFO Init: main: Still rescanning. At block 1725845. Progress=0.990314
2022-07-18T11:09:33.713299Z INFO Init: main: Still rescanning. At block 1725846. Progress=0.990309
2022-07-18T11:11:03.820310Z INFO Init: main: Still rescanning. At block 1725847. Progress=0.990309
2022-07-18T11:14:08.912884Z INFO Init: main: Still rescanning. At block 1725849. Progress=0.990308
2022-07-18T11:26:15.057549Z INFO Init: main: Still rescanning. At block 1725851. Progress=0.990304
2022-07-18T11:30:28.700889Z INFO Init: main: Still rescanning. At block 1725852. Progress=0.990303
2022-07-18T11:40:31.789186Z INFO Init: main: Still rescanning. At block 1725856. Progress=0.990299
2022-07-18T11:43:54.190974Z INFO Init: main: Still rescanning. At block 1725859. Progress=0.990299
2022-07-18T11:44:55.558447Z INFO Init: main: Still rescanning. At block 1725860. Progress=0.990298
2022-07-18T11:54:17.412680Z INFO Init: main: Still rescanning. At block 1725862. Progress=0.990295
2022-07-18T11:57:05.603360Z INFO Init: main: Still rescanning. At block 1725863. Progress=0.990294
2022-07-18T11:58:33.452451Z INFO Init: main: Still rescanning. At block 1725864. Progress=0.990294
2022-07-18T11:59:48.586427Z INFO Init: main: Still rescanning. At block 1725865. Progress=0.990296
2022-07-18T12:14:11.875190Z INFO Init: main: Still rescanning. At block 1725866. Progress=0.990289
2022-07-18T12:20:08.638476Z INFO Init: main: Still rescanning. At block 1725867. Progress=0.990286
2022-07-18T12:24:59.388889Z INFO Init: main: Still rescanning. At block 1725869. Progress=0.990285
2022-07-18T12:26:22.821597Z INFO Init: main: Still rescanning. At block 1725871. Progress=0.990285
2022-07-18T12:28:24.086896Z INFO Init: main: Still rescanning. At block 1725872. Progress=0.990285
2022-07-18T12:32:20.445594Z INFO Init: main: Still rescanning. At block 1725873. Progress=0.990284
2022-07-18T12:36:06.091991Z INFO Init: main: Still rescanning. At block 1725874. Progress=0.990282
After I upgraded zcash to v5.1.0, it has started rescanning a week. At Last I found the progress is moving backward.
Is there any way to this problem？Thanks.
Due to the recent increase in transaction outputs, blocks are harder to validate. In fact, they are being produced faster than your machine can check them. Unless the situation changes, you will not catch up, unfortunately.
I just want to transfer coin from my old wallet. But if I do not rescan the blockchain, I can’t make it.
Is there any solution to solve it? Thank you for your reply.
Thank you for your reply.
I just want to transfer coin from my old wallet. There is no any estimated time for v5.2.0 release, but I need solve it as soon as possible. I have tried a lot of methods like starting a new node to import the backup wallet, but no one works. I really don’t know what to do next.
I would guess these issues are more likely to be memory related. With Windows you can allocate a readyboost partition somewhere like on a quality, high speed SD card or flash drive and will work most of the time for ram bottlenecks. On Linux it’s a swap file and you can adjust what’s called swapiness. Idk if you can on Windows but typically it seems it gets used a lot.
I’m running two 5.1.0 nodes, on one an i5 mesa 1.7ghz x8 with 8GB and one on a Xeon 2.8ghz x8 with 12GB. Both are on HDDs which I didn’t consider before but both are using 3.7 GB and my cpus aren’t throttling much at all. Zcashd spawns like 20 something processes under zc-wait-to-stop but it’s incuring like 20% max per single thread at any one time while the other threads are 0-5% most commonly. The Xeon is even less noticable usage. The Network up and down gets wild but thats normal I think. Mostly it’s just a spike for a second then pretty low usage.
