Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 42. (Read 52103 times)

I think I may have figured it out. It appears that the thermal/temp sensor was flopping around inside the case, as in it was just dangling near the bottom, so it wasn't taking proper readings of the temps. I took off the right side panel, and sort of wedge it in as best as possible next to the plate that the CPU heatsink sits on. Not really sure if that is where it goes or not, but so far the miner has been running without issues for a few hours now. I ordered some thermal tape  and plan on taping it into place so that it doesn't start flopping around again.

Anyone have any ideas where exactly the sensor is supposed to be located so I can put it in its proper place?

Hi Everyone. Just received and setup my Apollo Full Node miner. Its running fine, and connected to the pool but the whole OS will freeze after about 45-60 minutes. No mouse control, no keyboard input. The red light on the Apollo is still blinking, but it doesn't connect to the pool anymore, no hashing being reported. The only way to get it back is to flip the switch off, and then flip it back on. It freezes even if the miner is off, and yes its still syncing the blockchain, but if its going to keep freezing even without the miner running its going to take more than 48 hours to sync this blockchain. Its not hot to the touch really, but with the miner on its temp is about 76 C.

Any ideas on why this would be freezing and what can be done to fix it?

Not sure where you are coming up with this, we respond to every email and im looking at our support que right now and there are only 10 outstanding tickets that will probably be answered in the next few hours (and we only have queues after weekends).

So if your definition of non existent support means not answering your immediate question within 10 minutes, then yes we have non existent support and will continue to have non existent support. Im not hiring random support agents from India and driving up costs of our units by 20% to satisfy this urge.

All our support emails are answered by my team that work on the units themselves (including myself) and can actually answer your question, but this means you might not have a response for a few days.


Now in terms of the nodes issues we are not seeing anything on our test systems, nor any widespread outages (my first thought was the ordinals/BRC-20 fiasco causing issues, but even with 1G mempool we have plenty of memory overhead).

Second issue could be if you have a recent system (bought after Nov/Dec last year), we switch to a new controller heatsink and some units were assembled without the heatsink adhesive properly installed. If your node/system is shutting down, or your your MCU temp (the one on the top menu bar) is higher than 85c then this could be the issue. You'll need to remove the side panel the MCU is on and remove the MCU and reseat the heatsink (press down on it hard for at least 10 seconds to make sure the thermal pad is stuck on there well).

Second step if your still having an issue is to reflash your SD card to make sure there is no corruption that could be causing system instability, if your still having node issues email us with two below logs:

take a screenshot of system monitor while the node is still active (preferably after it has started up and synced), you can open a terminal and type htop for this
send log file of bitcoind, its in the Bitcoin folder inside the node drive (debug.log)