Re: Official FutureBit Apollo II/BTC Software/Image and Support thread

Quote from: eagleye on April 29, 2025, 04:48:31 PM

Quote from: SysIO on April 29, 2025, 10:42:14 AM

Hi, what about this problem? I formatted the ssd three times on my new Apollo 2 to restart the process. There is a repair/recovery procedure to avoid wasting time? Huh

This is a part of debug.log:

2025-04-29T10:02:02Z Synchronizing blockheaders, height: 894449 (~100.00%)
2025-04-29T10:02:03Z New outbound peer connected: version: 70016, blocks=894449, peer=1 (outbound-full-relay)
2025-04-29T10:02:03Z No valid UPnP IGDs found
2025-04-29T10:02:04Z UpdateTip: new best=000000000000000000161b3eb86d10c4ca7501c597f01007530c318549e1dde5 height=505892 version=0x20000000 log2_work=87.952195 tx=295081822 date='2018-01-24T14:42:57Z' progress=0.278244 cache=1.2MiB(9206txo)
2025-04-29T10:02:06Z UpdateTip: new best=00000000000000000038dd541c3c5ae0df94f6b606b4caf89f3085aec7417ae3 height=505893 version=0x20000000 log2_work=87.952241 tx=295083361 date='2018-01-24T14:49:42Z' progress=0.278246 cache=2.1MiB(16043txo)
2025-04-29T10:02:07Z UpdateTip: new best=00000000000000000079010c5b9058205c8c646e67765de3c1260be2bf06cea3 height=505894 version=0x20000000 log2_work=87.952287 tx=295085778 date='2018-01-24T15:15:59Z' progress=0.278248 cache=3.5MiB(26303txo)
2025-04-29T10:02:08Z UpdateTip: new best=00000000000000000067ed29ff5a5b8ce33c697a72b2a9db31af3e34afa77a66 height=505895 version=0x20000000 log2_work=87.952334 tx=295087877 date='2018-01-24T15:16:20Z' progress=0.278250 cache=4.6MiB(34864txo)
2025-04-29T10:02:10Z UpdateTip: new best=0000000000000000004464b8ddeda229a7d97f6cc5c7b35612c9cb153c18a270 height=505896 version=0x20000000 log2_work=87.952380 tx=295089051 date='2018-01-24T15:18:16Z' progress=0.278251 cache=5.8MiB(42202txo)
2025-04-29T10:02:11Z UpdateTip: new best=0000000000000000001a3a514a5be70a838d2feffa35338ff22e2c85254ec4fb height=505897 version=0x20000000 log2_work=87.952426 tx=295089825 date='2018-01-24T15:20:04Z' progress=0.278252 cache=6.6MiB(48369txo)
2025-04-29T10:02:11Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb
2025-04-29T10:02:11Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb
2025-04-29T10:02:11Z You can use -debug=leveldb to get more complete diagnostic messages
2025-04-29T10:02:11Z Error: Error reading from database, shutting down.
2025-04-29T10:02:11Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb

Thanks

shutdown and restart the miner. Turn off completely then turn on. you want to reset the system this way. the chainstate will rebuild itself. Just restarting the node may not clear the error. That has been my solution. These chainstate files are temporary and get rewritten on bitcoind restart and when bitcoind flushes the database memory. If the error continues after several attempts then you could have a corrupt database on the nvme and you'll need to format the nvme. It's why I have a backup nvme. Also, when you restart the apollo bitcoind will take several minutes rewriting the chainstate. You'll see the cpu usage running 100% or close to it as it rebuilds the chainstate and verifies the database. If you interrupt this process by stopping the node you interrupt this process and don't fix the problem. Use the system monitor to look at bitciond running. You'll see cpu usage and disk read/writes as long as that's active bitcoind is running properly.

My apollo II has been running well for months and I've not seen that error again. only during download of IDB. I think it may be power surges or network interruptions that may have caused the problem.

Regarding power surges, you need a good backup power supply with noise suppression. The apollo II power supply seems sensitive to power surges.

It worked again thanks to your reply, many thanks, but now the block counter stop to 785095 for more time and this is the log:

2025-05-01T18:10:51Z UpdateTip: new best=0000000000000000000595c4447aeca726f55be44eee7853e08220533e521d40 height=785094 version=0x200ee000 log2_work=94.116211 tx=823352602 date='2023-04-12T15:33:37Z' progress=0.775759 cache=318.1MiB(2164404txo)
2025-05-01T18:10:52Z UpdateTip: new best=0000000000000000000049af2d495822edb701291ad2264dc8f3921bea2227d3 height=785095 version=0x20400000 log2_work=94.116225 tx=823355666 date='2023-04-12T15:38:24Z' progress=0.775760 cache=318.4MiB(2166945txo)
2025-05-01T18:10:53Z ERROR: ConnectBlock: Consensus::CheckTxInputs: 0f65054cb7fc6f36310edd1805bda844d4c21905a7048996f0df437671966538, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-05-01T18:10:53Z InvalidChainFound: invalid block=000000000000000000035e95d598779668af4fcc8b7d00812d97596c4c30dab2 height=785096 log2_work=94.116238 date=2023-04-12T15:42:49Z
2025-05-01T18:10:53Z InvalidChainFound: current best=0000000000000000000049af2d495822edb701291ad2264dc8f3921bea2227d3 height=785095 log2_work=94.116225 date=2023-04-12T15:38:24Z
2025-05-01T18:10:53Z ERROR: ConnectTip: ConnectBlock 000000000000000000035e95d598779668af4fcc8b7d00812d97596c4c30dab2 failed, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-05-01T18:10:53Z InvalidChainFound: invalid block=00000000000000000003d52ddd60a5c14a419cae4d7f17a955944dba62a90a40 height=785098 log2_work=94.116266 date=2023-04-12T15:51:36Z
2025-05-01T18:10:53Z InvalidChainFound: current best=0000000000000000000049af2d495822edb701291ad2264dc8f3921bea2227d3 height=785095 log2_work=94.116225 date=2023-04-12T15:38:24Z
2025-05-01T18:10:59Z New outbound peer connected: version: 70016, blocks=894767, peer=42 (outbound-full-relay)
2025-05-01T18:12:21Z No valid UPnP IGDs found
2025-05-01T18:15:42Z Flushed fee estimates to fee_estimates.dat.

Power Off and On don't work now Embarrassed