|
You should add backup pools to your config, or at least clear out the default pools unless you want to be mining for bitmain when your primary pool goes down.
|
|
|
|
|
You should copy and paste the kernel log (located under the System tab) so we can take a look.
|
|
|
|
|
So you'd say the problem is usually with a fan and not the miner? In my case they are both stock fans, I might swap them out one at a time and see what happens.
|
|
|
|
Any idea why this antminer was showing three fans? Here is what it looked like: Checking fans!get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[2] speed=6120
get fan[4] speed=1800
get fan[2] speed=6120
get fan[4] speed=1800
get fan[2] speed=6120
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6120
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6120
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6120
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6120
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6120
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
get fan[2] speed=6240
get fan[4] speed=1800
get fan[5] speed=1800
Fatal Error: some Fan lost or Fan speed low!
I thought this was rather amusing. I double-checked the miner to make sure it only had two fans, and that they were running at full speeds. A firmware downgrade to April 2017 seemed to bypass the issue. Thoughts? EDIT: The April firmware did not fix the issue, it still lost the fan. The only solution was replacing the bad fan. |
|
|
|
Alright, I will see if bitmain will do a warranty repair. I really appreciate your experience with these issues because otherwise I would be way more clueless  |
|
|
|
Casamentero fue mi pensamiento inicial ... tal vez emparejamiento? No tienes muchas opciones  |
|
|
|
|
¿Estás corriendo en 220v? Deberías copiar el kernel log para que podamos verlo.
|
|
|
|
That error has been exclusively showing up on 1117 firmware machines. The downgrade to the april firmware always fixes it for me.
Thanks! I should have guessed, that did the trick for about 90-95% of them. It seems on a select few the issue still persists, although the kernel log hangs on "Start bmminer ..." instead of giving endless output. Also, what is your preferred method of flashing firmware when you encounter the code 413 - Request Entity Too Large? Is there any other method besides using a microSD card, and how exactly do you put the firmware on the microSD? Do you extract the files first? And what format, is FAT32 sufficient? |
|
|
|
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.pngDisabling 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.jpgIf you still are under warranty you could at least consider sending the miner back to Bitmain for warranty repair. |
|
|
|
If you see the correct hashrate on your pool dashboard, e.g. pool.bitcoin.com shows a scoring hash rate near 14 TH/s, then you are fine. The general consensus regarding discarded shares is that it's a useless stat. As I understand it: - Elapsed: how much time has passed since you have started hashing to pool. It's slightly shorted than the Uptime shown on the System Overview page, which includes boot time
- Utility is the hashrate of your miner times the luck you have had thus far. Over time, luck stabilizes to near 100%. Your utility is close to your hashrate so your miner has had typical luck.
- Work utility is the typical definition of utility as in cgminer. You should have approximately 1 work utility per 72 megahashes. This means that 209k is a good work utility for a 14 TH/s miner
- Your best share is the share that has met the highest difficulty so far. Shares that meet higher difficulties are better. Bitcoin's current difficulty is around 4 trillion right now. If you found a share that exceeded this difficulty you (or your pool) would submit the proof of work and claim the block reward. Pools generally decrease your difficulty (check #DiffA) so that you will find more shares. If your shares exceed the desired difficulty, then you are rewarded, otherwise not. So although higher shares are better, the difficulty check is on a pass/fail basis.
Also, decreasing difficulty does not give you an advantage. Finding twice as many shares at half the difficulty nets you the same reward. Also, if your first pool is alive, you will not mine to your secondary or tertiary pool choices. They are only backups, they do not relate to your discarded shares. I would recommend leaving them blank if you really only want to mine to one pool. Your time elapsed was only 36 minutes even though you did mention you mined for some hours, it is very possible that the bitcoin.com pool did not find a block during this time and thus you were not rewarded for your shares thus far. You can always check the bitcoin cash blockchain to see recent blocks and who they were mined by if the proof of work was submitted by known pools. In the main page (system overview) you can see the file system version, which is the date of your firmware. I assume you probably have the autotune firmware from November 2017. It is not necessary to change your firmware if you are not having problems with your miner. TL;DR You are paid based on the scoring hash rate, determined by your pool. If you are happy with the hashrate shown in your pool dashboard, you should not be concerned greatly with the miner's stats. |
|
|
|
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 |
|
|
|
|
I have seen similar setups and I would say there is no downsides to having those fans blowing straight towards the miner intake fans. Typically I have seen the gable fans all used on the hot side for exhausting hot air, but it should work the way you have it too.
|
|
|
|
|
Sometimes when downgrading the antminer s9 to the april firmware I get the HTML code 413 - Request Entity Too Large.
Is there any way to get around this or is the only solution to use IP Report reset or SD card?
|
|
|
|
I am seeing more and more antminer s9s that will not boot and are stuck in an endless loop of grep bmminer, any suggestions on how to address this issue? https://pastebin.com/BTAzQE7mbmminer not found= 1369 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
bmminer not found= 1387 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
bmminer not found= 1396 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
bmminer not found= 1405 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
bmminer not found= 1414 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
bmminer not found= 1432 root 0:00 grep bmminer
etc... |
|
|
|
|
On warmer days like today, the antminer s9's built-in thermal protection is very useful since it stops miners from running above 128C. Although the vast majority of these miners do stop at 128, the thermal protection doesn't seem to kick in right away when a miner suddenly spikes in temperature. For example, I saw a miner reach 199C and 170000+ HW errors before the protection kicked in. It turns out that a plastic bag had gotten sucked up to one of the miners and completely cut off the intake airflow.
Is there any way to have the thermal check run more often? Otherwise it seems that the only solution would be to have an external monitor that would check the temperature frequently and stop the miner from hashing above 125C or so.
|
|
|
|
They fixed freq does not offer the option edit or choose the freq. it is exactly set to 650...so how did you manage to set 660.xx???
You can set the freq in cgi-bin/minerAdvanced.cgi. The default (with the 650M fw) is 650.00M, but you could set it at 656.25M or 662.50M etc. as long as you are not concerned about voiding any warranty protection you might have. |
|
|
|
|
Oh well, at least this problem usually has an easy fix, although it is strange that the issue seems to be with neither the fans nor the controller board...
One thing I would try, since you seem to only be detecting one fan, is to boot up with the front fan unplugged and then boot up with the back fan unplugged to see which one is not being detected. The fact that you mentioned that the boot is hanging on "Checking fans!" indicates that perhaps neither fan is being detected. Out of curiosity, have you tried a different power supply? Perhaps there was some fault and your psu is now delivering less than 12 volts.
|
|
|
|
|
Show Posts
