Author

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

hero member
Activity: 818
Merit: 1006
It seems some of the newer units have problems if the temperature is too low. Symptoms of this issue are machines that run fine sometimes but will restart every 1-10 minutes when it's cold. Machines with this issue will usually work fine as long as their hashing isn't interrupted, but once they get cold, they have trouble starting up again. In our DC, we have two SP30s that arrived in the last 1 or 2 weeks with Murata PSUs that show this problem around when the intake temperature gets below 15°C.

The issue appears to be related to an integer underflow on an 8-bit (probably unsigned) char used for recording DC2DC temperatures. I'm not certain that this is exactly the case, but it fits the data I've seen so far. I expect this issue will be fixed with a firmware update. If you have a machine that's showing this type of issue, you may want to wait before RMAing it.

If you have a recent unit that seems to stop hashing at night, or has trouble starting up while cold, you may be able to get it to work by (a) reducing the fan speed to about 60 or 70, (b) increasing the ambient temperature temporarily, (c) using echo 1 > /etc/mg_dc2dc_temp_ignore, (d) increasing the starting voltage slighly (I recommend not exceeding 670, or you might fry ASICs or DC2DCs), and/or (e) (if you're feeling adventurous -- this can be dangerous!) blocking part of the intake airflow temporarily until the machine is started. Be very careful when using (d) and (e), as they can destroy your machine if you're not very careful or if your machine has other issues.

Here's a grab from the ASIC stats page on one machine that was showing this problem. Note the 250c-255c temperatures on the DC2DCs as well as the 1-5c temperatures. This was with an intake air temperature of around 12°C. My guess is that the DC2DC temperature probes are inaccurate and measure about 10°C low in this unit, and if the reading goes below 0, it cycles up to 255 instead (uint8).

Code:
Uptime:8 | FPGA ver:32
-----BOARD-0-----
PSU[NEW-MURATA]: 0->0w[0 0 0] (->0w[0 0 0]) (lim=1300) 0c cooling:0/0x0
-----BOARD-1-----
PSU[NEW-MURATA]: 0->0w[0 0 0] (->0w[0 0 0]) (lim=1300) 0c cooling:0/0x0
LOOP[0] ON
 0: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 44W  67A 253c] ASIC:[ 85c  560hz(BL: 560)    0 (E:193) F:0]
 1: DC2DC/1/:[vlt1:646 vlt2:653(DCl:794 Tl:794 Ul:749) 45W  69A 253c] ASIC:[ 85c  560hz(BL: 560)    0 (E:193) F:0]
 2: DC2DC/1/:[vlt1:644 vlt2:653(DCl:794 Tl:794 Ul:749) 42W  65A 251c] ASIC:[ 85c  535hz(BL: 535)    0 (E:193) F:0]
LOOP[1] ON
 3: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 45W  70A 254c] ASIC:[ 85c  575hz(BL: 575)    0 (E:193) F:0]
 4: DC2DC/1/:[vlt1:646 vlt2:653(DCl:794 Tl:794 Ul:749) 44W  67A 255c] ASIC:[ 85c  560hz(BL: 560)    0 (E:193) F:0]
 5: DC2DC/1/:[vlt1:646 vlt2:653(DCl:794 Tl:794 Ul:749) 41W  64A 252c] ASIC:[ 85c  535hz(BL: 535)    0 (E:193) F:0]
LOOP[2] ON
 6: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 46W  71A 255c] ASIC:[ 85c  585hz(BL: 585)    0 (E:193) F:0]
 7: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 43W  66A 255c] ASIC:[ 85c  545hz(BL: 545)    0 (E:193) F:0]
 8: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 39W  61A 252c] ASIC:[ 85c  505hz(BL: 505)    0 (E:192) F:0]
LOOP[3] ON
 9: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 45W  70A 254c] ASIC:[ 85c  585hz(BL: 585)    0 (E:192) F:0]
10: DC2DC/1/:[vlt1:646 vlt2:653(DCl:794 Tl:794 Ul:749) 46W  70A 255c] ASIC:[ 85c  585hz(BL: 585)    0 (E:193) F:0]
11: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 39W  59A 255c] ASIC:[ 85c  500hz(BL: 500)    0 (E:193) F:0]
LOOP[4] ON
12: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 43W  66A   3c] ASIC:[ 85c  560hz(BL: 560)    0 (E:192) F:0]
13: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 45W  69A   4c] ASIC:[ 85c  575hz(BL: 575)    0 (E:193) F:0]
14: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 44W  67A 255c] ASIC:[ 85c  560hz(BL: 560)    0 (E:193) F:0]
LOOP[5] ON
15: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 39W  60A 250c] ASIC:[ 85c  480hz(BL: 480)    0 (E:193) F:0]
16: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 29W  45A 250c] ASIC:[ 85c  360hz(BL: 360)    0 (E:190) F:0]
17: DC2DC/1/:[vlt1:646 vlt2:653(DCl:794 Tl:794 Ul:749) 41W  64A 250c] ASIC:[ 85c  510hz(BL: 510)    0 (E:193) F:0]
LOOP[6] ON
18: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 36W  55A 252c] ASIC:[ 85c  455hz(BL: 455)    0 (E:193) F:0]
19: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 42W  65A 254c] ASIC:[ 85c  530hz(BL: 530)    0 (E:193) F:0]
20: DC2DC/1/:[vlt1:646 vlt2:653(DCl:794 Tl:794 Ul:749) 28W  44A 253c] ASIC:[ 85c  360hz(BL: 360)    0 (E:183) F:0]
LOOP[7] ON
21: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 35W  54A 254c] ASIC:[ 85c  455hz(BL: 455)    0 (E:192) F:0]
22: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 41W  64A 255c] ASIC:[ 85c  520hz(BL: 520)    0 (E:193) F:0]
23: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 42W  65A 253c] ASIC:[ 85c  530hz(BL: 530)    0 (E:193) F:0]
LOOP[8] ON
24: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 41W  63A 254c] ASIC:[ 85c  515hz(BL: 515)    0 (E:193) F:0]
25: DC2DC/1/:[vlt1:650 vlt2:653(DCl:794 Tl:794 Ul:749) 42W  65A 255c] ASIC:[ 85c  530hz(BL: 530)    0 (E:193) F:0]
26: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 40W  61A 255c] ASIC:[ 85c  505hz(BL: 505)    0 (E:193) F:0]
LOOP[9] ON
27: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 43W  67A   4c] ASIC:[ 85c  540hz(BL: 540)    0 (E:193) F:0]
28: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 43W  67A   5c] ASIC:[ 85c  540hz(BL: 540)    0 (E:193) F:0]
29: DC2DC/1/:[vlt1:648 vlt2:653(DCl:794 Tl:794 Ul:749) 46W  71A   1c] ASIC:[ 85c  565hz(BL: 565)    0 (E:193) F:0]
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
It's a month full of holidays, I'm sorry for our slow reply time.
If you don't get a reply from support@ within 72 hours, email again.

Ok I e-mailed two days again and e-mailed yesterday. I will wait until tomorrow and e-mail again Sad
It's holiday from Wednesday ...
newbie
Activity: 36
Merit: 0
It's a month full of holidays, I'm sorry for our slow reply time.
If you don't get a reply from support@ within 72 hours, email again.

Ok I e-mailed two days again and e-mailed yesterday. I will wait until tomorrow and e-mail again Sad
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
It's a month full of holidays, I'm sorry for our slow reply time.
If you don't get a reply from support@ within 72 hours, email again.
newbie
Activity: 36
Merit: 0
It seems I have the same issue as bitcoinpapi. I have e-mailed many times to @sales and have had no reply. It is costing me $500 to send the machine back. I recieved the machine late too. I was expecting it in September and it came first week of October. And when the machine came it was not working. Would I be able to get a refund for this item as I have heard nothing what so ever. Will you take care of the shipping charge if I send the item back? This is one of the three machines. The other two machines are hashing away in a data centre in michagan. Please review and let me know asap Guy as i'm loosing out here and not happy.
hero member
Activity: 728
Merit: 500
Any testing on the October batch, still on track for 6.5 Thash?
legendary
Activity: 915
Merit: 1005
...
I understand my unit might not be RMA until a week or so because of the holidays. All i am asking is to be compensated or be able to start hashing in your data center.
We'll sort it out after the Holliday, on Sunday.

No problem.

Will wait on the reply from SP to sort out the down time. Enjoy the holidays.  
To be clear, it's not part of our SLA or TOS and I'm not promising a compensation here.
I'm not sure we have free machines right now. We usually do RMAs from new machines rolling out of the assembly line if needed.
We'll review the case and decide.

Guy

Guy,

Thank you I understand. Will follow up with SP support.

Enjoy the holidays.

--
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
...
I understand my unit might not be RMA until a week or so because of the holidays. All i am asking is to be compensated or be able to start hashing in your data center.
We'll sort it out after the Holliday, on Sunday.

No problem.

Will wait on the reply from SP to sort out the down time. Enjoy the holidays. 
To be clear, it's not part of our SLA or TOS and I'm not promising a compensation here.
I'm not sure we have free machines right now. We usually do RMAs from new machines rolling out of the assembly line if needed.
We'll review the case and decide.

Guy
legendary
Activity: 915
Merit: 1005
...
I understand my unit might not be RMA until a week or so because of the holidays. All i am asking is to be compensated or be able to start hashing in your data center.
We'll sort it out after the Holliday, on Sunday.

No problem.

Will wait on the reply from SP to sort out the down time. Enjoy the holidays. 
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
...
I understand my unit might not be RMA until a week or so because of the holidays. All i am asking is to be compensated or be able to start hashing in your data center.
We'll sort it out after the Holliday, on Sunday.
legendary
Activity: 915
Merit: 1005
The latest that I am on is 2.4.20 . Nothing else comes back for SP when I try to upgrade
My bad, you are right the version is 2.4.20

Cool Talked too early for me. I have no more errors but it is still not stable. Will have to follow up with SP-Teach tomorrow

Guy,

I have not been able to hash since the machine was delivered on Thursday . Can you please look into this ? I might need RMA

--
B
Please contact support@. Please be patient, due to Zvisha's vacation Remo has double the workload.

Guy

Guy,


I understand that it is a holiday. Based on support it has been concluded that the miner delivered was not functional and as a result will need to be RMA. Can I start hashing in your facility or be compensated seeing that this was a September deliver.

I understand my unit might not be RMA until a week or so because of the holidays. All i am asking is to be compensated or be able to start hashing in your data center.
hero member
Activity: 818
Merit: 1006
Would be interesting to know how are these guys removing all the SP generated heat from behind the racks....
https://bitcointalksearch.org/topic/m.9137120

My guess is that they're limited by power availability per rack at that location, not by cooling. Much higher densities are possible. I think I've heard that they do higher densities at one of their other DCs, too.
hero member
Activity: 572
Merit: 500
Would be interesting to know how are these guys removing all the SP generated heat from behind the racks....
https://bitcointalksearch.org/topic/m.9137120

Wall of fans. Literally.

Neat Smiley I hope for their sake that the BTC price increases. That's an awesome setup.
hero member
Activity: 546
Merit: 500
Owner, Minersource.net
Would be interesting to know how are these guys removing all the SP generated heat from behind the racks....
https://bitcointalksearch.org/topic/m.9137120

Wall of fans. Literally.
sr. member
Activity: 314
Merit: 250
Would be interesting to know how are these guys removing all the SP generated heat from behind the racks....
https://bitcointalksearch.org/topic/m.9137120
hero member
Activity: 572
Merit: 500
Nobody can accurately predict whether any miner will ROI, as it depends on largely unknown variables.

By the day, the lyrics here make more sense into the crypto world ..

Quote
Everybody said, boy, don't go any higher,
Uh uh, fuck that, I can do anything,
Never push the limit, and don't play with fire,
Uh uh, fuck that, I can do anything,
Na na na Na na na na Na na na na na na
Wear my heart on my fist take
You by surprise fighter,
Uh uh, fuck that, I can do anything

http://www.azlyrics.com/lyrics/hedley/anything.html
hero member
Activity: 714
Merit: 500

Welcome to the world of no ROI mining. With BTC pricing going down and difficult going up. $10 to $15 is pretty good.
To be fair, difficulty doesn´t seem to be going up (much) at the coming jump.
(And Bitcoin price seems to be recovering again atm.)

Nobody can accurately predict whether any miner will ROI, as it depends on largely unknown variables.

If your power cost is over 15ct/kWh I would strongly suggest you look for a suitable hosting option though.
sr. member
Activity: 407
Merit: 255
Hi Guys,

From the 3 machines I ordered from Spondoolies.. 2 of them are working and one of them doesn't so they've requested to get it sent back to them. I will be loosing out on hashing and paying for shipping the miner back. Is this something spondoolie will compensate for? I did recieve the 3 units pretty late too.. I got them on the 2nd of October when they said it would come in mid-September..

Anyhow I have been mining with the other two machines and have noticed only getting like $10 to $15 per day max combined together for mining with Slush.. Is this usual or should I change to BTC Guild?

Sorry I'm new to mining.. I was expecting these machines could produce upto $50 dollars per day minimum for each machine.

Welcome to the world of no ROI mining. With BTC pricing going down and difficult going up. $10 to $15 is pretty good.
legendary
Activity: 3892
Merit: 4331
yep, one of my hosts (thanks, Jeff!) reported that sp-30 was crashing because miner was initially reading voltage as above 300V when, in fact, it was 246-254V. I guess, this was an extreme case of the same phenomenon. When this Sp-30 was later moved to 208V (otherwise it would not work), miner was initially reading 246V instead.

300V does not sound normal. I usually see +/- 5V of variation. I have occasionally seen anomalous readings (e.g. 180V instead of 245V) that disappear after restarting minergate or rebooting. I have not seen any consistently erroneous readings. If you are frequently seeing high voltage readings that continue after restarting a device, then I would suspect that you either have a faulty power supply or large voltage harmonic distortion on your power line.

Yes, not consistent, but it was getting this reading initially, then shutting itself off in the first few hours of operation. I think Zvi, Remo or someone else or both of these capable engineers looked at it and requested a move to 208V. Anyway, from a practical point of view if this miner sometimes reads 208V as 246V and hashes at OK speed anyway-I am fine with it. I have grown to be very practical about miners. Sometimes I think that they "like" to be left alone. When I was constantly uploading new software, starting and restarting miners after every little turn in the hashing rate, production was always worse then when I just left them hash and let production rate fluctuate as it may. It was true for competitors S1 and S3, but I did not have a chance for this approach to S-30 at home because I don't have power and space for it at home (duh!).

Right now, the most I can wish for is for miners to produce stably and for the damned difficulty rate to stay put or decline (as it did in 2011), but the latter part is just a dream. 

hero member
Activity: 818
Merit: 1006

Then something is wrong with mine Grin

Quote
"summary":[{"Elapsed":4614,"MHSav":950338.47,"MHS5s":979096.86,"MHS1m":961125.07,"MHS5m":966234.23,"MHS15m":960960.48,
"FoundBlocks":0,"Getworks":119,"Accepted":2198,"Rejected":0,"HardwareErrors":0,"Utility":28.58,"Discarded":2623,"Stale":0,
"GetFailures":0,"LocalWork":126900,"RemoteFailures":0,"NetworkBlocks":10,"TotalMH":4384949000,"WorkUtility":3711.76,
"DifficultyAccepted":4789558.9160156,"DifficultyRejected":0,"DifficultyStale":0,"BestShare":18602305,
"DeviceHardware%":0,"DeviceRejected%":0,"PoolRejected%":0,"PoolStale%":0,"Lastgetwork":1412817990}]

Oh, sorry, we don't use those ones. We use stats["STATS"]["ASICstotalrate"]. The stats["summary"]["MHS"...] values are wrong on my machine too.
Jump to: