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

[zvisha]

Hi all,

I just got a 15 unit batch of SP20's approximately 30 hours ago.  I absolutely love these rigs!!!  However, I am running into an issue with one rig.  It says, "LOOP[0] ON TO:0 (w:38)
0: disabled (Asic all engines fail BIST).

I have IBM 2880W PSU's with breakout boards.  All of the others are running well on these IBM 2880W PSU's except for one I had problems connecting to last night [I will deal with it after I finish my new mining closet in the next couple of days].

I have replaced the PCI-e cord in port 1 of the SP20 and I've changed ports with a new cord on the breakout board.  Yet, it still says, "LOOP[0] ON TO:0 (w:38)
0: disabled (Asic all engines fail BIST)."

I was getting too sleepy last night to continue trouble shooting it.  If someone else has had this issue or has something to offer for me to try, please chime in.

Thank you

Nothing to do about this.
The ASIC was damaged in shipment.

[Guy Corem]

I love that sign.
Great work Spondoolies I look forward to reviewing your next gen miners. I also am eagerly looking forward to our interview next week.

Since we had some discussions about gen3 miners I would like to congratulate SP-Tech for their 600 page with a special image:

Same here

[Guy Corem]

Understood.  Looking forward to working with the new miners.  I'll let you know what DHL asks for.  I upgraded home panel to 400A and put in 220v 20A and 30A circuits.  I have 24A safely usable on the 30A circuits (5280W) with the derated PDUs. Do you think I can run (2) SP31s on each of those circuits as long as I underclock them?

What is your order # ?

[raskul]

Since we had some discussions about gen3 miners I would like to congratulate SP-Tech for their 600 page with a special image:

did someone say GEN3?

 

[notey]

4675. Thanks.

Understood.  Looking forward to working with the new miners.  I'll let you know what DHL asks for.  I upgraded home panel to 400A and put in 220v 20A and 30A circuits.  I have 24A safely usable on the 30A circuits (5280W) with the derated PDUs. Do you think I can run (2) SP31s on each of those circuits as long as I underclock them?

What is your order # ?

[Guy Corem]

4675. Thanks.

Understood.  Looking forward to working with the new miners.  I'll let you know what DHL asks for.  I upgraded home panel to 400A and put in 220v 20A and 30A circuits.  I have 24A safely usable on the 30A circuits (5280W) with the derated PDUs. Do you think I can run (2) SP31s on each of those circuits as long as I underclock them?

What is your order # ?

Katya is checking with DHL now.

Edit: We'll reply privately by email.

[Tigggger]

I was part of the group buy ages ago for the SP30, because it failed to live up to the specs that were advertised at the time Spondoolies agreed to either issue coupons or a refund for $944.06.

Because I was confident in SP I decided to go with the coupons, however the pricing on products since then has never been good enough to warrant me purchasing an SP31, I asked in this thread at the time and was told they would be good for any other products for the next 6 months.

Sadly as we know the BTC price collapsed which has meant that even once I have applied the discount I'd essentially be paying money for a machine that loses money (All my SP equipment has been sold because its not profitable to run in the UK, or at my hosts abroad) so needless to say I haven't purchased anything.

As the 6 month period is almost over and Spondoolies have said there is no new hardware imminent, I asked if I could have the refund instead and was suprised that this was refused I must say I wasn't expecting that given how good SP have been with their customers and now I'm stuffed.

Therefore my last hope of salvaging something from this (unless SP want to reconsider) is if someone wants a brand new SP31 shipped direct, I will order it and give you $400 off the price, PM me if interested.

[takagari]

The monitor page seems to be broken, it's reporting really high average hash rates.

Code:

{"Elapsed":64616,"MHSav":2448947.61,"MHS5s":3324640.36,"MHS1m":1755088.42,"MHS5m":1550657.77,"MHS15m":1490862.71

All my SP20s are doing this, thoughts?

[wh00per]

The cgminer averages are calculated with respect to the shares submitted to the pool, the pool difficulty and the time between two consecutive accepted shares. Either you're extremely lucky in the last 30 min or so, or something is wrong with the part accepting your shares. (It can be the "pool speed" recovering after a "slow" interval, on the pool side.)

I can bet all of your SP20 are on the same pool .. right? Try on a different pool with a couple of them for a while.

[takagari]

The cgminer averages are calculated with respect to the shares submitted to the pool, the pool difficulty and the time between two consecutive accepted shares. Either you're extremely lucky in the last 30 min or so, or something is wrong with the part accepting your shares. (It can be the "pool speed" recovering after a "slow" interval, on the pool side.)

I can bet all of your SP20 are on the same pool .. right? Try on a different pool with a couple of them for a while.

I'm using slush, I can see they report properly on the pool, and the miners report normal. all 6 of them do the same thing, and report wrong.

[wh00per]

Yeah .. Slush gives you their version of the average hashing value (over last 10 rounds), cgminer does its own (over 1-5-15 min), based on the share transfers, and the miner itself reports something else based on the ASIC frequencies and count .. in the long run, they agree. sometimes in the short run they don't. It's called variance of the instantaneous readings versus a calculated average (which by the way, is calculated differently at every level - miner, software and pool).

Slush pool says  ..

Why is hashrate reported on my profile incorrect?
Posted by Jan (Support) on 06.12.2013 13:32:11
Hashrate shown in your account is based on statistics of your shares in last 10 rounds. If you started mining just a few hours ago (see user stats), then it may be lower than what your hashrate actually is. It's just informative, it doesn't have any impact on mining or your reward.

[takagari]

Yeah .. Slush gives you their version of the average hashing value (over last 10 rounds), cgminer does its own (over 1-5-15 min), based on the share transfers, and the miner itself reports something else based on the ASIC frequencies and count .. in the long run, they agree. sometimes in the short run they don't. It's called variance of the instantaneous readings versus a calculated average (which by the way, is calculated differently at every level - miner, software and pool).

Slush pool says  ..

Why is hashrate reported on my profile incorrect?
Posted by Jan (Support) on 06.12.2013 13:32:11
Hashrate shown in your account is based on statistics of your shares in last 10 rounds. If you started mining just a few hours ago (see user stats), then it may be lower than what your hashrate actually is. It's just informative, it doesn't have any impact on mining or your reward.

I understand that, it averages out and can appear lower or not accurate.
They have been online for some time now, and one is infact reporting in at 3.4THash, If they were a bit off, I could understand, that's insane.
Is there another output to draw from to get what cgminer is reporting?

[klondike_bar]

Im having issues with a pair of SP10 units that im trying to undervolt for efficiency and slow fans.

at 15% fans, 600mv start, 620mv max, and 750W max, i see initial hashrates arounf 900GH/600W but it quickly has 5-10 chip errors per machine ('xxxxxxxxxxxx' all over the place in the stats tab) and drops to around 750GH/500W

am i tuning something wrong? temps seem fine with the slow fans, and the intake/exhaust is about 20/60

edit: seems that a starting voltage of 610mv eliminates the majority of 'dead' chips.

is scheduling available or planned for implementation in the SP10?

[pekatete]

The cgminer averages are calculated with respect to the shares submitted to the pool, the pool difficulty and the time between two consecutive accepted shares. Either you're extremely lucky in the last 30 min or so, or something is wrong with the part accepting your shares. (It can be the "pool speed" recovering after a "slow" interval, on the pool side.)

I can bet all of your SP20 are on the same pool .. right? Try on a different pool with a couple of them for a while.

I'm using slush, I can see they report properly on the pool, and the miners report normal. all 6 of them do the same thing, and report wrong.

Funny you say that. Slush had an issue earlier today that I noticed too .... for about an hour (could have been longer!), the pool was not automatically setting a diff. One of my S5's was left at diff 32 (the default) a long time, I'd say half an hour to 45 minutes, and was submitting loads of shares (could tell from the accepted shares metric), until I went into the new interface at slush and manually set a diff. A pool sync followed about the time you posted this which again took longer than usual to complete .... that may explain your un-usually high rates.

[Guy Corem]

Congratulations to Olivier Janssens for being elected as a Bitcoin Foundation board member.
Change is coming ...

https://twitter.com/olivierjanss

[RoadStress]

Congratulations to Olivier Janssens for being elected as a Bitcoin Foundation board member.
Change is coming ...

https://twitter.com/olivierjanss

Congratulations also!

[TheRealSteve]

Congratulations indeed, hopefully some of his ideals will percolate through

With relevance to this thread, only fair to provide some partial disclosure: http://www.coindesk.com/spondoolies-tech-5-million-series-b/

[Guy Corem]

Congratulations indeed, hopefully some of his ideals will percolate through

With relevance to this thread, only fair to provide some partial disclosure: http://www.coindesk.com/spondoolies-tech-5-million-series-b/

Indeed.

[zvisha]

Im having issues with a pair of SP10 units that im trying to undervolt for efficiency and slow fans.

at 15% fans, 600mv start, 620mv max, and 750W max, i see initial hashrates arounf 900GH/600W but it quickly has 5-10 chip errors per machine ('xxxxxxxxxxxx' all over the place in the stats tab) and drops to around 750GH/500W

am i tuning something wrong? temps seem fine with the slow fans, and the intake/exhaust is about 20/60

edit: seems that a starting voltage of 610mv eliminates the majority of 'dead' chips.

is scheduling available or planned for implementation in the SP10?

No, but it cab done from cron using ssh.
I hope someone from community can prepare a guide that I will publish.

[klondike_bar]

Im having issues with a pair of SP10 units that im trying to undervolt for efficiency and slow fans.

at 15% fans, 600mv start, 620mv max, and 750W max, i see initial hashrates arounf 900GH/600W but it quickly has 5-10 chip errors per machine ('xxxxxxxxxxxx' all over the place in the stats tab) and drops to around 750GH/500W

am i tuning something wrong? temps seem fine with the slow fans, and the intake/exhaust is about 20/60

edit: seems that a starting voltage of 610mv eliminates the majority of 'dead' chips.

is scheduling available or planned for implementation in the SP10?

No, but it cab done from cron using ssh.
I hope someone from community can prepare a guide that I will publish.

i tried a cronjob with cat /etc/mg_custom_mode_day > /etc/mg_custom_mode && /usr/bin/local/spond-manager restart
and while it changed the mg_custom_mode file, it failed to correctly restart the minergate. any attempts to restart minergate via the ui, ssh, or reboot seemed to not work. same with factory reset (keeping cgminer.conf). a recovery with uSD worked though.

I havent tinkered with an SP10 in some time, so am not sure if what worked fine on the SP3x is a bit different here. not sure if the problems i encountered with minergate failing  to restart are due to a difference in the way the files work. perhaps the next-best solution is either:
cp -rf /etc/mg_custom_mode_day /etc/mg_custom_mode && /usr/bin/local/spond-manager restart
or
cat /etc/mg_custom_mode_day > /etc/mg_custom_mode && reboot