Quote from: eagleye on November 03, 2024, 02:41:25 AM

Quote from: MegatronOHMICAVT on November 02, 2024, 06:43:40 PM

Quote from: jstefanop on September 16, 2024, 04:31:23 PM

Quote from: cryptocrow on September 16, 2024, 10:21:22 AM

Aha this may work. Lets see, its processing.

screen -dmS node /opt/apolloapi/backend/node/bitcoind -reindex -datadir=/media/nvme/Bitcoin -conf=/opt/apolloapi/backend/node/bitcoin.conf

Yep, next release has a "Reindex node" option before the formate node drive as away to recover the node database without going to the extreme of wiping the drive in case of hard shutdowns etc

Hi fellow Apollo node-runners. Long time follower here with a first time question, possibly on this issue above.

Updating my Apollo BTC MCU2 unit to a 2TB nvme, and also updating to 2.0.5.

Node stops sync and refuses connection, alerting disk space full. Log shown below.

The nvme drive isn't showing up when checking lsblk in command line, but the drive is functioning when the node connects, at least initially.

The -reindex command will allow node to reconnect. And also re-flashed, confirming checksum. But it will refuse connection shortly after all of this.

Would -reindex-chainstate command make a difference here? Maybe the micro SD is damaged in some way?

Please advise if anything looks familiar.

Code:

2024-11-02T02:47:19Z UpdateTip: new best=0000000000000000cfef544b24af88f6552deaea28be61cf96b10d5ccefb576c height=286202 version=0x00000002 log2_work=76.626933 tx=33033093 date='2014-02-16T15:44:31Z' progress=0.032903 cache=434.2MiB(3180596txo)
2024-11-02T02:47:19Z *** Disk space is too low!
2024-11-02T02:47:19Z Error: Disk space is too low!
2024-11-02T02:47:19Z ERROR: SaveBlockToDisk: FindBlockPos failed
2024-11-02T02:47:19Z ERROR: ProcessNewBlock: AcceptBlock FAILED (AcceptBlock: Failed to find position to write new block to disk)
2024-11-02T02:47:19Z tor: Thread interrupt
2024-11-02T02:47:19Z Shutdown: In progress...
2024-11-02T02:47:19Z opencon thread exit
2024-11-02T02:47:19Z torcontrol thread exit
2024-11-02T02:47:19Z addcon thread exit
2024-11-02T02:47:19Z net thread exit
2024-11-02T02:47:19Z UPNP_DeletePortMapping() returned: 0
2024-11-02T02:47:19Z mapport thread exit
2024-11-02T02:47:19Z UpdateTip: new best=0000000000000000860990bd046f2d7635cefc0519aaef94c3251a448e4df5e2 height=286203 version=0x00000002 log2_work=76.627072 tx=33033574 date='2014-02-16T15:49:05Z' progress=0.032904 cache=434.2MiB(3180630txo)
2024-11-02T02:47:19Z msghand thread exit
2024-11-02T02:47:20Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2024-11-02T02:47:21Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.90s)
2024-11-02T02:47:21Z scheduler thread exit
2024-11-02T02:47:21Z Writing 0 unbroadcast transactions to disk.
2024-11-02T02:47:21Z Dumped mempool: 0.00189343s to copy, 0.0098008s to dump
2024-11-02T02:47:21Z Flushed fee estimates to fee_estimates.dat.
2024-11-02T02:48:56Z *** Disk space is too low!
2024-11-02T02:48:56Z Error: Disk space is too low!
2024-11-02T02:48:56Z ForceFlushStateToDisk: failed to flush state (Disk space is too low!)
2024-11-02T02:48:56Z *** Disk space is too low!
2024-11-02T02:48:56Z Error: Disk space is too low!
2024-11-02T02:48:56Z ForceFlushStateToDisk: failed to flush state (Disk space is too low!)
2024-11-02T02:49:03Z Shutdown: done

You need to format the new 2TB drive with the format command in settings. Don't format your old data drive. Just to make sure all is good. I did that with my new drive. Then if you have a usb to pcie adapter, copy your 1TB drive to your new 2TB drive. takes about 45 mins. then shutdown, swap and reboot and it should work fine. THat's my experience. Keep the 1TB as a backup. That's what I have.

I did the reindex-chainstate , took longer. I found it to slow down the process on the raspberry pi. The raspberry cpu isn't fast enough for reindex-chainstate. Also lack of ram slows the process. Seems to actually be quicker to start an IBD after a formatted drive and it is quicker. However, I highly recommend a backup like above. Once my IBD was complete I copied the drive for a backup. I also would backup the nvme drive mid IBD download when I was having problems with the raspberry pi crashing mid download. That made recovery quicker in future crashes. My hardest part was the IBD. Once done my system is now running much better.

I have low trust in the reliability of the included microsd card. The original is possibly a much older 16GB microsd. I purchased a new one cheap and with much higher bandwidth and more memory, Cheapest one I could find. I flashed it and find it more stable than the included card was.

Cool, thank you. Before picking up a USB / pcie adapter I'm trying a cache size increase. That seems to be the size error I keep hitting.

MegatronOHMICAVT

Posts

Merits