HashFast Sierra's Owners Thread

[kevin911]

so I have received my sierra but at least once or twice a day it zombies   and doesn't kick back in until I restart cgminer
does anyone know why this happens?

Are you overclocking it (too much)?

clock 590, current hashrate of 1.22TH/s, temp 77'c 0.79v
and i have to restart cgminer twice, first time it just hangs then second time it kicks in straight away

[1715111863]

1715111863

[1715111863]

1715111863

[1715111863]

1715111863

[1715111863]

1715111863

[-ck]

so I have received my sierra but at least once or twice a day it zombies  and doesn't kick back in until I restart cgminer
does anyone know why this happens?

Are you overclocking it (too much)?

clock 590, current hashrate of 1.22TH/s, temp 77'c 0.79v

Well if it's dropping out then it's unstable and you're obliged to try it at a lower clock speed.

[kevin911]

so I have received my sierra but at least once or twice a day it zombies  and doesn't kick back in until I restart cgminer
does anyone know why this happens?

Are you overclocking it (too much)?

clock 590, current hashrate of 1.22TH/s, temp 77'c 0.79v

Well if it's dropping out then it's unstable and you're obliged to try it at a lower clock speed.

if i remove --hfa-hash-clock 590 will it clock at its normal clock rate (550) only reason why i over clocked it is cause it barely passes 1TH/s without overclocking

[-ck]

if i remove --hfa-hash-clock 590 will it clock at its normal clock rate (550) only reason why i over clocked it is cause it barely passes 1TH/s without overclocking

Yes I understand why people overclock... but not all hardware is created equal and it's called overclocking for a reason.

[kevin911]

if i remove --hfa-hash-clock 590 will it clock at its normal clock rate (550) only reason why i over clocked it is cause it barely passes 1TH/s without overclocking

Yes I understand why people overclock... but not all hardware is created equal and it's called overclocking for a reason.

but in reality i shouldn't have to overclock as it should be hashing at 1.2 TH/s minimum?

[solarion]

In a perfect world yes. It's not ck's fault though.

Are you seeing squelching messages in the cgminer output?

[kevin911]

In a perfect world yes. It's not ck's fault though.

Are you seeing squelching messages in the cgminer output?

i didn't say it was ck's fault, im just asking if there's a solution to this problem if anyone else has come across it as well.
I have been told to use a program called cgwatcher to monitor cgminer & if it zombies it will auto restart cgminer. haven't tested that theory yet, but before i do i thought i would ask if there was any other solution.
When you say squelching messages, what do you mean? i think the only message i have seen is something to do with no response from head then it say's zombie, sorry i didn't really pay much attention, was just concerned the sierra had knocked off & i rapidly restarted everything to get it back up and running

[kevin911]

ok, this is what cgminer says
HFS 0: Failed to reset after write failure, disabling
HFS 0 failure, disabling!
HFS 0: Failed to get data associated with header
USB init, open device failed, err -12, you need to install a WinUSB driver for - HFA device 2:2-i1
See README.txt file included for help
hashfast detect (2:2) failed to initialise (incorrect device?)

has anyone come across this before?

[solarion]

In a perfect world yes. It's not ck's fault though.

Are you seeing squelching messages in the cgminer output?

i didn't say it was ck's fault, im just asking if there's a solution to this problem if anyone else has come across it as well.
I have been told to use a program called cgwatcher to monitor cgminer & if it zombies it will auto restart cgminer. haven't tested that theory yet, but before i do i thought i would ask if there was any other solution.
When you say squelching messages, what do you mean? i think the only message i have seen is something to do with no response from head then it say's zombie, sorry i didn't really pay much attention, was just concerned the sierra had knocked off & i rapidly restarted everything to get it back up and running

It seems that when the miner is pushed too far, specific cores are "squelched". At least that is the message that cgminer reports. I've not seen one in some while now.

Mine is running comfortably at 604 and has been for a few weeks averaging 1.261Th during that time. I've converted to a .conf file, but the original .bat file simply had this preceding pool information:

"cgminer.exe --hfa-hash-clock 604 --hfa-fan 85"

Your temps seem to be under control, so it seems like you just got a bit of a dud.

Edit: windows + cgminer requires zadig.

[kevin911]

In a perfect world yes. It's not ck's fault though.

Are you seeing squelching messages in the cgminer output?

i didn't say it was ck's fault, im just asking if there's a solution to this problem if anyone else has come across it as well.
I have been told to use a program called cgwatcher to monitor cgminer & if it zombies it will auto restart cgminer. haven't tested that theory yet, but before i do i thought i would ask if there was any other solution.
When you say squelching messages, what do you mean? i think the only message i have seen is something to do with no response from head then it say's zombie, sorry i didn't really pay much attention, was just concerned the sierra had knocked off & i rapidly restarted everything to get it back up and running

It seems that when the miner is pushed too far, specific cores are "squelched". At least that is the message that cgminer reports. I've not seen one in some while now.

Mine is running comfortably at 604 and has been for a few weeks averaging 1.261Th during that time. I've converted to a .conf file, but the original .bat file simply had this preceding pool information:

"cgminer.exe --hfa-hash-clock 604 --hfa-fan 85"

Your temps seem to be under control, so it seems like you just got a bit of a dud.

ok thank you for your help, do you think running it in linux will make a difference? and il try the .conf file setup as well.
I don't know why i expected any different from hashfast, waited this long and got a dud lol
il also test each board to see if i can locate it down to one board that seems to be causing the issue.
again, thanks for the info, at least now i know its something to do with the sierra

[QuiveringGibbage]

but in reality i shouldn't have to overclock as it should be hashing at 1.2 TH/s minimum?

in reality, BTC H/w manufacturers tent to estimate the product's hashing speeds and power consumptions. Real world figures can differ dramatically.

My Sierra was stable on 604Mhz and hashing ~1.3THs, but once I took it apart. I could get it to about 1.4THs. Each board behaves differently. See http://imgur.com/a/94wo7#28 for my last screen shot of cgminer and pics of my Sierra. You will notice different clock speed for each board in the Sierra.

Here's a snap shot of cgminer at the time of posting:

Code:

 cgminer version 4.3.3 - Started: [2014-05-15 17:29:56]
----------------------------------------------------------------------------------------------------
 (5s):787.5G (1m):1.207T (5m):1.309T (15m):1.332T (avg):1.469Th/s
 A:17328394  R:20517  HW:17106  WU:20522.3/m | ST: 5  SS: 0  NB: 97  LW: 20093194  GF: 0  RF: 0
 Connected to us.ozco.in diff 461 with stratum as user quiveringgibbage.larry
 Block: 4200d5e2...  Diff:8.85G  Started: [09:02:45]  Best share: 58.2M
----------------------------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: HFB AL      : 550MHz  75C  10% 0.79V  | 102.6G / 429.1Gh/s WU: 5994.9/m A:5058818 R:5550 HW:14752
 1: HFB KEN     : 656MHz  85C  48% 0.78V  | 299.2G / 484.7Gh/s WU: 6771.5/m A:5711371 R:6063 HW: 1529
 2: HFB ROBERTA : 666MHz  85C  72% 0.78V  | 453.3G / 555.2Gh/s WU: 7755.9/m A:6558205 R:8904 HW:  825
----------------------------------------------------------------------------------------------------
 [2014-05-16 09:02:58] Accepted 41b0b091 Diff 998/461 HFB 0 pool 0

While i was tuning the boards to find their max. stable hashing rate, cgminer occasionally gets ZOMBIEs and doesn't recover. But once I lay off the OCing, they can hash stable and if one should fail, cgminer tents to be able to recover it automatically after 60 secs of 0 share submitted.

Hash wild and Hash Fast,
QG

[kevin911]

but in reality i shouldn't have to overclock as it should be hashing at 1.2 TH/s minimum?

While i was tuning the boards to find their max. stable hashing rate, cgminer occasionally gets ZOMBIEs and doesn't recover. But once I lay off the OCing, they can hash stable and if one should fail, cgminer tents to be able to recover it automatically after 60 secs of 0 share submitted.

Interesting to know, i don't think i waited 60 seconds to find out if it would auto kick in.
also, are you running cgminer in linux? if so, which one would you recommend or doesn't it really matter?
also, is the sierra being damaged in anyway by setting the clock rate to 590? as i thought i read somewhere 612 was a sweet spot, i didn't fancy pushing it that far.

[aasl]

HF seems to submit a bankrupt request:
http://ia902509.us.archive.org/13/items/gov.uscourts.canb.522575/gov.uscourts.canb.522575.1.0.pdf

[-ck]

HF seems to submit a bankrupt request:
http://ia902509.us.archive.org/13/items/gov.uscourts.canb.522575/gov.uscourts.canb.522575.1.0.pdf

You read it wrong. That's someone else demanding HF bankrupts.

[Minor Miner]

HF seems to submit a bankrupt request:
http://ia902509.us.archive.org/13/items/gov.uscourts.canb.522575/gov.uscourts.canb.522575.1.0.pdf

You read it wrong. That's someone else demanding HF bankrupts.

yes.   the people they owe money to and who HF has been ignoring.   In every country in the world their are laws about ignoring people that you owe money to.   and in most countries in the world there are repercussions against running a company on the funds of others irresponsibly.

[aasl]

HF seems to submit a bankrupt request:
http://ia902509.us.archive.org/13/items/gov.uscourts.canb.522575/gov.uscourts.canb.522575.1.0.pdf

You read it wrong. That's someone else demanding HF bankrupts.

oh... my fault...

[QuiveringGibbage]

Interesting to know, i don't think i waited 60 seconds to find out if it would auto kick in.
also, are you running cgminer in linux? if so, which one would you recommend or doesn't it really matter?
also, is the sierra being damaged in anyway by setting the clock rate to 590? as i thought i read somewhere 612 was a sweet spot, i didn't fancy pushing it that far.

sweet spot differs from chip to chip. i'm not a chip engineer but i presume you could damage any chip if you pumped too much power through it. but i believe ck said he'd spent a lot of time on the cgminer code for HashFast. so i'd say it'd be some sort of fail safe function. ck would have to comment, i haven't read his code. iirc he mentioned 850 was the limit

what i do know from practical experience is that if you hash with too high of a clock rate, the ASIC chip tends to stop hashing and cgminer will automatically lower the MHz after 60sec of no share received from the device.

Cheers,
QG

[padrino]

Looking to purchase a Sierra, if anyone has one they want to part with please write..

[digitizedcurrency2010]

The Ming Rig is crashing . Using Hashfast SIERA with cgminer 3.12.0. It was working fine and in last 5 days have been having the issue below. As Suggested on the thread I have tried the parameters but with little luck. Any Ideas would be appreciated.

cgminer version 3.12.0 - Started: [2014-10-10 10:13:54]
-------------------------------------------------------------------------------
(5s):245.2G (avg):370.2Gh/s | A:4608  R:0  HW:0  WU:5141.9/m
ST: 2  SS: 0  NB: 1  LW: 5701  GF: 0  RF: 0
Connected to stratum.mining.eligius.st diff 128 with stratum as user XX
Block: 1ad0c4c6...  Diff:35G  Started: [10:13:54]  Best share: 3.43K
-------------------------------------------------------------------------------
Pool management  settings Display options Quit
HFS 0:  max104C 0.82V | ZOMBIE/370.2Gh/s | A:4608 R:0 HW:0 WU:5141.9/m
-------------------------------------------------------------------------------
[2014-10-10 10:14:18] Accepted 7bc81b54 Diff 529/128 HFS 0
[2014-10-10 10:14:19] Accepted 5f74e674 Diff 687/128 HFS 0
[2014-10-10 10:14:19] Accepted 01d09177 Diff 141/128 HFS 0
[2014-10-10 10:14:21] Accepted 012d8f4e Diff 217/128 HFS 0
[2014-10-10 10:14:22] Accepted ebe5db27 Diff 278/128 HFS 0
[2014-10-10 10:14:22] Accepted 010ac52b Diff 246/128 HFS 0
[2014-10-10 10:14:23] Accepted b3c11428 Diff 365/128 HFS 0
[2014-10-10 10:14:25] Accepted 01a1d731 Diff 157/128 HFS 0
[2014-10-10 10:14:26] Accepted 55b5b7a4 Diff 765/128 HFS 0
[2014-10-10 10:14:31] Accepted 0130d63b Diff 215/128 HFS 0
[2014-10-10 10:14:33] Accepted b57ade24 Diff 361/128 HFS 0
[2014-10-10 10:14:37] Accepted 574a4f1d Diff 751/128 HFS 0
[2014-10-10 10:14:40] Accepted a2cc1e3b Diff 403/128 HFS 0
[2014-10-10 10:14:42] Accepted e422166f Diff 287/128 HFS 0
[2014-10-10 10:14:42] Accepted d0271d48 Diff 315/128 HFS 0
[2014-10-10 10:14:59] Accepted 01e369ce Diff 136/128 HFS 0
[2014-10-10 10:15:01] HFS 0: Hit overheat temp, throttling!
[2014-10-10 10:15:01] Accepted 13205ba0 Diff 3.43K/128 HFS 0
[2014-10-10 10:15:02] Accepted 5d433a9a Diff 703/128 HFS 0
[2014-10-10 10:15:02] Accepted 4eac85e5 Diff 833/128 HFS 0
[2014-10-10 10:15:05] Accepted 45d0f23d Diff 939/128 HFS 0
[2014-10-10 10:15:05] Accepted 018ec251 Diff 164/128 HFS 0
[2014-10-10 10:15:05] Accepted 01ff1c46 Diff 128/128 HFS 0
[2014-10-10 10:15:13] Accepted 01477790 Diff 200/128 HFS 0
[2014-10-10 10:15:14] Accepted 01157037 Diff 236/128 HFS 0
[2014-10-10 10:15:15] Accepted 01563dab Diff 191/128 HFS 0
[2014-10-10 10:15:16] HFS 0 Thermal overload tripped! Resetting device
[2014-10-10 10:15:16] HFS 0: OP_USB_INIT: Tossing packet, valid but unexpected type 134
[2014-10-10 10:15:16] HFS 0: OP_USB_INIT: Tossing packet, valid but unexpected type 134
[2014-10-10 10:15:16] HFS 0 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE
[2014-10-10 10:15:16] HFS 0 Failed to reset device, killing off thread to allow re-hotplug
[2014-10-10 10:15:16] HFS 0: device disappeared, disabling
[2014-10-10 10:15:16] HFS 0 failure, disabling!
[2014-10-10 10:15:17] Hashfast detect (1:2) failed to initialise (incorrect device?)

[Micky25]

I would downclock or put the rig in a cooler place - and use a newer version of cgminer.