Antminer S9 good hasboards but not hashing!

[Morescratch]

I have several S9's running with good hashboard status but the GH/S(RT) is "0.0000" for every board. When I reboot they start hashing but quickly fall back to "0.0000". The chips are running hot at 90+. Any ideas on what is going on? Could it be network?

[1715433891]

1715433891

[1715433891]

1715433891

[1715433891]

1715433891

[ccgllc]

Not the network.  I see this occasionally in my S9 farm as well.

You can try different firmware.  If you brave and stupid (like me), you can try the fixed frequency firmware as a last resort.  So far, I have not bricked anything doing that, and once in awhile it helps, but your mileage may vary.

Basically you have a card that is failing.  The trick is to see if you can find some firmware that bypasses whatever is going wrong.

Good luck, and welcome to the world of shitty, but cheap, S9s.  I have personally sworn off of them, after buying about 150, and only buy Avalons now when I can catch a good sale.

[Morescratch]

Actually, looking at the kernel log I see that the temperature is too high! Bummer. Any idea on why this particular machine might be experiencing this? I have many other machines on the same rack and they are all running at "normal" (e.g. 70-80 degrees).

Code:

Fatal Error: Temperature is too high!
do read_temp_func once...
do check_asic_reg 0x08

get RT hashrate from Chain[5]: (asic index start from 1-63)

get RT hashrate from Chain[6]: (asic index start from 1-63)

get RT hashrate from Chain[7]: (asic index start from 1-63)
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=30
read failed, old value: Chain[5] Chip[62] local Temp=91
read failed on Chain[5] Chip[62] middle Temp old value:102
Done read temp on Chain[5]
do read temp on Chain[6]
Chain[6] Chip[62] TempTypeID=55 middle offset=27
read failed, old value: Chain[6] Chip[62] local Temp=87
read failed on Chain[6] Chip[62] middle Temp old value:98
Done read temp on Chain[6]
do read temp on Chain[7]
Chain[7] Chip[62] TempTypeID=55 middle offset=29
read failed, old value: Chain[7] Chip[62] local Temp=84
read failed on Chain[7] Chip[62] middle Temp old value:93
Done read temp on Chain[7]
set FAN speed according to: temp_highest=102 temp_top1[PWM_T]=102 temp_top1[TEMP_POS_LOCAL]=91 temp_change=17 fix_fan_steps=1
set full FAN speed...
FAN PWM: 100
read_temp_func Done!
CRC error counter=0

[ccgllc]

Open it up and see if you have dust, dead moths, or lose heat sinks?

[fanatic26]

It says read failed for gathering temps so I think it is basing things off of the last recorded high temperature. Something weird going on there for sure.

[tim-bc]

On your miner's cgi-bin/minerConfiguration.cgi you could use F12 and find the <fieldset class="cbi-section" id="cbi-bmminer-default" style="display:none"> and <div class="cbi-value" id="temp_over" style="display:none"> lines and remove the display:none attribute to show the checkbox and see if disabling that thermal protectioin temporarily could help you to get the miner running again.

https://i.stack.imgur.com/l8msd.png

[fanatic26]

On your miner's cgi-bin/minerConfiguration.cgi you could use F12 and find the <fieldset class="cbi-section" id="cbi-bmminer-default" style="display:none"> and <div class="cbi-value" id="temp_over" style="display:none"> lines and remove the display:none attribute to show the checkbox and see if disabling that thermal protectioin temporarily could help you to get the miner running again.

https://i.stack.imgur.com/l8msd.png

Disabling thermal protection is a terrible idea. IF it does start hashing above the thermal limit it will shortly catch on fire.

[tim-bc]

On your miner's cgi-bin/minerConfiguration.cgi you could use F12 and find the <fieldset class="cbi-section" id="cbi-bmminer-default" style="display:none"> and <div class="cbi-value" id="temp_over" style="display:none"> lines and remove the display:none attribute to show the checkbox and see if disabling that thermal protectioin temporarily could help you to get the miner running again.

https://i.stack.imgur.com/l8msd.png

Disabling thermal protection is a terrible idea. IF it does start hashing above the thermal limit it will shortly catch on fire.

Good point, you should only use it as a troubleshooting tool in these rare situations, otherwise if you leave it disabled you can start a fire / destroy your miner / void your warranty / etc like this https://i.stack.imgur.com/SQbiz.jpg

If you still are under warranty you could at least consider sending the miner back to Bitmain for warranty repair.