Title: S7 ASIC Failure Post by: Shades01 on January 31, 2016, 02:45:27 AM 3 of my S7 miners have all lost 2 ASIC chains each. This happened about the same time. There was an internet outage earlier yesterday morning. I got them all working and connected again, all 6 of my S7 miners working great. Then about 10 hours later, 3 of mine, the 3 batch 7's I have lost 2 boards each.
I've gone through all of the connectors, everything is seated well. Power supplies have been tested separately, and work fine. They are all running at 625.00M Frequency. System Overview: Miner Type Antminer S7 Hostname antMiner Model GNU/Linux Hardware Version 1.5.3.0 Kernel Version Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014 File System Version Tue Sep 15 16:50:19 CST 2015 Cgminer Version 4.8.0 Uptime 19 Load Average 1.05, 0.87, 0.61 Monitor: Mem: 78060K used, 173112K free, 0K shrd, 0K buff, 39912K cached CPU: 40% usr 30% sys 0% nic 30% idle 0% io 0% irq 0% sirq Load average: 0.76 0.82 0.60 1/75 1840 PID PPID USER STAT VSZ %VSZ %CPU COMMAND 397 396 root S < 168m 68% 61% /usr/bin/cgminer --bitmain-dev /dev/bitmain-asic --bitmain-options 115200:32:8:7:200:0782:0725 --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 8192 --api-listen --default-config /config/cgminer.conf 1839 1838 root R 2148 1% 9% top -b -n 1 400 1 root S 5980 2% 0% /usr/bin/monitor-recobtn /usr/bin/factory_config_reset.sh 356 1 root S 3364 1% 0% /usr/bin/ntpd -p /var/run/ntp.pid -g 372 1 root S 2980 1% 0% /usr/sbin/lighttpd -f /etc/lighttpd.conf 365 1 avahi S 2728 1% 0% avahi-daemon: running [antMiner-10.local] 366 365 avahi S 2728 1% 0% avahi-daemon: chroot helper 396 1 root S 2616 1% 0% {screen} SCREEN -S cgminer -t cgminer -m -d /usr/bin/cgminer --bitmain-dev /dev/bitmain-asic --bitmain-options 115200:32:8:7:200:0782:0725 --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 8192 --api-listen --default-config /config/cgminer.conf 353 1 root S 2272 1% 0% /usr/sbin/dropbear -r /config/dropbear_rsa_host_key -p 22 420 1 root S 2148 1% 0% {miner-m.sh} /bin/sh /sbin/miner-m.sh 419 1 root S 2148 1% 0% {monitorcg} /bin/sh /sbin/monitorcg 339 1 root S 2148 1% 0% udhcpc -b -t 10 -A 10 -x hostname antMiner -i eth0 1838 372 root S 2148 1% 0% /bin/sh /www/pages/cgi-bin/monitor.cgi 1840 1838 root S 2148 1% 0% /bin/sh /www/pages/cgi-bin/monitor.cgi 1262 419 root S 2016 1% 0% sleep 5m 1768 420 root S 2016 1% 0% sleep 1m 417 1 root S 1908 1% 0% /sbin/getty 115200 ttyO0 418 1 root S 1908 1% 0% /sbin/getty 38400 tty1 1 0 root S 1652 1% 0% init [5] 103 1 root S 1640 1% 0% /usr/bin/monitor-ipsig 406 1 root S 1632 1% 0% /usr/bin/test-btn /usr/bin/test.sh 21 2 root RW 0 0% 0% [kworker/u:1] 10 2 root SW 0 0% 0% [rcu_sched] 15 2 root SW 0 0% 0% [kworker/0:1] 11 2 root SW 0 0% 0% [watchdog/0] 3 2 root SW 0 0% 0% [ksoftirqd/0] 2 0 root SW 0 0% 0% [kthreadd] 5 2 root SW< 0 0% 0% [kworker/0:0H] 6 2 root SW 0 0% 0% [kworker/u:0] 7 2 root SW< 0 0% 0% [kworker/u:0H] 8 2 root SW 0 0% 0% [migration/0] 9 2 root SW 0 0% 0% [rcu_bh] 12 2 root SW< 0 0% 0% [khelper] 13 2 root SW 0 0% 0% [kdevtmpfs] 14 2 root SW< 0 0% 0% [netns] 16 2 root SW 0 0% 0% [bdi-default] 17 2 root SW< 0 0% 0% [kintegrityd] 18 2 root SW< 0 0% 0% [kblockd] 19 2 root SW 0 0% 0% [khubd] 20 2 root SW 0 0% 0% [irq/86-44e0b000] 24 2 root SW 0 0% 0% [irq/23-tps65217] 27 2 root SW 0 0% 0% [irq/46-4819c000] 36 2 root SW< 0 0% 0% [rpciod] 38 2 root SW 0 0% 0% [khungtaskd] 39 2 root SW 0 0% 0% [kswapd0] 40 2 root SW 0 0% 0% [fsnotify_mark] 41 2 root SW< 0 0% 0% [nfsiod] 42 2 root SW< 0 0% 0% [crypto] 45 2 root SW< 0 0% 0% [pencrypt] 46 2 root SW< 0 0% 0% [pdecrypt] 53 2 root SW< 0 0% 0% [OMAP UART0] 54 2 root SW 0 0% 0% [spi1] 57 2 root SW 0 0% 0% [spi2] 60 2 root SW< 0 0% 0% [kpsmoused] 61 2 root SW 0 0% 0% [irq/150-mmc0] 73 2 root SW< 0 0% 0% [deferwq] 149 2 root SWN 0 0% 0% [jffs2_gcd_mtd9] 336 2 root SW 0 0% 0% [kworker/0:2] 409 2 root SW< 0 0% 0% [bitmain-asic] 1230 2 root SW 0 0% 0% [flush-mtd-unmap] I can send Kernel logs if that would be useful at all. Here's what all three show: Start Up: http://imgur.com/vrZvxmn After a few minutes: http://imgur.com/9k6c6Uw Any help would be great. Thank you! Title: Re: S7 ASIC Failure Post by: adaseb on January 31, 2016, 02:46:36 AM Check to see if its not the power supply, if it isn't send it back for warranty.
Title: Re: S7 ASIC Failure Post by: RadekG on January 31, 2016, 11:46:00 AM Oh yes, I had the same problem, one board was dead. Two chips overheated and desoldered from PCB. The same syptoms like yours S7. Sent back for RMA, received repaired board.
Title: Re: S7 ASIC Failure Post by: Shades01 on January 31, 2016, 08:09:30 PM Do you remember how long and how much it cost to get the boards back?
Title: Re: S7 ASIC Failure Post by: RadekG on February 02, 2016, 03:26:47 PM I am in EU, I used priority postage which cost about USD15 and my board came back about a month later by UPS.
Title: Re: S7 ASIC Failure Post by: not.you on February 02, 2016, 09:27:52 PM You must have missed the posts about this already. Basically it is a known issue that if the internet goes down the fans do not spin fast enough to cool the boards and they will overheat and fail. This is only an issue on earlier batches (not sure which batch it was finally fixed on) and only if you have the fans set to auto and never updated the firmware. There is firmware that fixes this but it has been pretty well established that setting fans to manual above 60% or so will keep this from happening also.
Title: Re: S7 ASIC Failure Post by: Shades01 on February 03, 2016, 04:07:26 PM My fans have been set to 80% manually since I first turned them off, so that is not the issue.
|