[ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs

[allinvain]

We'll RMA both units and improve our support procedures with Minersource.

Guy

I have two SP20s hosted with Centerus and they both got damaged during shipping. I passed on the assembly instructions sent by Barbara to the Centerus support crew and they re-assembled the units and checked all the connections, but neither miner is hashing. I'm wondering who do I contact to request an RMA.

Do you guys have skype support as well? I see people mentioning zvisha being available on skype but I take it he's there more for detailed technical support not customer service issues, no?

Since Centerus is not on your hosting partners page I take it nobody from your company keeps in regular touch with their crew, no?

 

[1713403753]

1713403753

[1713403753]

1713403753

[1713403753]

1713403753

[1713403753]

1713403753

[ManeBjorn]

Zvisha does Skype chats just remember he is in Israel so the time zone difference.
 

We'll RMA both units and improve our support procedures with Minersource.

Guy

I have two SP20s hosted with Centerus and they both got damaged during shipping. I passed on the assembly instructions sent by Barbara to the Centerus support crew and they re-assembled the units and checked all the connections, but neither miner is hashing. I'm wondering who do I contact to request an RMA.

Do you guys have skype support as well? I see people mentioning zvisha being available on skype but I take it he's there more for detailed technical support not customer service issues, no?

Since Centerus is not on your hosting partners page I take it nobody from your company keeps in regular touch with their crew, no?

 

[miner454]

We'll RMA both units and improve our support procedures with Minersource.

Guy

Thank you.

[luki19994]

Hi there
i have bought a SP31.
full paid on 26 August Order no 2423
After SP "identified three options for hosting" i choose minersource.
MS recieve my Unit on 31 October
then mailing, waiting , mailing,waiting ,...
on 6.11 i get a mail:
There was a problem at the facility, we have your units and they will go online within the next 18 hours.

waiting , waiting ,
then yesterday i get a contract to fill out , send it back
and now
waiting , waiting

normal that after eleven days my unit is not online ?

thanks for your help

[jtoomim]

MS recieve my Unit on 31 October
then mailing, waiting , mailing,waiting ,...
normal that after eleven days my unit is not online ?

You may want to post here instead or as well, as this sounds more like a hosting issue than a Spondoolies issue: https://bitcointalk.org/index.php?topic=622998.new#new

[zvisha]

P.S. We will update next version to power limit of 288W for SP20 and 1275w for SP31, you can change it if you want.

It's really annoying when you do this. We've already tested our SP30s and SP31s and found the PSU limits that work best for each machine. In the past, when firmware changes these settings, we haven't had records of which machines were using which settings and have had to go back and figure them out again from scratch. Not fun. You have more machines deployed successfully with PSU limits higher than 1275W than you have shipping out right now. Overwriting old settings is more disruptive than leaving them be.

Also, 1275W sounds very low.

I am in agreement here. Having to retune 50+ machines every firmware update gets very tedious.

I am talking about the default settings.
The change will only effect new machines and machines where users never changed the "/etc/mg_custom_mode*" file (not fan, not limits).
Even then you can write a one-liner script that will "touch /etc/mg_custom_*"  on every machine.

Do you guys see a problem with that?

[zvisha]

Version 2.5.12 became the official, 2.5.6 removed and 2.5.13 is the latest experimental.
2.5.12 - different handling of BIST and Murata flow - improves stability.
2.5.13 - sets default (after factory reset) values to 1275/288 in SP3x/SP2x. Redirection bug fixed. Handling of ambient temperatures lower then 0c added.

 

[zvisha]

Zvisha does Skype chats just remember he is in Israel so the time zone difference.
 

We'll RMA both units and improve our support procedures with Minersource.

Guy

I have two SP20s hosted with Centerus and they both got damaged during shipping. I passed on the assembly instructions sent by Barbara to the Centerus support crew and they re-assembled the units and checked all the connections, but neither miner is hashing. I'm wondering who do I contact to request an RMA.

Do you guys have skype support as well? I see people mentioning zvisha being available on skype but I take it he's there more for detailed technical support not customer service issues, no?

Since Centerus is not on your hosting partners page I take it nobody from your company keeps in regular touch with their crew, no?

 

I have Skype in my phone, so I am available 100%, but sometimes I sleep. 
Supporting thousands of miners as a side job in my free time is getting ridiculously time consuming, so we are now hiring people for customer support, to handle PSU configuration and discovery and disablement of ASICs damaged in shipment.

[luki19994]

Thanks
Will do

[allinvain]

Zvisha does Skype chats just remember he is in Israel so the time zone difference.
 

We'll RMA both units and improve our support procedures with Minersource.

Guy

I have two SP20s hosted with Centerus and they both got damaged during shipping. I passed on the assembly instructions sent by Barbara to the Centerus support crew and they re-assembled the units and checked all the connections, but neither miner is hashing. I'm wondering who do I contact to request an RMA.

Do you guys have skype support as well? I see people mentioning zvisha being available on skype but I take it he's there more for detailed technical support not customer service issues, no?

Since Centerus is not on your hosting partners page I take it nobody from your company keeps in regular touch with their crew, no?

 

I have Skype in my phone, so I am available 100%, but sometimes I sleep. 
Supporting thousands of miners as a side job in my free time is getting ridiculously time consuming, so we are now hiring people for customer support, to handle PSU configuration and discovery and disablement of ASICs damaged in shipment.

I guess what I was asking earlier is, what is your skype id. PM it to me please if you do not mind.

[klondike_bar]

new SP20 price! $795
with discount code and shipping of 2 units (3.4TH): 4.5 BTC

7* bitmain S3+ units (3.4 TH) with coupons and shipping this week = 4.7 BTC
4* Bitmain C1 (4TH) with watercooling and shipping this week = 5.3 BTC   (4.64 for 3.5TH)

[klondike_bar]

new SP20 price! $795
 If it was shipping today it would probably be an easy sale, but November 18 is 5 weeks away, or about 3 difficulty increases (~25% cumulative increase?)

It is 11th of November.

5 weeks?

Did I read the email wrong. It did say shipping on the 18th not available for purchase?

Color me confused.

colour me confused - i thought it was october...?

ive edited my post due to this revelation

[RoadStress]

new SP20 price! $795
 If it was shipping today it would probably be an easy sale, but November 18 is 5 weeks away, or about 3 difficulty increases (~25% cumulative increase?)

November, NOT December

November 18 is just one week away!

[Tupsu]

new SP20 price! $795
with discount code and shipping of 2 units (3.4TH): 4.5 BTC

7* bitmain S3+ units (3.4 TH) with coupons and shipping this week = 4.7 BTC
4* Bitmain C1 (4TH) with watercooling and shipping this week = 5.3 BTC   (4.64 for 3.5TH)

wrong math

1x SP20 price! $795+shipping   1700GH/s
2x C1 price   $800+shipping    2000GH/s

Which one is more GH/s ?

[Bicknellski]

new SP20 price! $795
with discount code and shipping of 2 units (3.4TH): 4.5 BTC

7* bitmain S3+ units (3.4 TH) with coupons and shipping this week = 4.7 BTC
4* Bitmain C1 (4TH) with watercooling and shipping this week = 5.3 BTC   (4.64 for 3.5TH)

wrong math

1x SP20 price! $795+shipping   1700GH/s
2x C1 price   $800+shipping    2000GH/s

Which one is more GH/s ?

Which one requires extra components not mentioned in the price?

[jtoomim]

I have had 39 SP30s running 2.5.12 so far for about 12 hours 16 minutes with no apparent issues. If I see no problems with 2.5.12 by next morning, I will probably move the rest of our machines over to it. Otherwise, I will probably move everything back to 2.4.23.

I've had a plethora of "disabled (bist cant start, stuck X)" errors on the remaining 100 or so SP30s we have running 2.5.6 in the mean time. It seems every few hours, I have to restart cgminer on 5% or 10% of our machines to get them back to full hashrate. Very annoying, but so far the issue has always been resolved by restarting minergate.

I've also had several reports of machines on 2.5.6 showing half hashrate at the pool even though I see full hashrate. These issues have always been restarted by a minergate restart.

I saw some much more serious problems on 2.5.7 during the 36 hours we had machines using that version. We saw about 10 machines get "Loop serial failed x" error messages (where x is a loop number, between 0 and 9 inclusive) and fail to start until one or sometimes two ASICs on that loop were disabled. After a few hours, many of these ASICs could be enabled again, but about 25% of the ones that failed are still non-operational. Currently, I think there are 9 ASICs which we lost on 2.5.7 which have not recovered.

It's possible that the potential ASIC-damaging bug in 2.5.7 might still be present in 2.5.12. I haven't seen any indications of it yet, but I also haven't had enough machines running on it for long enough to be certain. On 2.5.7, I saw the loop serial failed ASIC damage thing with about 5% of our machines per day. At that rate, there's only about a 63% chance that I would have seen it if it were present at the same rate in 2.5.12 with 39 machines running half a day.

It is now looking like the issues we've been seeing in our datacenter with the potential ASIC-damaging bug was not related to version 2.5.7 per se, but is instead temperature-related, and we only noticed it now because the temperatures in our DC only recently started getting really close to 0°C. Version 2.5.13 does not appear to fix these issues. Zvi is looking into it further.

The other two bugs were definitely firmware related, so you should still avoid 2.5.6 and 2.5.7.

Findings are still tentative and provisional, and investigation is ongoing.

[Tupsu]

new SP20 price! $795
with discount code and shipping of 2 units (3.4TH): 4.5 BTC

7* bitmain S3+ units (3.4 TH) with coupons and shipping this week = 4.7 BTC
4* Bitmain C1 (4TH) with watercooling and shipping this week = 5.3 BTC   (4.64 for 3.5TH)

wrong math

1x SP20 price! $795+shipping   1700GH/s
2x C1 price   $800+shipping    2000GH/s

Which one is more GH/s ?

Which one requires extra components not mentioned in the price?

Both require a PSU,  2x C1 need 2 liter distilled water+200ml antifreeze. And C1  is silent.

But I look forward to Antminer S5, which goes on sale 15 November

[Guy Corem]

I have had 39 SP30s running 2.5.12 so far for about 12 hours 16 minutes with no apparent issues. If I see no problems with 2.5.12 by next morning, I will probably move the rest of our machines over to it. Otherwise, I will probably move everything back to 2.4.23.

I've had a plethora of "disabled (bist cant start, stuck X)" errors on the remaining 100 or so SP30s we have running 2.5.6 in the mean time. It seems every few hours, I have to restart cgminer on 5% or 10% of our machines to get them back to full hashrate. Very annoying, but so far the issue has always been resolved by restarting minergate.

I've also had several reports of machines on 2.5.6 showing half hashrate at the pool even though I see full hashrate. These issues have always been restarted by a minergate restart.

I saw some much more serious problems on 2.5.7 during the 36 hours we had machines using that version. We saw about 10 machines get "Loop serial failed x" error messages (where x is a loop number, between 0 and 9 inclusive) and fail to start until one or sometimes two ASICs on that loop were disabled. After a few hours, many of these ASICs could be enabled again, but about 25% of the ones that failed are still non-operational. Currently, I think there are 9 ASICs which we lost on 2.5.7 which have not recovered.

It's possible that the potential ASIC-damaging bug in 2.5.7 might still be present in 2.5.12. I haven't seen any indications of it yet, but I also haven't had enough machines running on it for long enough to be certain. On 2.5.7, I saw the loop serial failed ASIC damage thing with about 5% of our machines per day. At that rate, there's only about a 63% chance that I would have seen it if it were present at the same rate in 2.5.12 with 39 machines running half a day.

It is now looking like the issues we've been seeing in our datacenter with the potential ASIC-damaging bug was not related to version 2.5.7 per se, but is instead temperature-related, and we only noticed it now because the temperatures in our DC only recently started getting really close to 0°C. Version 2.5.13 does not appear to fix these issues. Zvi is looking into it further.

The other two bugs were definitely firmware related, so you should still avoid 2.5.6 and 2.5.7.

Findings are still tentative and provisional, and investigation is ongoing.

Jtoomim, thank you for helping debug firmware issues we'll have problem recreating in Isarel
Also for keeping the miners in top condition.

Guy

[Biodom]

I have had 39 SP30s running 2.5.12 so far for about 12 hours 16 minutes with no apparent issues. If I see no problems with 2.5.12 by next morning, I will probably move the rest of our machines over to it. Otherwise, I will probably move everything back to 2.4.23.

I've had a plethora of "disabled (bist cant start, stuck X)" errors on the remaining 100 or so SP30s we have running 2.5.6 in the mean time. It seems every few hours, I have to restart cgminer on 5% or 10% of our machines to get them back to full hashrate. Very annoying, but so far the issue has always been resolved by restarting minergate.

I've also had several reports of machines on 2.5.6 showing half hashrate at the pool even though I see full hashrate. These issues have always been restarted by a minergate restart.

I saw some much more serious problems on 2.5.7 during the 36 hours we had machines using that version. We saw about 10 machines get "Loop serial failed x" error messages (where x is a loop number, between 0 and 9 inclusive) and fail to start until one or sometimes two ASICs on that loop were disabled. After a few hours, many of these ASICs could be enabled again, but about 25% of the ones that failed are still non-operational. Currently, I think there are 9 ASICs which we lost on 2.5.7 which have not recovered.

It's possible that the potential ASIC-damaging bug in 2.5.7 might still be present in 2.5.12. I haven't seen any indications of it yet, but I also haven't had enough machines running on it for long enough to be certain. On 2.5.7, I saw the loop serial failed ASIC damage thing with about 5% of our machines per day. At that rate, there's only about a 63% chance that I would have seen it if it were present at the same rate in 2.5.12 with 39 machines running half a day.

It is now looking like the issues we've been seeing in our datacenter with the potential ASIC-damaging bug was not related to version 2.5.7 per se, but is instead temperature-related, and we only noticed it now because the temperatures in our DC only recently started getting really close to 0°C. Version 2.5.13 does not appear to fix these issues. Zvi is looking into it further.

The other two bugs were definitely firmware related, so you should still avoid 2.5.6 and 2.5.7.

Findings are still tentative and provisional, and investigation is ongoing.

Interesting. Did you try NOT to evacuate the heat that miners produce, but instead direct large fans on a stack of miners, so heat is distributed in the warehouse?
This might be a naive question because you certainly have a large density of miners. I am curious because one of my miners is hosted in WA.

[Biffa]

new SP20 price! $795
with discount code and shipping of 2 units (3.4TH): 4.5 BTC

7* bitmain S3+ units (3.4 TH) with coupons and shipping this week = 4.7 BTC
4* Bitmain C1 (4TH) with watercooling and shipping this week = 5.3 BTC   (4.64 for 3.5TH)

wrong math

1x SP20 price! $795+shipping   1700GH/s
2x C1 price   $800+shipping    2000GH/s

Which one is more GH/s ?

Which one requires extra components not mentioned in the price?

Both require a PSU,  2x C1 need 2 liter distilled water+200ml antifreeze. And C1  is silent.

But I look forward to Antminer S5, which goes on sale 15 November

Don't the C1 need pumps and radiators as well?