Just got my apollo II full node.  The tape on the microsd card I understand for transport but I think it creates issues with card seating in the slot.  I had boot issues until I removed the tape, re seated the card,  then the apollo booted fine.

But here is my issue. Miner started and works fine.  The node started loading and loading fast connected to ethernet with 10 connections.  then about 25% in it crashed.  now I get the error message "Warning: Connection refused.  Your node is not running."

I thought it was the router but then i finally found the debug.log in the bitcoin directory on the nvme drive.  It said my database was corrupted with a write batch wrong count. see below.

2024-09-26T22:34:36Z UpdateTip: new best=000000000000002a66d9c7eb33bad96b675d9a7c4e8ecec6166e9a157152f5df height=233533 version=0x00000002 log2_work=69.887555 tx=16874573 date='2013-04-28T08:24:48Z' progress=0.017003 cache=716.6MiB(5437775txo)
2024-09-26T22:34:36Z UpdateTip: new best=00000000000000bc1bcdf0a8120e78ca915909716d8bb86340060e7ea1f98ed1 height=233534 version=0x00000002 log2_work=69.887606 tx=16874741 date='2013-04-28T08:28:55Z' progress=0.017003 cache=716.6MiB(5437858txo)
2024-09-26T22:34:45Z Fatal LevelDB error: Corruption: WriteBatch has wrong count
2024-09-26T22:34:45Z You can use -debug=leveldb to get more complete diagnostic messages
2024-09-26T22:34:45Z *** System error while flushing: Fatal LevelDB error: Corruption: WriteBatch has wrong count
2024-09-26T22:34:45Z Error: A fatal internal error occurred, see debug.log for details
2024-09-26T22:34:45Z tor: Thread interrupt
2024-09-26T22:34:45Z addcon thread exit
2024-09-26T22:34:45Z torcontrol thread exit
2024-09-26T22:34:45Z opencon thread exit
2024-09-26T22:34:45Z Shutdown: In progress...
2024-09-26T22:34:45Z ERROR: ProcessNewBlock: ActivateBestChain failed (System error while flushing: Fatal LevelDB error: Corruption: WriteBatch has wrong count)
2024-09-26T22:34:45Z net thread exit
2024-09-26T22:34:45Z msghand thread exit
2024-09-26T22:34:45Z UPNP_DeletePortMapping() returned: 0
2024-09-26T22:34:45Z mapport thread exit
2024-09-26T22:34:45Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2024-09-26T22:34:45Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.00s)
2024-09-26T22:34:45Z scheduler thread exit
2024-09-26T22:34:45Z Writing 0 unbroadcast transactions to disk.
2024-09-26T22:34:45Z Dumped mempool: 1.3707e-05s to copy, 0.00195496s to dump
2024-09-26T22:34:45Z Flushed fee estimates to fee_estimates.dat.

multiple restart attempts return the same error
2024-09-26T22:35:36Z Using obfuscation key for /media/nvme/Bitcoin/blocks/index: 0000000000000000
2024-09-26T22:35:37Z ERROR: LoadBlockIndexGuts: failed to read value
2024-09-26T22:35:37Z : Error loading block database.
Please restart with -reindex or -reindex-chainstate to recover.
2024-09-26T22:35:37Z Aborted block database rebuild. Exiting.
2024-09-26T22:35:37Z Shutdown: In progress...
2024-09-26T22:35:37Z scheduler thread exit
2024-09-26T22:35:37Z Flushed fee estimates to fee_estimates.dat.
2024-09-26T22:35:38Z Shutdown: done

Do I need to delete the database and start over? Or can this be recovered?