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

MyRig

donator

Activity: 792

Merit: 510

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.

Quote from: dannygroove on April 23, 2016, 10:24:27 AM

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

sr. member

Activity: 546

Merit: 253

Quote from: dannygroove on April 23, 2016, 10:24:27 AM

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.

dannygroove

sr. member

Activity: 306

Merit: 250

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.

Mr.paul

newbie

Activity: 21

Merit: 0

Quote from: OgNasty on April 22, 2016, 11:39:06 PM

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.

Bicknellski

hero member

Activity: 924

Merit: 1000

Happy with recent purchase of S7s and one power supply.

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

OgNasty

donator

Activity: 4760

Merit: 4323

Leading Crypto Sports Betting & Casino Platform

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

Cyper_BLC

sr. member

Activity: 490

Merit: 270

Reverse Engineer

Quote from: lanfeusst on April 22, 2016, 12:39:15 PM

Quote from: Cyper_BLC on April 22, 2016, 09:53:11 AM

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 Sad

latest version is not handle 6 hashboards.
I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works. Sad

any ideas ?
i am not linux guy i cant figured out. Sad

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 [email protected]

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
------------------------- Wink

always ok

newer version firmware has this code like that, allways disabled Angry

like not.you said. Wink

   # 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...

not.you

legendary

Activity: 1726

Merit: 1018

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@ as shown below

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

lanfeusst

full member

Activity: 190

Merit: 100

Quote from: not.you on April 22, 2016, 01:50:00 PM

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

legendary

Activity: 1726

Merit: 1018

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

full member

Activity: 190

Merit: 100

Quote from: not.you on April 22, 2016, 01:11:24 PM

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

legendary

Activity: 1726

Merit: 1018

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

full member

Activity: 190

Merit: 100

Quote from: Cyper_BLC on April 22, 2016, 09:53:11 AM

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 Sad

latest version is not handle 6 hashboards.
I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works. Sad

any ideas ?
i am not linux guy i cant figured out. Sad

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 [email protected]

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

legendary

Activity: 1726

Merit: 1018

Quote from: Cyper_BLC on April 22, 2016, 09:53:11 AM

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 Sad

latest version is not handle 6 hashboards.
I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works. Sad

any ideas ?
i am not linux guy i cant figured out. Sad

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?

Cyper_BLC

sr. member

Activity: 490

Merit: 270

Reverse Engineer

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 Sad

latest version is not handle 6 hashboards.
I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works. Sad

any ideas ?
i am not linux guy i cant figured out. Sad

not.you

legendary

Activity: 1726

Merit: 1018

Quote from: notlist3d on April 19, 2016, 01:33:17 PM

Quote from: HerbPean on April 19, 2016, 12:56:42 PM

Quote from: carlosmnk on April 19, 2016, 12:50:33 PM

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.

bitcoinbarron

member

Activity: 68

Merit: 10