mirror of
https://github.com/raspiblitz/raspiblitz.git
synced 2025-11-18 18:07:45 +01:00
Compare commits
16 Commits
copilot/up
...
v1.10
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
3c207ac909 | ||
|
|
f2fde48542 | ||
|
|
63d5974e40 | ||
|
|
828874b9f8 | ||
|
|
3975454887 | ||
|
|
d237e10b8c | ||
|
|
0478d2066c | ||
|
|
e04df01acb | ||
|
|
4b5e3b7e0f | ||
|
|
d158345bab | ||
|
|
94d91b663f | ||
|
|
4fa4edd310 | ||
|
|
3997b3badf | ||
|
|
1e28523705 | ||
|
|
8685987f9e | ||
|
|
bb57156f90 |
4
FAQ.md
4
FAQ.md
@@ -343,11 +343,11 @@ Once you finished all the transfers, the Raspiblitz will make a quick-check on t
|
||||
|
||||
### Bitcoind tells me to reindex - how can I do this?
|
||||
|
||||
To find/access information fast in large data sets like the Bitcoin blockchain indexes are needed. Those indexes can get corrupted on your HDD/SSD and to repair them they need to be rebuild - re-indexed. Bitcoind has two different options to do this - a fast way called "reindex-chainstate" (which just rebuilds the UTXO set from the blocks as you have them) and the slow but complete way called just "reindex" that would even recheck all your block data - see for details here: https://bitcoin.stackexchange.com/questions/60709/when-should-i-use-reindex-chainstate-and-when-reindex
|
||||
To find/access information fast in large data sets like the Bitcoin blockchain indexes are needed. Those indexes can get corrupted on your HDD/SSD and to repair them they need to be rebuilt - re-indexed. Bitcoind has two different options to do this - a fast way called "reindex-chainstate" (which just rebuilds the UTXO set from the blocks as you have them) and the slow but complete way called just "reindex" that would even recheck all your block data - see for details here: https://bitcoin.stackexchange.com/questions/60709/when-should-i-use-reindex-chainstate-and-when-reindex
|
||||
|
||||
So if you read in your debug logs of bitcoind that you should "reindex" you can try first just to do a fast "reindex-chainstate" and if that didnt worked a slow and full "reindex".
|
||||
|
||||
See the raspiblitz script `./config.scripts/network.reindex.sh` or the REAPIR menu to start these processes.
|
||||
See the raspiblitz script `./config.scripts/network.reindex.sh` or the REPAIR menu to start these processes.
|
||||
|
||||
### Why is my "final sync" taking so long?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user