ANTMINER S7 is available at bitmaintech.com with 4.86TH/s, 0.25J/GH

[not.you]

Hi, i have a problem with a miner: it only shows the temp of two boards, the central one is NOT showed. What can i do to fix this??

Thanks!!

If it's mining fine, do nothing. You have a bad a temp sensor I guess. I wouldn't be too worried since you two good sensor ... the unit will detect if it is overheating or not.

I have asked before with bitmain and as long as you have a good sensor they say you should be good.  This goes all the way back to S3 day's they were happy if just one was working, so in your case with 2 you should be fine as even if another failed still have one.

You only really need one for it to shutdown if it get's to hot.  But  I know the feeling getting a new one and seeing one dead my first time I got that I thought was something to worry and it's not.  Your MUCH better off running it then going weeks possibly without a hashing board for a temp sensor (and I don't think they would take a RMA for just temp sensor anyways).

I have a machine that has a board that often reports a zero temp but occasionally it reports some random temp, I have seen numbers from the 30's to 140's.  What sucks is that the miner will not mine if the temp is reported above 90.  If you turn off the checkmark to stop mining above 80 it will indeed mine with a temp between 80 and 90 but there does not appear to be any way to make it mine with a temp reported above 90.  I have poked around in the file system and can't find anything to disable that.  So when it reports a temp above 90 all I can do is power cycle it over and over again until it reports a temp below that.  It usually runs for days without that erroneous temp changing (whatever it is) but every so often it just changes, and if it randomly changes to something above 90 it stops mining.  I don't have a way to remotely power cycle it either so sometimes I have to get in the car and drive down to the miner's location and power cycle it over and over to get it back up and working.  I am thoroughly unimpressed with the S7's both in terms of the price (including the drastic price drops) and the quality.  These look likely to be the first miners I have bought since Butterfly fucking labs that will not even break even.

[Cyper_BLC]

my 3 b1 S7 miners goes to silence yesterday, they can reachable but dont hashing, cgminer cant start hashing.
i tried nearly everything 1 solution is flash new firmware and go. but i am using 6hashboards latest version is not handle 6 hashboards.
I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works.
any ideas ?
i am not linux guy i cant figured out.

[not.you]

my 3 b1 S7 miners goes to silence yesterday, they can reachable but dont hashing, cgminer cant start hashing.
i tried nearly everything 1 solution is flash new firmware and go. but i am using 6hashboards latest version is not handle 6 hashboards.
I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works.
any ideas ?
i am not linux guy i cant figured out.

Are you saying you had 3 miners all stop working at the same time?  If so that doesn't sound like a problem with the miners, it sounds like a network problem.

Do you have backup pools configured?  Do the pools show alive or dead?

[lanfeusst]

my 3 b1 S7 miners goes to silence yesterday, they can reachable but dont hashing, cgminer cant start hashing.
i tried nearly everything 1 solution is flash new firmware and go. but i am using 6hashboards latest version is not handle 6 hashboards.
I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works.
any ideas ?
i am not linux guy i cant figured out.

I had the same problem today and some days in the past also.

When you start or restart cgminer the cgminer.sh script (/etc/init.d/cgminer.sh) checks that the connectivity to 114.114.114.114 is up.
I guess it is a one of bitmain ip.
Today this IP (114.114.114.114) is down, so all of Bitmain gear (S3, S4, S5, and S7) will refuse to restart cgminer if you restart the miner or change your configuration.
If 114.114.114.114 is not up, the cgminer.sh script exits and does not start cgminer.
To fix the problem there are 3 possibilities:
1) Wait for 114.114.114.114 to get back up => Seems unacceptable to me.
2) Upgrade the firmware to a newer version

3)  Fix the script and restart cgminer.sh
To do that :

3.1)Connect to your miner by ssh
Replace 192.168.0.170 with the IP of your miner

Code:

ssh root@192.168.0.170

3.2)Edit /etc/init.d/cgminer.sh and comment out 3 lines from line 35 to 37:

Code:

vi /etc/init.d/cgminer.sh

Code:

#if [ $network_ok -eq 0 ];then
#    return
#fi

If you don't know how to use vi :
http://www.tutorialspoint.com/unix/unix-vi-editor.htm

3.3) Then restart cgminer with :

Code:

/etc/init.d/cgminer.sh restart

Warning :
You will have to redo the same modification if you reboot !
To avoid that, do after fixing cgminer.sh:

Code:

cp /etc/init.d/cgminer.sh /config/cgminer_fix.sh

And then if you reboot you only need to do :

Code:

cp /config/cgminer_fix.sh /etc/init.d/cgminer.sh
/etc/init.d/cgminer.sh restart

[not.you]

I restarted both of my S5's a couple of hours ago without issue.  114.114.114.114 is apparently a DNS server in china.  It may indeed be down since it is not responding to DNS queries from me but I am on the outside of the great firewall so maybe that is normal?  I have all of my miners set with static IP's and 8.8.8.8 for DNS.

[lanfeusst]

I restarted both of my S5's a couple of hours ago without issue.  114.114.114.114 is apparently a DNS server in china.  It may indeed be down since it is not responding to DNS queries from me but I am on the outside of the great firewall so maybe that is normal?  I have all of my miners set with static IP's and 8.8.8.8 for DNS.

The exact original code in cgminer.sh is

Code:

network_ok=`ping -c 1 114.114.114.114 | grep " 0% packet loss" | wc -l`
if [ $network_ok -eq 0 ];then
    return
fi

So without a doubt, if the miner can't ping it, it won't start cgminer, it does not depend on which DNS you use. Maybe the S5 doesn't use the same IP, but I thought it would. (I have had the problem with S5 in the past but I don't have S5 to check anymore)

[not.you]

This is what I see in my S5.

Code:

do_start() {
        # gpio1_16 = 48 = net check LED
        if [ ! -e /sys/class/gpio/gpio48 ]; then
                echo 48 > /sys/class/gpio/export
        fi
        echo low > /sys/class/gpio/gpio48/direction

        gateway=$(route -n | grep 'UG[ \t]' | awk '{print $2}')
        if [ x"" == x"$gateway" ]; then
                gateway="192.168.1.1"
        fi
        if [ "`ping -w 1 -c 1 $gateway | grep "100%" >/dev/null`" ]; then
                prs=1
                echo "$gateway is Not reachable"
        else
            prs=0
                echo "$gateway is reachable"
        fi
        #ping $gateway -W1 -c1 & > /dev/null
        #prs=$?
        if [ $prs = "0" ]; then
                echo heartbeat > /sys/class/leds/beaglebone:green:usr3/trigger
                echo 1 > /sys/class/gpio/gpio48/value
        else
                echo none > /sys/class/leds/beaglebone:green:usr3/trigger
                return
        fi
        sleep 5s

..and so on...

Looks like it only checks for the gateway.  I'll check out an S7 in a second.

[lanfeusst]

This is what I see in my S5.

Code:

do_start() {
        # gpio1_16 = 48 = net check LED
        if [ ! -e /sys/class/gpio/gpio48 ]; then
                echo 48 > /sys/class/gpio/export
        fi
        echo low > /sys/class/gpio/gpio48/direction

        gateway=$(route -n | grep 'UG[ \t]' | awk '{print $2}')
        if [ x"" == x"$gateway" ]; then
                gateway="192.168.1.1"
        fi
        if [ "`ping -w 1 -c 1 $gateway | grep "100%" >/dev/null`" ]; then
                prs=1
                echo "$gateway is Not reachable"
        else
            prs=0
                echo "$gateway is reachable"
        fi
        #ping $gateway -W1 -c1 & > /dev/null
        #prs=$?
        if [ $prs = "0" ]; then
                echo heartbeat > /sys/class/leds/beaglebone:green:usr3/trigger
                echo 1 > /sys/class/gpio/gpio48/value
        else
                echo none > /sys/class/leds/beaglebone:green:usr3/trigger
                return
        fi
        sleep 5s

..and so on...

Looks like it only checks for the gateway.  I'll check out an S7 in a second.

Interesting.
I guess it has been removed in recent firmware...I have the S7 firmware from october 23

[not.you]

That one above is an S5.  Here is an S7 Batch 8 or 9.  Looks like that bit is commented out:

Code:

     # check network state
        #network_ok=`ping -c 1 114.114.114.114 | grep " 0% packet loss" | wc -l`
        #if [ $network_ok -eq 0 ];then
        #    return
        #fi

        # gpio1_16 = 48 = net check LED
        if [ ! -e /sys/class/gpio/gpio48 ]; then
                echo 48 > /sys/class/gpio/export
        fi
        echo low > /sys/class/gpio/gpio48/direction

        gateway=$(route -n | grep 'UG[ \t]' | awk '{print $2}')
        if [ x"" == x"$gateway" ]; then
                gateway="192.168.1.1"
        fi
        if [ "`ping -w 1 -c 1 $gateway | grep "100%" >/dev/null`" ]; then
                prs=1
                echo "$gateway is Not reachable"
        else
            prs=0
                echo "$gateway is reachable"
        fi
        #ping $gateway -W1 -c1 & > /dev/null
        #prs=$?
        if [ $prs = "0" ]; then
                echo heartbeat > /sys/class/leds/beaglebone:green:usr3/trigger
                echo 1 > /sys/class/gpio/gpio48/value
        else
                echo none > /sys/class/leds/beaglebone:green:usr3/trigger
                return
        fi
        sleep 5s

I have an S7 from batch 3 or 4 (I can't remember which).  I'll take a look at it.  I also just realized that 192.168.1.1 is not the correct gateway on these machines although that address does exist on my network.

Well there it is in the older firmware:

Code:

        network_ok=`ping -c 1 114.114.114.114 | grep " 0% packet loss" | wc -l`
        if [ $network_ok -eq 0 ];then
            return
        fi

        # gpio1_16 = 48 = net check LED
        if [ ! -e /sys/class/gpio/gpio48 ]; then
                echo 48 > /sys/class/gpio/export
        fi
        echo low > /sys/class/gpio/gpio48/direction

        gateway=$(route -n | grep 'UG[ \t]' | awk '{print $2}')
        if [ x"" == x"$gateway" ]; then
                gateway="192.168.1.1"
        fi
        if [ "`ping -w 1 -c 1 $gateway | grep "100%" >/dev/null`" ]; then
                prs=1
                echo "$gateway is Not reachable"
        else
            prs=0
                echo "$gateway is reachable"
        fi
        #ping $gateway -W1 -c1 & > /dev/null

Not commented out.  So maybe a firmware update would be enough to fix the problem for anyone who has it.

EDIT: Just noticed that Cyper_BLC can't use the firmware update because he has the controller controlling extra cards.  Cyper_BLC looks like you can put # symbols in front and comment it out per the instructions from lanfeusst above.  If you are on Windows download Putty to SSH into the miner.

To connect just put in root@<miner IP> as shown below



when it connects, use the password admin
Then use the steps from lanfeusst above.

[Cyper_BLC]

my 3 b1 S7 miners goes to silence yesterday, they can reachable but dont hashing, cgminer cant start hashing.
i tried nearly everything 1 solution is flash new firmware and go. but i am using 6hashboards latest version is not handle 6 hashboards.
I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works.
any ideas ?
i am not linux guy i cant figured out.

I had the same problem today and some days in the past also.

When you start or restart cgminer the cgminer.sh script (/etc/init.d/cgminer.sh) checks that the connectivity to 114.114.114.114 is up.
I guess it is a one of bitmain ip.
Today this IP (114.114.114.114) is down, so all of Bitmain gear (S3, S4, S5, and S7) will refuse to restart cgminer if you restart the miner or change your configuration.
If 114.114.114.114 is not up, the cgminer.sh script exits and does not start cgminer.
To fix the problem there are 3 possibilities:
1) Wait for 114.114.114.114 to get back up => Seems unacceptable to me.
2) Upgrade the firmware to a newer version

3)  Fix the script and restart cgminer.sh
To do that :

3.1)Connect to your miner by ssh
Replace 192.168.0.170 with the IP of your miner

Code:

ssh root@192.168.0.170

3.2)Edit /etc/init.d/cgminer.sh and comment out 3 lines from line 35 to 37:

Code:

vi /etc/init.d/cgminer.sh

Code:

#if [ $network_ok -eq 0 ];then
#    return
#fi

If you don't know how to use vi :
http://www.tutorialspoint.com/unix/unix-vi-editor.htm

3.3) Then restart cgminer with :

Code:

/etc/init.d/cgminer.sh restart

Warning :
You will have to redo the same modification if you reboot !
To avoid that, do after fixing cgminer.sh:

Code:

cp /etc/init.d/cgminer.sh /config/cgminer_fix.sh

And then if you reboot you only need to do :

Code:

cp /config/cgminer_fix.sh /etc/init.d/cgminer.sh
/etc/init.d/cgminer.sh restart

Thank you so much lanfeusst, It works like a charm

i modified like that :
-------------------------This code
network_ok=`ping -c 1 114.114.114.114 | grep " 0% packet loss" | wc -l`
if [ $network_ok -eq 0 ];then
    return
fi
------------------------- Goes to:
network_ok=1
if [ $network_ok -eq 0 ];then
    return
fi
------------------------- always ok


newer version firmware has this code like that, allways disabled   like not.you said.
   # check network state
   #network_ok=`ping -c 1 114.114.114.114 | grep " 0% packet loss" | wc -l`
   #if [ $network_ok -eq 0 ];then
   #    return
   #fi
i hate bitmain...

[OgNasty]

I had an S7 suddenly show as dead.  It was running 10/23 firmware.  Updating to the 12/11 firmware solved the issue.

[Bicknellski]

Happy with recent purchase of S7s and one power supply.

Nice to see you can still rely on Antminer year after year after year.

[Mr.paul]

I had an S7 suddenly show as dead.  It was running 10/23 firmware.  Updating to the 12/11 firmware solved the issue.

mine too, updating new firmware 575 one the ok back.

[dannygroove]

Antminer S7 B10 not connecting to the setup page. Nothing is configurable, miner is inaccesible.

http://imgur.com/yDMsOzb

Someone told me they fixed this in a new firmware update. Is this true? Im afraid to do a firmware update and that my miner will brick.

[Sierra8561]

Antminer S7 B10 not connecting to the setup page. Nothing is configurable, miner is inaccesible.

http://imgur.com/yDMsOzb

Someone told me they fixed this in a new firmware update. Is this true? Im afraid to do a firmware update and that my miner will brick.

All my miners are running the most up to date firmware available for each model. I've never had a problem.

[MyRig]

Can you at least make it to the login page or the initial password screen, then to this main page with blank data?

If so,  you have a few options

1st be to factory reset the S7 with a paperclip.  There is a pin hole next to the Ethernet connector and use a paperclip and press and hold the button for about 10 seconds and let it go and wait for about 30 seconds and then physically reboot the S7.  This may restore it to the factory default setting.

If this does not help, you may want to go find 8gb microSD card, and create a bootable MicroSD card and insert it into the microSD slot of the S7 and power it off and power it back on.  Let the S7 complete the boot process and if possible, let it run as is for about 5 minutes then your Beagle Bone Black may be restored to the factory default setting.

Image and Imaging Tool:
https://bitmaintech.com/support.htm?pid=007201604120945219855QObfk20066C

If none of these works, your Beagle Bone Black or the Control PCB may be damaged.

Antminer S7 B10 not connecting to the setup page. Nothing is configurable, miner is inaccesible.

http://imgur.com/yDMsOzb

Someone told me they fixed this in a new firmware update. Is this true? Im afraid to do a firmware update and that my miner will brick.

[staysecure]

Have one S7 running for 14 days now, excellent performance. Average 4.7 THs at 700 MHz. Buying a few more soon.

[iram66680]

Have one S7 running for 14 days now, excellent performance. Average 4.7 THs at 700 MHz. Buying a few more soon.

How much in those 14 days have you made in bitcoin? I am starting to garner interest in mining, but thought it maybe a lost cause for trying to get bitcoin and might start doing it for an alt coin or even litecoin.
But want to know first what I can get in 2 weeks running one of these as they sell for $700 each as of now.
Thanks if you can answer this simply question of mine. 

[philipma1957]

Can you at least make it to the login page or the initial password screen, then to this main page with blank data?

If so,  you have a few options

1st be to factory reset the S7 with a paperclip.  There is a pin hole next to the Ethernet connector and use a paperclip and press and hold the button for about 10 seconds and let it go and wait for about 30 seconds and then physically reboot the S7.  This may restore it to the factory default setting.

If this does not help, you may want to go find 8gb microSD card, and create a bootable MicroSD card and insert it into the microSD slot of the S7 and power it off and power it back on.  Let the S7 complete the boot process and if possible, let it run as is for about 5 minutes then your Beagle Bone Black may be restored to the factory default setting.

Image and Imaging Tool:
https://bitmaintech.com/support.htm?pid=007201604120945219855QObfk20066C

If none of these works, your Beagle Bone Black or the Control PCB may be damaged.

Antminer S7 B10 not connecting to the setup page. Nothing is configurable, miner is inaccesible.

http://imgur.com/yDMsOzb

Someone told me they fixed this in a new firmware update. Is this true? Im afraid to do a firmware update and that my miner will brick.

Nice to see you return



https://bitcointalk.org/index.php?topic=1430885.msg14645057#msg14645057


https://bitcointalk.org/index.php?topic=1445536.msg14644921#msg14644921


https://bitcointalk.org/index.php?topic=1165628.msg14644846#msg14644846

All April  23rd dates above.


and this is:

A Jan 14th date

 https://bitcointalk.org/index.php?topic=1165628.msg13548650#msg13548650

So you have been gone for 100 days.

A) I hope you stick around and help people with s-7 gear.

B)  please solve my s-7 batch 1 issue  it under preformed and you never sent me any compensation for it.

C) based on the compensation you gave to us at li's group it should be 67 USD.

So send me
67 USD worth of BTC here is my address

 1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje

I have talked to yoshi months ago and sent a lot of emails asking for this money

no money.

I even said send me a coupon when I buy my next s-7

I purchased 17 of them no coupon.

Do not say the 100 dollar coupon counts  as it is not any bigger then the ones sent with out my bad batch 1
Frankly it would need to be a 167 dollar coupon not a 100.

 I don't understand a company like yours .  I gave you 50,000 usd in business  I supported you gear.  At this moment I am trying to help a few people with bad s-7s'

https://bitcointalk.org/index.php?topic=1423701.0


And you blew me off for 67 USD  that is truly dumb on the part of your company. really bad business.

It has reached the point that I wrote some truly nasty posts.

That is not my nature. I rather you fix this issue for me then chase after you and other bitmaintech workers.

[cryptotore]

So, today I rebooted all 6 of my S7 Batch 1 asic's. They had been up for 50 days since last reboot. They where all hashing before reboot.
The thing is, now none of them will hash.

I can't see any of the hashingboards under the "Miner Status" tab.
I've tried changing PSU's.

It's really weird that all of the machines stopped working at the same time.. after a reboot.

What to do? :S Any advice would be appreciated

Edit:

When you start or restart cgminer the cgminer.sh script (/etc/init.d/cgminer.sh) checks that the connectivity to 114.114.114.114 is up.
I guess it is a one of bitmain ip.
Today this IP (114.114.114.114) is down, so all of Bitmain gear (S3, S4, S5, and S7) will refuse to restart cgminer if you restart the miner or change your configuration.
If 114.114.114.114 is not up, the cgminer.sh script exits and does not start cgminer.

Seems like 114.114.114.114 is down.. hopefully this is the problem!

Edit 2:

This was the problem. Upgraded from oct to dec firmware, fixed it.