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

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

Guy

Guy,

My two SP31 October batches are defective.  My ROI is basically screwed.  Sh*t happens.

The first SP31 never came up with the latest firmware etc.
The second SP31 with the latest firmware ran for a while and now it's basically as good as dead.

Minersource tech support (the colo that is hosting my SP31's) is waiting for Zvisha's reply.  But I got an email fro sptech today saying Zvisha is waiting for Minersource.  We are going in circles.

I really don't want to deal with two dead SP31's.  Minesource has put too much effort trying to get these SP31's online.  I had already purchased two hosting that will not even be used for this.

Could I get authorization to return these two defective SP31's?

Please reply.

Your Loyal and Return Customer.

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

Look in the Events tab. Post what you find.

Try disabling ASICs. First, disable all but one ASIC. See if it starts up. If it does, then try enabling a few more ASICs, then a few more, etc. Eventually, you may be able to isolate one or two ASICs that are causing the trouble.

If you see "Loop serial failed X" messages, then you can start by disabling loop X, then re-enabling those ASICs one by one. If you see that message, you should also let Zvi know (and preferably also me by Skype; my Skype ID is jtoomim).

You're welcome to contact me on Skype if you want more advice. Zvi's rather busy, and I'd be happy to help if I can until he can get his workload under control again.

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.

5 out of 10 SP30's seem to have failed after about 10 hours with the new firmware 2.5.6

Intake air temps have also dropped down to about 5-10c

CGminer status is : Not Running
Minergate is: Running

all loops are showing disabled.

LOOP[0] OFF ((null))
0: disabled ((null))
1: disabled ((null))
2: disabled ((null))

Have tried rebooting and power cycling. do these things not like the cold?

any suggestions?

Thank you for the quick response, much appreciated!

 Jeez you are an idiot

We'll ship replacement SP20 after fixing the package issue next week.

Guy

Yup, I'm facing the exact same issue as you with the warped board. Barbara has also replied to my earlier email which included pictures of the board when I unpacked it saying that they are looking into it. Let's hope they are able to get back with a fix.

Cheers

Hi. I got my miner November 7th. Got it all plugged in and the 2nd board would cause a halt in cgminer. Miner would not hash. Eventually, I disabled all the ASICS on the 2nd board, and the miner would hash with only the first module.

Noticed that the boards sat at an angle inside the case, so I opened it up and re-aligned. The boards are not screwed in or secured with anything except some grooves raised up from the enclosure. Pretty cheap design, which is prone to board shifting if handled rough in transit.

After re-aligning, I manually enabled and disabled each ASIC on board 2, and figured out that ASIC 4 will not work under any voltage, the other ASICs on the board work fine. Getting 1300 GH/s with 7 ASICS...so not too bad at max 225w per module setting. I'll turn up the juice once all the problems have been worked out, hopefully.

Got an e-mail tonight from Barbara saying they will refund 0.12 BTC because the SP20s shipped late. I'm cool with that, so I thanked her and also told her to forward my diagnosis to tech support. Also filed a form for tech support asking for directions as to how to proceed. Requested they send me a replacement board.

I'd rather not ship the whole thing back and lose hashing time. I can do major surgery on just about any electronic device without a problem.

I have an SP10 Dawson also that has been going without a problem for months now. I can't really say I'm impressed with the SP20, because I'm so far pretty underwhelmed.

Firmware is still 2.5.6, not really sure about any other versions. Hopefully they will get all the bugs worked out soon.

I would love one of those as well.
I have a feeling my garage and basement would not sound like an active aircraft hangar. LOL

Not a problem at all. I was just noticing a pattern. Why so angry?

Ignored, a waste of thread space.

So what are you trying to say? That I can't put hardware related questions to Spondoolies in their hardware thread but it's perfectly fine for you troll the AM shareholders thread? Are you an AM shareholder? If not, why are you even posting in that thread?

Do you have a problem with the relevant on-topic question that I asked?

Every time I ask something about AM you come here. I think this is the third time (if I remember correctly) when you do this You are way too predictable.

Nice signature btw.

What's the time-frame for Spondoolies next gen ASIC? Have you taped out yet? When are you guys expecting samples?

Quick look at the thread, I didn't realize the SP35 had been revised down from 6Th to 5.5Th, is another round of compensation in order to cover users that purchased when it was listed at 6Th?

Hi all.
Version 2.5.12 is ready. It solves "low hash rate in pool" for some SP20 having this issue.
For SP30 it works well in our DC, but because it might have done some damage to jtoomim (few ASICs stopped working) - let's wait with the upgrade.
Regards`

UPpdate: updated wording not to cause panic

thx guys!