Honestly, I've had only the issue I mentioned with using the units on the "new" software version on WIFI. I prefer hardwired anyway but had one unit in my "back hall" with no ethernet cable access (I set up an older WIFI router as an "extender" on my network, hardwired the Apollo 1 Node unit to it, zero issues since). I also had to re-install the software once (Apollo 1 unit, early on) so replaced the original sim card with a newer one I had on hand with no issues since. I have one original Apollo Node Unit with two Apollo Miners running on it as well as 2 Apollo 2 Node units each with one Apollo Miner connected. I heat my small home with them and again, have had no issues other than what I've mentioned already. I did follow all of the set-up instructions to the letter, have very good internet service with my own high quality modem and router, and all my electronics plugged into APC Line-R Voltage Regulator units. Wish I could provide more help but would suggest:
*Replace the original sim card with a same size higher quality one (cheap) and re-install official software
*Consider buying a cheapish voltage regulator and use that to protect/ensure the Node Miner is getting clean voltage (and the one's I use act as a surge protectors too; we suffer spikes/minor outages here in the East Tennessee Valley due to storms at times)
*Review and be sure to follow directions for set-up to the letter
*Don't run the miner while downloading the chain
I realize this is all pretty basic but I honestly have had a great experience with these miners and can only suggest what has worked for me. I hope this helps even if just a little. Good luck!
[/quote]
I tried the reindex. It really doesn't work like you think. Better to start over.
Things to consider. Have you monitored the bitcoin log. Theres a command a few pages back explaining how to open a window and watch the bitcoin log live. Sometimes you get errors that points you in the direction of the problems. It will also show you the program is running when you think nothing is going on.
Also check the bitcoind program in the system monitor and watch that run. If it disappears you know the program crashed. Sometimes its better to reboot the system and allowing the node to restart or restarting the node after a reboot. Just restarting the node after a crash may mean strange things might be happening with memory or something and I've seen more problems just restarting the node.
I found that the bitcoind program would crash I reboot the system and it picks up where it left off. A chainstate error does not get fixed by reindexing. A restart and fresh run of bitcoind would usually fix this. This is the database bitcoind writes from the blockchain database as a reference. This chainstate is already rewritten on every reboot and over time with new block data.
One other thing I did was get another pcie memory stick and backup the blockchain during successful downloads after getting to a specific point. As you get later in the download after i think around year 2020 the blockchain data changed, got bigger and each new block took longer to process so the first 3/4 could take 2 days and the last 1/4 takes another 2 days.
Don't use the apollo to do anything else but download the blockchain. no surfing or browsing. I even close the browser windows and monitor remotely. Uses less memory and processing power.
Once you get the IBD, my system is running very well in all modes. ECO, normal and TURBO. Right now I'm in ECO for quiet and running very stable.
A good surge suppressor/noise conditioner is important for the power to the apollo II along with a backup power supply. Crashes have the chance of corrupting the bitcoin database.
[/quote]
Thanks everyone for the help. I have tried most of those things, including having a UPS on the system and trying different NVME drives that people listed here that would work. I finally heard back from futurebit and they said I have the "rare" controller hardware issue and are issuing me a RMA... we'll see how long this takes.