real_tokenMember
Posts: 4 · Reputation: 125
#1Feb 25, 2021, 03:58 PM
Here's a recovery guide using SSH for those times when you can’t access the Web UI.
THE ISSUE
So, after upgrading to Apollo OS v2.1 and changing the miner from Balanced to Turbo mode through the Web UI, some Apollo BTC MCU1 units can get stuck in this endless reboot cycle. You’ll see the Linux login screen pop up for a second (if you’re connected via HDMI), then it just reboots again, which makes it impossible to access the Web UI.
What's going on? The Apollo miner actually checks the power mode from two different places:
The SQLite database at /opt/apolloapi/futurebit.sqlite which the Web UI uses.A plain text file located at /opt/apolloapi/backend/apollo-miner/mode that the miner itself reads when starting up. If the Turbo mode leads to a crash before the system shuts down properly, the mode file might still be set to turbo even if you tried to switch it back. Every time it boots up, the miner starts in Turbo, pulls too much power or crashes, and then reboots over and over, causing this annoying loop.
Which devices are affected? It’s the Apollo BTC MCU1 running Apollo OS v2.x. This has been confirmed with Apollo OS v2.1.
WHAT YOU NEED
You’ll want a computer that’s on the same local network as your Apollo.
A SSH client (Terminal for Mac/Linux, PuTTY or Windows Terminal for Windows).
The local IP address of your Apollo (you can find this in your router’s device list just look for "FutureBit Apollo" or check it out on the HDMI screen during that brief boot).
Default SSH login details:
Username: futurebit
Password: futurebit123