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

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?

 

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

Guy

Error::: PLL stuck:ffffffff asic(4/255) LOOP:127 (Initial freq), 3000
Nov 11 02:33:35 miner local1.warn minergate[1019]: Critical: ASIC ERROR PLL on address 4/255
Nov 11 02:33:35 miner local1.warn minergate[1019]: Discovered stuck PLL 7000001

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.

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.

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.

Try disabling the problematic ASICs, then wait a few hours or a few days, and try to reenable the ASICs again. You can add a few long power-off cycles as well. That seems to have worked for most of our machines that have had issues with 2.5.7. Hit me up on Skype (jtoomim) if you want me to take a look at it.

Still having issues with mine.  I'm thing 2.5.7 might have damaged my Asics its super unstable.  Right now I have it reset to factory setting at 70% fan.  When I try to bump up the fan to my normal
80% the problems get worse : constant cgminer restarts asics going into fault loop.  ugh this is not good.

Ditto as well ... but I don't think this problem ever showed on the SP10s, it's a SP30/31 thing and maybe now the SP20. (Stand to be corrected if I'm wrong).

SP10 ... solid as a rock!

ditto. still the world's best miner

I've got one of the first SP10's ever made and no ASIC dropouts.

How common is it for these ASIC loops to drop off or need to be disabled?  Essentially that is reducing your mining power....  Expected lifespan?  Do we even know?

Some ASICs can't be activated again. Is this the main sha256 chip that is affected, or a different hardware failure?