[ Test mode ] Ordering is currently disabled
CIPHERON
All posts

OperationPublished by Cipheron

Reading logs – the most common error messages on Antminers and Whatsminers

Antminers report errors as text in the kernel log, Whatsminers as numbered codes. The most common messages from both manufacturers, what they mean and what you check first.

A miner that is not hashing almost always says why. With Bitmain it is in the log as text, with MicroBT as a number in the interface.

Where to look

  • Antminer: in the web interface under the kernel log. Read from the bottom; the last lines before the stop are the ones that count.
  • Whatsminer: in the web interface and in WhatsMinerTool as an error code.

Save the log before you restart. After the restart it has been overwritten.

Antminer

ERROR_FAN_LOST. A fan is missing, has stopped or is turning too slowly. The miner does not hash, to protect the chips. Check the connectors and fans, and replace the affected one. If the message remains, Bitmain names the control board as the next cause.

ERROR_TEMP_TOO_HIGH. The temperature is above the limit. Check the intake air, dust in the heatsinks and the fans. If only one board is affected while the others run normally, the fault is on that board. Do not restart until the cause has been fixed: Bitmain expressly prohibits repeated restarts at high temperature.

fail to read pic temp. The PIC chip of a hashboard is not responding. Bitmain advises cross-swapping the cables and reflashing the firmware. If the message remains, the board has to go in for repair.

ERROR_POWER_LOST. The voltage is not right or the power supply has shut down. Check the input voltage, cables, distribution and whether the power supply matches the model.

only find 0 asic or a chip count that is too low. The board is not detected, or only partly. Reseat the data cable between the control board and the board, swap it for the one from another board and watch whether the fault moves with the cable or with the board. If the log finds only some of the chips, Bitmain advises not restarting again and having the board repaired.

ERROR_SOC_INIT: soc init failed. Initialisation was aborted. In Bitmain's examples, the line comes directly after the message about the chip count. So read the line before it: the cause is then on the hashboard.

Whatsminer

The codes are arranged in groups. In the hashboard codes from 300 to 599, the last digit identifies slot 0, 1 or 2.

  • 110: Speed error on the intake fan. Check the connector, replace the fan.
  • 200: No power supply found. Check the connection between power supply and control board, update the firmware.
  • 206: Input voltage too low. Measure the connection and the voltage under load.
  • 350 to 352: Temperature protection of a hashboard. Check the intake air and heatsinks.
  • 530 to 532: Hashboard not found. Check the connection to the board.
  • 600: Ambient temperature too high. The intake air is too warm, the ventilation is not sufficient. MicroBT requires below 35 °C in normal operation.
  • 2010: No pool is reachable. This is not a hardware fault. Check the network and pool settings.

The order of troubleshooting

The same message can have several causes. Go from the simple to the expensive:

  1. Network and pool, if the unit is running but not submitting anything.
  2. Power: voltage, cables, connectors.
  3. Cooling: intake air, dust, fans.
  4. Cables in the unit: data cables and busbars of the boards.
  5. Firmware: reset to the factory version.
  6. Board or power supply, only once everything else has been ruled out.

Only ever change one thing and then restart. Otherwise you do not know what helped.

When to stop

If the warranty is still running, troubleshooting ends before the unit is opened. Reseating cables and replacing fans is fine; anything beyond that belongs in a repair ticket with the manufacturer. The saved log is the most important attachment for it.

Sources

As of October 2026. Wording and codes differ depending on the model and firmware version.

0 Items in cart→