Bitcoin Forum

Good day,

I have a friend who complained that his S7 always halts and stops responding, so he reboots it a few times a day

So, I have a question for new S7 users: How stable does your Antminer S7 works?

I want to know if other S7 Batch 1 miners perform the same way.

Help me please

Mines are running stready since 2 weeks. (2 units)

One unit required a few soft reboot to get the right hashrate (4.84th)

 My s-7 is rock solid  4810gh at 600 mhz  pointed at f2pool.

temps are 55c

I do not have to reboot.

A big key is the power you supply.  All 9 jacks to my  3 blades are at 11.96 volts under full 1200 watts of draw.

i have an interesting case: miner was stable for 2 weeks at 600 (~4.84), then declined overnight to ~4.6.
Upon soft reboot-back at 4.85 now for 24 hr. All temp stayed pretty much the same, did not check voltage, but it is the same PSU (EVGA 1300 G2).
It very much reminds me of some (probably not all) S3 machines. I had a few that were stable, then periodically declined after 2-3 weeks and required a soft reboot in gui.

Same, I have 2 S3 running 441 for a few hours then after 48+ they drop down to 415-420.

I got one that is rock solid 504GH forever and ever

Mine is getting 4450GH/s @ 550 and the temps are in the high 50's.  I haven't had any stability problems, but mine does appear to be running hotter than others.  At 600 I was seeing temps around 70.

Do you have any M600 or 600M stickers on the hash boards themselves? I think Bitmain is now better screening these boards and applying stickers to "really good" boards.

Nope.  No stickers.

It could be your power supply is having trouble delivering the power and is causing it to shut down due to heat then restart causing problems with the beaglebone.

What about S7 and p2pool? Have anyone tried to point it to p2pool?

Mine has been pointed at the NastyPool (https://bitcointalk.org/index.php?topic=306611.0) p2pool node for over a week now.  Runs great.

Have you tried it on a standard p2pool node?

NastyPool (https://bitcointalk.org/index.php?topic=306611.0) is a standard p2pool node.  Any developed code is done outside of p2pool, so our node is 100% default p2pool.

My batch 1 is running stable for 22 days at 4.85

Hate to resurrect an old thread, but I just bought one of the latest batch S7s. it had the old firmware from October but I left it as is for about 2-3 weeks now. It intermittently becomes unreachable on the network and stops hashing, or at least I assume it isn't hashing since the pool doesn't recognize my worker anymore, and I can't reach it via web interface. So, I obviously cannot soft reboot since I cannot get into the web GUI. A hard reboot gets everything back in order as it is supposed to though. I upgraded to the latest Firmware, but it seems to make the issue much more frequent. I have the latest Firmware from the BitmainTech site, which states

S7 Firmware - 700M, 4.73th/s miner MD5: 69248149D96B022620DF000AA9F3D615

Has anyone else come up with this issue? My suspicion is intermittent loss of internet and it goes into a closed loop state, but doesn't ever pick up the network again? This is just my theory.


Also can someone explain what the differences between the firmwares are? Why are some rated at different frequencies for different expected Hashrates? Is there any issue if we use the wrong firmware on the wrong batch of miners? How can you tell which is right for which?

I have two issues which might explain your observations:

1) speed decline - I am observing speed decline during random time window - sometime sooner, sometime later. Always high CPU usage - over 1.5, after restart CPU usage drops below 1.0 so script watching CPU usage and auto restart can solve this issue

2) freeze of Antminer - it is since Ant S5 version, if hashboard stops working the miner freezes after some time. It becomes completely unresponsible. Only way is to check frequently and reboot ant before it freeyes. It can freeze in 30 minutes after hash board failure, but never allow hashing with faulty board more than few hours. This is in case of "-----" status chips. If S7 hash board is unpowered, few minutes later it changes status from "-----" to "ooooo" even it is not hashing. I can't say that freezing S7 is the same way like S5, but I think we sould look this way.

THANKS! not sure if it is doing the same thing as the S5s did.

Do you have a instructional walkthrough on this AutoRestart Script watching CPU?

also does anyone have a restart script and how to apply to restart the S7 on a time schedule?

You can't easily mod Ant's firmware, but you can use ssh login to control the miner. For automatic reboots you can use watcher like M's miner monitor which can do triggered actions.

I didn't think you could SSH into the newer miners, I will see if I can find something about this Ms Miner Monitor, do you have a link handy?

Here you go: https://bitcointalk.org/index.php?topic=596178.0

That is the M's monitor he is talking about. It can do a lot "M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner"

Their is a problem with the cgminer on the s7. The same thing that wasn't fixed on the s5. So restarts are going to be necessary at some point. Bitmain should address these errors but they are greed and hardhead so i doubt that this will be the case any time soon. If you are having problems get a hold of them and ask them to upgrade cgminer,

If you haven't already, set the fan speed manually.  That seems to help stability A LOT in many cases!