- Kernel Log: it keeps records of ANTMINER's operation stages, which serves a way to troubleshoot some common issues.
- How to check the kernel log: after entering the backstage of the miner, click "system" and then find the "kernel log‘’ option.
Common Problems and Solutions
1. Fan Error
If the miner's fan is not working or the fan can't reach the required speed, the kernel log will show sentences as below.
Solution:
a. Ensure the fan connector has been plugged all the way into the socket and there's no damage on the fan cable. (Below pictures are bad socket and bad cable examples)
b. Replace with a good fan to test. If it doesn't solve the problem, replace the control board.
c. Reset the miner to the factory setting.
d. Return the miner to us for repair.
2. EEPROM Error
If the kernel log shows,
Solution:
In most cases, it indicates the hashboard issues. Try to upgrade the firmware or recover the control board by SD card flashing. If it doesn't solve the problem, return the miner for repair.
3. Missing Chips/missing Hashboards
Kernel log examples such as missing chips and missing hashboards can be like
Solution:
a. Missing chips: replace the PSU and ensure the miner is grounded well.
b. Missing hashboard: ensure the cables are good and properly placed.
If the measures above can't solve the problem, return the miner for repair.
4. Read Temp Sensor Failed
Solution:
In most cases, it indicates the hashboard issues. Try to upgrade the firmware or recover the control board by SD card flashing. Replace with a good known PSU to test. If it doesn't solve the problem, return the miner for repair.
5. Overtemp Protection
If the temperature is too high, the miner will stop working and you could find below words in the kernel log:
Read this article for detailed instructions:
https://support.bitmain.com/hc/en-us/articles/360008523893
6. Low-temp Protection
Read this article for detailed instructions:
https://support.bitmain.com/hc/en-us/articles/900000125666
Should you have any inquiries, feel free to contact us for assistance.
![]() |
Contact us > |
Comments
0 comments
Article is closed for comments.