Topic: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs - page 109. (Read 1260226 times)

I _guess_ it is poor power delivery.  Right now I see it running with 4.2 th/s.

Nevertheless, the issue is that I have only ssh-access to the miner at the moment. In /etc/mnt I see the file "mg_disabled_asics" with the following content:

0:0 1:0 2:0
3:0 4:0 5:0
6:0 7:0 8:0
9:0 10:0 11:0
12:0 13:0 14:0
15:0 16:0 17:0
18:0 19:0 20:0
21:0 22:0 23:0
24:0 25:0 26:0
27:0 28:0 29:0

I assume that it should be possible to disable the ASICs here. Or am I totally wrong? And IF it is possible to disable asics, would "1" mean disabled and "2" removed?

I have one like that where it seems that its only stable once i manually disable at least one asic from the 'trouble loop', and it generally disables 2-3 more for failing BIST, then becomes reasonably stable.

go to settings, and one of the lower categories allows you to DISABLE specific chips. disable 1-2 at a time fromt he trouble loop, as the issue is sometimes a chip and sometimes poor power delivery

One of my SP31 is not behaving very nicely. Actually, it is hashing with a maximum of about 1 Th. I have access via ssh, and looking in the logs, I see the following - well, it asks me to disable "one by one". How can this be done through ssh? Or has anybody an advice what I should do?

Hi. Will you be showing one of your new machines down town tomorrow here in Austin ?

Hello All.

Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 15: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 16: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 17: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 6 !^[[0;0m
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 18: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 19: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 20: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 7 !^[[0;0m
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 21: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 22: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 23: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 8 !^[[0;0m
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 24: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 25: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 26: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 9 !^[[0;0m
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 27: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 28: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Asic disable 29: Loop RT loss - disable us one-by-one to find the bad one
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Testing LOOPs done = ret=20
Mar 28 00:06:14 miner local1.warn minergate[1737]: Critical: Data Timeout on read fffe:70 (1), (problem:20)
Mar 28 00:06:22 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:5^[[0;0mMar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:3^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:4^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:5^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:6^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:7^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:8^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:9^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:10^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:11^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:12^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:13^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mdc2dc i2c error ASIC:14^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 0 !^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 1 !^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 2 !^[[0;0m
Mar 28 00:06:23 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 3 !^[[0;0m
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 4 !^[[0;0m
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 5 !^[[0;0m
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 6 !^[[0;0m
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 7 !^[[0;0m
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 8 !^[[0;0m
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: ^[[31mERROR: Loop failed 9 !^[[0;0m
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: Testing LOOPs done = ret=25
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: ^[[31mBad loop 0 = trying power cycle^[[0;0m
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: PSU restart
Mar 28 00:06:24 miner local1.warn minergate[1737]: Critical: PSU restart
Mar 28 00:06:28 miner local1.warn minergate[1737]: Critical: PSU restart
Mar 28 00:06:28 miner local1.warn minergate[1737]: Critical: PSU restart

LOOP[2] ON TO:0 (w:79)
 4: DC2DC/1/:[vlt1:660 vlt2:664(DCl:794 Tl:664 Ul:727) 12W  18A  87c] ASIC:[ 85c (125c) 770hz(BL: 770)   35 (E:193) F:0 L:0]
 5: DC2DC/1/:[vlt1:724 vlt2:727(DCl:794 Tl:794 Ul:727) 106W 146A  60c] ASIC:[ 85c (125c) 1050hz(BL:1050)   44 (E:193) F:0 L:0]

What is wrong ? That ASIC was all good before tonight ... :-(

then after like 15 minutes ..

LOOP[0] OFF TO:0 (test serial failed)
0: disabled (serial problem)
1: disabled (serial problem)

same behaviour after 2-3 reboot (power off/on)

You are correct.   It's not that we couldn't do a max density air cooled solution.  Spondoolies already does this.   It's that our architecture is designed to be upgradeable.  Some design concessions had to be made.

Water cooling also opens up the hottest parts of the world to mining.  We can easily handle 40c+ ambient air temps.   And have tested to 70c exiting water temps if so desired for industrial waste heat usage.  Higher temps may be possible.   With a serial power design this will easily be achievable.

-Nathan

Ok done these steps on my Ubuntu VM, what would be the next step after ""make deploy"" for installing no-ip to my machine?

Very nice you now have the dev environment for the SPxx, now all that is left is the routine to update the NoIP servers with your ip. NoIP have an api for that here. All you need to do now (in code to include on the SPxx) is obtain the SPxx gateway IP (i.e your internet IP NOT the SPxx IP) and periodically update their servers on where to find you. Theres also an arduino forum discussion on implementing NoIP that may interest you here.

PS. I have to say you can implement that routine above in pearl (or any scripting language the SPxx OS supports) rather than the arduino way, so just provided for the interfacing with NoIP.

Mr. Ho

Thank you Sir and I thank Spondoolies-Tech (Official Chat forum) for giving this community a heads up about your upcoming products.

Why don't we move this discussion to a "Miner Edge" forum and copy/links that are relevant.   

I look forward to what MinerEdge, LLC. is bringing to the table.


P.S. Wish the best in Huston this week @ Blockchain Innovation  ( http://Texasbitcoinconference.com)


  /s/ TuffToad
Louisville, Ky U.S.A

MinerEdge rack mounted system based on RockerBox pictures can be found here http://imgur.com/a/5g0cq

Hello All.

This is the Miner Edge LLC official Bitcointalk user.

Guy,  Will you do the honors of confirming that this is the real Miner Edge.    We emailed earlier about shipping a broken SP35 for serial power testing.

Thanks for the kind words David,

My condolences to your grandfather.  97 is a good run!  

-Nathan

Hello All.

This is the Miner Edge LLC official Bitcointalk user.

Only if you're not designed for it. We've got a 48U rack running 73.5 kW at our datacenter on pure air cooling with no trouble. It has 15 SP35s and 7 SP30/SP31s. The idea that you have to go to water cooling in order to achieve high densities is both expensive and false.

Only if you're not designed for it. We've got a 48U rack running 73.5 kW at our datacenter on pure air cooling with no trouble. It has 15 SP35s and 7 SP30/SP31s. The idea that you have to go to water cooling in order to achieve high densities is both expensive and false.

From our chats with datacenter owners,  the over 3KW of heat that the SP35 puts out often is too much.