1.
Issue: The miner has no hash rate. One of the hash board’s temperature exceeds 80 degree Celsius.
Reason: A piece of heat sink is loose or dropped off.
Solution: Remove the hash board that exceeds 80 degree Celsius to repair.
Note: If large quantity of hash boards temperature exceeds 80 degree Celsius, please add cooling devices, as the high temperature will ultimately go into the high temperature protection mode and the miner will shut down. Moreover, the miner can easily get defective when working in a high temperature environment.
2.
Issue: The hash rate is good, but there is no temperature shown on the Miner status.
The hash board is easily burnt if there is no temperature shown for monitoring or when the real temperature is very high
Reason: The temperature detector is damaged on one of the hash boards that lead to the other two hash boards to have the issues on temperature display as well.
Solution: Test the 3 hash boards one by one by connecting to the control board and let it run for about 5 minutes, find the faulty hash board with temperature detection problem and ship it back to repair.
3.
Issue: The hash rate is lower than normal. There is an “X” shown on the Miner status.
Reason: The ASIC chip is damaged, which resulted in the loss of some hash rate on the hash board.
Solution: If that hash board can still work well, you can keep and continue to let it work. There is no need to repair it unless the hash board becomes totally defective.
4.
Issue: The hash rate is lower than normal. There are a lot of “X” shown on Miner status
Reason: The chips are damaged, which lead to the entire hash board running abnormally.
Solution: Remove the hash board to repair.
5.
Issue: The hash rate is lower than normal. There are a lot of “-” shown on Miner status
Reason: It may be caused by instability of the PSU voltage or a defective hash board.
Solution: Replace the PSU and control board-hash board 18 pin ribbon cable. If replacing didn't work, please remove the hash board to repair.
6.
Issue: The hash rate is lower than normal. Some chips are lost. The hash rate is only running at 2/3 of the normal.
Reason: Chain scission of chips
Solution: Remove the hash board to repair.
7.
Issue: The miner has no hash rate. There is X.X.X.X shown on the Hardware Version. Hash board cannot be detected. There is no information shown at all on the Miner status interface.
Cause: The firmware of miner is not detected.
Solution: Power off the miner and reset it. Reload the firmware.
8.
Issue: The miner worked great when it was powered. After awhile, there is no hash rate.
Reason: One of the fans is not detected. Miner will work well only when both fans are detected.
Solution: Switch the control board connection between the two fans to find out which one is defective.
9.
Issue: A large number of Antpools surfaced. Hash rate is normal. There is no use resetting the router.
Reason: One of the computers in the network has been infected by virus or malware.
Solution: Find infected computer and remove the virus or malware.
10.
Issue: Miner can’t find IP. Red light flashing; Green light does not blink
- Reason：The Miner is not connected with the Internet.
Solution: Test the Internet cable, connection and the settings of the Internet (DHCP mode is required).
- Reason: The miner program has not started.
Solution: Reset the miner several times.
- Reason: The application of miner is lost.
Solution: Perform control board recovery
11.
Issue: The miner doesn’t work after powering on despite changing the PSU.
- Reason: There is a short circuit inside one of the hash boards.
Solution: Find which hash board is defective. Remove the defective part to repair.
- Reason: Control board failure
Solution: Change the control board
12.
Issue: PSU can’t work when if the PSU fan is running. Miner works well after changing PSU.
Reason: The PSU is defective. The PSU fan is powered by a different output. The defect can’t be judged by whether the fan rotation power is normal.
Solution: Ship back the PSU to repair.
13.
Issue: Miner restores to factory setting after powering off.
Reason：The software in BB board is damaged.
Solution: Perform control board recovery
14.
Issue: Miners work well for several month before it starts to malfunction.
- Reason: The hash boards were corroded by humidity and lots of dust.
Solution: Remove the defective hash boards, dust the miner and reduce air humidity.
- Reason: Large amount of dust, resulting in congestion in the air duct. Heat can’t be dissipated. Catkins are likely to cause congestion in air duct.
Solution: Remove the defective hash boards, dust the miner and add dust elimination.
15.
Issue: The machine is defective when network changed
Reason: Due to the network setup, miner can’t find the IP.
Solution: Power off and reset the miner.
16.
Issue: S7 malfunction after running for a while. It runs again after rebooting.
-Reason: Temperature exceeds 80 degree Celsius and miner will automatically shut down.
Solution: Increase the amount of air flow.
- Reason: The PGA in BB board weld badly, which lead to miner’s shut down.
Solution: Remove the BB board to repair.
17.
Issue: PSU can’t work but fan is running. All the indicators are off.
Reason: The control board cannot get power as the power circuit in IO board is damaged.
Solution: Switch the BB Board and IO Board with good miner to troubleshoot the defective parts.
Comments
249 comments
1) according to the official support staff's suggestion, you need to reset first, then upgrade to the newest firmware. but this doesn't help.
2) you should apply the last one.
hope you have more luck than me.
Hi, My L3+ doesn't show any of the symptoms shown above and seems to be working fine has good hash rate, However for the last 2 days i have only been profiting 0.06 LTC in 24 hours
Thats barely $3.72, please advise, I have check and read all questions and answer, I don't seem to hear anybody having a similar problem
[NEED HELP]
I'm having a Antminer S9, i found the IP via Report IP, login to control panel, configure the Static IP, but seems something goes wrong, and i can't login to control panel anymore.
I reset the machine few times, but can't search the IP via Report IP anymore.
Please help me, thanks
@Adam Chow. Try reboot your modem @ router. And try again with the ip reporter.
I have the same issue on my S9 one of the hashing board did not start, I did the following: reset the unit through the pool address, many times until the hashing board start again. This method works fine for me.
Why no hash on 3rd board???????? What should I do????
why is my only hash 2/3 one board not hashing or showing temp?
I suggest to try to reboot the unit many times until the hashing board start normally otherwise you should need to clean the board.
Hello , i have a problem with L3+ , it only detect 3 boards , also in log appear this info:
It's fixeable with upgrade/firmware ? its control board fault ? i need ship the control board ?
Oct 20 23:24:41 (none) local0.notice cgminer[374]: Start A New Asic Response.Chain Id:[0]
Oct 20 23:24:42 (none) local0.notice cgminer[374]: tty_init 1
Oct 20 23:24:42 (none) local0.notice cgminer[374]: Start A New Asic Response.Chain Id:[1]
Oct 20 23:24:42 (none) local0.notice cgminer[374]: tty_init 2
Oct 20 23:24:42 (none) local0.notice cgminer[374]: Start A New Asic Response.Chain Id:[2]
Oct 20 23:24:42 (none) local0.notice cgminer[374]: tty_init 3
Oct 20 23:24:42 (none) local0.notice cgminer[374]: Start A New Asic Response.Chain Id:[3]
Oct 20 23:24:42 (none) local0.notice cgminer[374]: open device over
Oct 20 23:24:42 (none) local0.notice cgminer[374]: send cmd to get chip address
Oct 20 23:24:44 (none) local0.notice cgminer[374]: Chain 0 ASIC 0 !!!
Oct 20 23:24:44 (none) local0.notice cgminer[374]: Chain 1 ASIC 72 !!!
Oct 20 23:24:44 (none) local0.notice cgminer[374]: Chain 2 ASIC 72 !!!
Oct 20 23:24:44 (none) local0.notice cgminer[374]: Chain 3 ASIC 72 !!!
Hi, I have 3 Antminer S9's with hashboards that are not working. This is now a total of 5 boards in 6 months. I could send this back as a warranty claim but I see that all the new machines have a different firmware version not available on the website. I suspect the problem has to do with the temperature sensors. The new software seems to not display one of the sensor readings and has an entry in the kernel log referencing a 'special fix'. So, can anyone tell me where I can get the below version of the firmware. Thanks.
hi Alex, do you mean the firmware S9V2.23 with the date of July 21, 2017 will fix it?
Hi Grand, No not necessarily. Thing is, I have received a couple of newer miners that are running this version of software. In the kernel log there is some wording like -
chain[5] temp offset record: 62,0,0,0,0,0,35,28
chain[5] temp chip I2C addr=0x98
chain[5] has no middle temp, use special fix mode.
chain[6] temp offset record: 62,0,0,0,0,0,35,28
chain[6] temp chip I2C addr=0x98
chain[6] has no middle temp, use special fix mode.
chain[7] temp offset record: 62,0,0,0,0,0,35,28
chain[7] temp chip I2C addr=0x98
chain[7] has no middle temp, use special fix mode.
I was just interested in trying this version on some of my faulty miners. Having said that - since the last blog, a miner running this software has now also lost a hashing board....
Bitmain partner released new special offer as pack x8 today of the Antminer D3 #Dashcoin Miner. Price of $12,599.00 .Order now while stock last
( https://antminer-store.com/product/8x-pack-antminer-d3-8-units-15-0-ghs/ )
Bitmain partner released new special offer as pack x8 today of the Antminer D3 #Dashcoin Miner. Price of $12,599.00 .Order now while stock last
( https://antminer-store.com/product/8x-pack-antminer-d3-8-units-15-0-ghs/ )
S9 14TH S9_V2.37. received couple of days ago.
I worry that I have too many HW errors - 912 for 18 hours. Is it ok for S9? For instance all my L3s working in the same room show much less HW errors and by the way work with less chip temperatures. Please advise, thanks.
I don't think this failure is caused by the temperature sensor or the handler, FYI.
the HW value is a little bit high but is ok, maybe it's just network instability.
Grand thanks for the prompt response. Should I reboot it occasionally to reset HW? if so, how often?
no need to do anything unless your HW rate (the percentage underneath “DiffA”) over 0.03%, in that case, your hash power may be compromised, so, try rebooting and pray
I purchased 3 L3+ four months ago and none is working, My experience as a Bitmain customer feels like a fraud victim.
After a week of techincal service emails (with very delayed responses from bitmain side), I applied the repair ticket and received the controller boards one week after placing the repair ticket. I had to pay taxes again for the delivery, I received older controller board models and plus they were not new, they had scratches.
After installing the new contoller boards and updating the firmware the reult is the same: Each machine works at 0 MH/s. The kernel log shows "Chain 0 ASIC 0", "Chain 1 ASIC 0" and go on for each hashboard. It detects the boards but not the chips.
I placed more tickets but still have no aswer. I called their phone number many times but no one answer, just one time I was able to talk with some one and this person do not did speak english well and it was a meaningless conversation.
Add me to the list of missing hash boards on Antminer S9.
My October batch of S9 came with:
File System Version Thu Sep 21 10:57:49 CST 2017
Logic Version S9_V2.37
The latest Firmware they have to download is:
File System Version Tue Aug 15 11:37:49 CST 2017
Logic Version S9_V2.30
So, they do not even have the latest firmware available for download!
As shown here ( S7 ) , every thing is good, but there is not a hashing power!!
Dear all:
After succesfully been working for about a month, one my two new L3+´s stop hashing and failed to show miner status of the hash boards anymore. All I am reciving is a 0 hash rate on the summary section. Pools section, on the other hand, are perfectly shown but the hashboards status section is collapsed. None of the hashboards can be seen.
I have reboot, reset, updated firmware, switch to static IP several times and none of these actions have been effective in solving this issue. Up to today it´s beed five days the machine stop hashing. What can I do about this? this is quite fursttrating since we have put a lot of effort on buying this equipment. Than you for your help.
Help me please, what can I do ?
Please process my order
BITMAIN Order Paid
Order ID: 0012017111900060
Date: 2017-11-19 01:01:17
Total: 1.39599675 BCH
Payment method: BCH Payment
I'm running a D3 that seems to have a bad middle hash board and since this is the only thread I could find talking about "High HW" I'm going to try and seek help here. After receiving my new D3 I ran it for 1 day and encountered the problem where a board goes all x's and stops mining after less than 1 day. I installed the latest firmware which is supposed to address the failures, but again it will stop mining completely after 10-20 hours. I did a factory reset and now the miner continuously mines with infrequent restarts, but I'm getting a lot of HW errors on the same board that was going down with x's prior to the firmware update.
Here is a screen shot showing 108 HW errors after only running for 29 minutes and only for the middle board.
Is this middle hashing board defective?
Version / Firmware
13 minutes later and now I have 166 HW errors and a DiffA# of 1.4242%. This can't be "normal"...
Any suggestions?
Hi @Scott,
For me high HW is okay rather than missing hashboard =D.
Sometimes there will be XXX, so we need to reboot the miner. If reboot doesn't work then try change PSU.
Lucky in Malaysia we have service center and community for repair Antminer with little cost. Don't need to sent back to Bitmain for warranty.
Good luck.
I agree it just seems excessive that only 1 of my boards is having this many issues. After 16.5 hours, the middle board has now had 4,054 errors and the other two boards 0.
Another strange issues is that the fan will shoot up to 6,200 RPMs for about 15 seconds and then cycle back down to 4,200 RPMs every few minutes.
Is there any documentation defining what each of the values are in the 'Miner Status' chart??
Article is closed for comments.