HASHRA - LUNAR SERIES - ASIC SCRYPT MINERS

[jjj0923]

I did upgrade one of my two units last night and it's been running fine but I did have to reboot it after upgrading

ok, cool.  was there any performance or stability boost do you think?

my only observation(and this has not been proven with multiple tests) is that the unit did not need to be restarted multiple times after changing pools, like I've experienced with the stock firmware.

oh and even though it reboots itself after the update - I neede to reboot it a second time because after it's own reboot all I say was this  in the syslog file:

Jun 12 14:18:54 hashracontroller cgminer: Started cgminer 3.1.1
Jun 12 14:18:59 hashracontroller single_ltc_monitor[2201]: Started LTC PRocess waiting 10 seconds to boot cgminer
Jun 12 14:18:59 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:18:59 hashracontroller cgminer: Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 00038d26
Jun 12 14:18:59 hashracontroller cgminer: All devices disabled, cannot mine!
Jun 12 14:19:04 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:09 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:14 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:19 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:24 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:29 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:34 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:39 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:44 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:49 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null

Jeff

The trick for rebooting is, first reboot the miner, and then reboot the pi. The miner has to be reset completely and alive, before connecting the pi to it.

thanks for the insight but how do you do that when your miners are remote - is there a command at the firmware level to reboot the miner?

[davecoin]

If you had 2000 accepted and 200 hardware errors, that means 10% of your hashrate is totally wasted.  That's not good.  Your 14mh/s miner is effectively a 12.6mh/s miner.

The clock speed is down to 310 and I have now 500 Accepted, 0 Rejected, 2 HW

That is amazing.  What pool?  Also, what is your ambient temperature where the miner is located?  I'm wondering if my performance issues are due to the heat in my mining space.

@jjj You can reboot the pi by logging into it user:pi pass:controla, then use the command sudo reboot. 

[jjj0923]

this is really getting rediculous

I had to reboot the pi machine 4 times today to get it our of slow mode.

this machine should have been tested more before it was shipped.

I am really unhappy.

this is really impressive performance from a so called 25 mh miner.

NOT!

pi@hashracontroller:~$ sudo screen -x SCRYPT
(5s):25.54M (avg):4.035Mh/s | A:183  R:5  HW:12  U:182.9/m  WU:6381.4/m         (5s):9.377M (avg):3.668Mh/s | A:196  R:6  HW:13  U:178.1/m  WU:6237.0/m         (5s):3.442M (avg):3.362Mh/s | A:213  R:6  HW:17  U:177.4/m  WU:6276.5/m         (5s):1.263M (avg):3.103Mh/s | A:233  R:6  HW:18  U:179.1/m  WU:6310.4/m         (5s):463.9K (avg):2.881Mh/s | A:247  R:8  HW:21  U:176.3/m  WU:6293.9/m         (5s):170.3K (avg):2.689Mh/s | A:268  R:8  HW:23  U:178.6/m  WU:6364.9/m         (5s):18.19M (avg):4.311Mh/s | A:287  R:8  HW:24  U:179.3/m  WU:6506.9/m         (5s):6.677M (avg):4.058Mh/s | A:305  R:8  HW:25  U:179.3/m  WU:6876.8/m         (5s):2.451M (avg):3.832Mh/s | A:319  R:8  HW:26  U:177.1/m  WU:6992.4/m         (5s):899.9K (avg):3.631Mh/s | A:336  R:8  HW:27  U:176.8/m  WU:7264.2/m         (5s):330.3K (avg):3.449Mh/s | A:355  R:9  HW:27  U:177.4/m  WU:7508.7/m  

[maxzilla]

I did upgrade one of my two units last night and it's been running fine but I did have to reboot it after upgrading

ok, cool.  was there any performance or stability boost do you think?

my only observation(and this has not been proven with multiple tests) is that the unit did not need to be restarted multiple times after changing pools, like I've experienced with the stock firmware.

oh and even though it reboots itself after the update - I neede to reboot it a second time because after it's own reboot all I say was this  in the syslog file:

Jun 12 14:18:54 hashracontroller cgminer: Started cgminer 3.1.1
Jun 12 14:18:59 hashracontroller single_ltc_monitor[2201]: Started LTC PRocess waiting 10 seconds to boot cgminer
Jun 12 14:18:59 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:18:59 hashracontroller cgminer: Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 00038d26
Jun 12 14:18:59 hashracontroller cgminer: All devices disabled, cannot mine!
Jun 12 14:19:04 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:09 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:14 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:19 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:24 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:29 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:34 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:39 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:44 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:49 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null

Jeff

The trick for rebooting is, first reboot the miner, and then reboot the pi. The miner has to be reset completely and alive, before connecting the pi to it.

thanks for the insight but how do you do that when your miners are remote - is there a command at the firmware level to reboot the miner?

Yea that would be difficult. There is no power cycle command from the PI to the miner.

Can you have a remote power switch installed ?
like this one? this one has a web interface
http://www.amazon.com/Managed-Designed-Manufactured-Synaccess-Networks/dp/B0039OZKPE

[jjj0923]

you can't even switch coins without this happening 80% of the time:

and this is with 'updated' firmware - personally like I said earlier - I think the firmware update makes things worse, not better

when are you guys going to get this fixed?

Jun 12 17:42:19 hashracontroller MinerClass log[2083]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:19 hashracontroller single_ltc_monitor[17304]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:24 hashracontroller MinerClass log[2083]: PHP Warning:  socket_connect(): unable to connect [111]: Connection refused in /var/www/class/cgminerclient.class.php on line 20
Jun 12 17:42:24 hashracontroller MinerClass log[2083]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:24 hashracontroller single_ltc_monitor[17304]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:29 hashracontroller MinerClass log[2083]: PHP Warning:  socket_connect(): unable to connect [111]: Connection refused in /var/www/class/cgminerclient.class.php on line 20
Jun 12 17:42:29 hashracontroller MinerClass log[2083]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:29 hashracontroller single_ltc_monitor[17304]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:34 hashracontroller MinerClass log[2083]: PHP Warning:  socket_connect(): unable to connect [111]: Connection refused in /var/www/class/cgminerclient.class.php on line 20
Jun 12 17:42:34 hashracontroller MinerClass log[2083]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:34 hashracontroller single_ltc_monitor[17304]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:39 hashracontroller MinerClass log[2083]: PHP Warning:  socket_connect(): unable to connect [111]: Connection refused in /var/www/class/cgminerclient.class.php on line 20
Jun 12 17:42:39 hashracontroller MinerClass log[2083]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 17:42:40 hashracontroller single_ltc_monitor[17304]: socket connect(127.0.0.1,4001) failed returning null

you guys need to rewrite your software. - this is rediculous.

so I reboot and it's still fucking happening GET THIS FIXED!

and if we HAVE to buy some sort of device from Amazon to remotely reboot machine every time we switch coins then that is something YOU SHOULD HAVE TO PAY FOR - NOT ME!

[jjj0923]

If you had 2000 accepted and 200 hardware errors, that means 10% of your hashrate is totally wasted.  That's not good.  Your 14mh/s miner is effectively a 12.6mh/s miner.

The clock speed is down to 310 and I have now 500 Accepted, 0 Rejected, 2 HW

That is amazing.  What pool?  Also, what is your ambient temperature where the miner is located?  I'm wondering if my performance issues are due to the heat in my mining space.

@jjj You can reboot the pi by logging into it user:pi pass:controla, then use the command sudo reboot. 

dc - he's talking about recycling the power on the mining unit - not the pi

[davecoin]

Did you email Simon about this?  I'm having the same issue this morning.  Yesterday I could switch pools without issue, today I can't. I updated the firmware as soon as I got the unit.

[jjj0923]

Did you email Simon about this?  I'm having the same issue this morning.  Yesterday I could switch pools without issue, today I can't. I updated the firmware as soon as I got the unit.

you have to reboot - it probably fails about 80% of the time when switching pools and you have to reboot.

and yes I contacted Simon and their tech support guy.

[crocko]

What coin are you mining with Hashra's ASICs ?

[jjj0923]

What coin are you mining with Hashra's ASICs ?

not to avoid the question, but why do you ask?

[crocko]

What coin are you mining with Hashra's ASICs ?

not to avoid the question, but why do you ask?

I don't know where to point my ASIC in order to have at least ROI... 

[chadwickx16]

What coin are you mining with Hashra's ASICs ?

not to avoid the question, but why do you ask?

I don't know where to point my ASIC in order to have at least ROI... 

Silkcoin is on POW for a limited time, or try wafflepool or Clevermining.

[jjj0923]

I did upgrade one of my two units last night and it's been running fine but I did have to reboot it after upgrading

ok, cool.  was there any performance or stability boost do you think?

my only observation(and this has not been proven with multiple tests) is that the unit did not need to be restarted multiple times after changing pools, like I've experienced with the stock firmware.

oh and even though it reboots itself after the update - I neede to reboot it a second time because after it's own reboot all I say was this  in the syslog file:

Jun 12 14:18:54 hashracontroller cgminer: Started cgminer 3.1.1
Jun 12 14:18:59 hashracontroller single_ltc_monitor[2201]: Started LTC PRocess waiting 10 seconds to boot cgminer
Jun 12 14:18:59 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:18:59 hashracontroller cgminer: Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 00038d26
Jun 12 14:18:59 hashracontroller cgminer: All devices disabled, cannot mine!
Jun 12 14:19:04 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:09 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:14 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:19 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:24 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:29 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:34 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:39 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:44 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null
Jun 12 14:19:49 hashracontroller single_ltc_monitor[2201]: socket connect(127.0.0.1,4001) failed returning null

Jeff

right, ok thanks.
I don't seem to have a big issue with restarts on the original firmware so I might just leave it. I took the clock down to 301 & using 50w less power for minimal loss of hash. Now if I could only do something about that infernal noise it makes :/  Though I suspect its as people say & its more the heatsink airflow rather than the fan which is the cause of the issue

took the clock down to 301? - that's the default value!

[jjj0923]

What coin are you mining with Hashra's ASICs ?

not to avoid the question, but why do you ask?

I don't know where to point my ASIC in order to have at least ROI... 

Silkcoin is on POW for a limited time, or try wafflepool or Clevermining.

the problem with silcoin is that the difficulty of almost 600 and even clvermining and ipo miner are having a hell of a time even finding blocks.

if you guys want to make money - send me a PM and I'll tell you what to mine that will blow clevermining away!

but I'm only sharing it with your guys - my fellow Hashra victims, because I feel for you.

[jjj0923]

this is how bad the software is on this system

check this out - it's mining and it doesn;t even know:

5s):0.000 (avg):0.000h/s | A:458  R:11  HW:48  U:183.1/m  WU:26461.2/m         (5s):0.000 (avg):0.000h/s | A:459  R:22  HW:50  U:176.5/m  WU:26229.5/m         (5s):0.000 (avg):0.000h/s | A:461  R:40  HW:50  U:170.7/m  WU:26111.1/m         (5s):0.000 (avg):0.000h/s | A:463  R:49  HW:50  U:165.3/m  WU:25726.9/m         (5s):0.000 (avg):0.000h/s | A:464  R:71  HW:51  U:159.9/m  WU:25854.6/m         (5s):0.000 (avg):0.000h/s | A:469  R:88  HW:51  U:156.3/m  WU:25930.7/m          

the screen is reporting 0 hash rate

this is after rebooting it 7 times to cross my fingers and hope this piece of junk actually mines


I have formally contacted Simon at Hashra and asked for a full refund - this is the "without question" worst experience with any piece of hardware I have ever had in my life and I've been around computers since 1973....and there isn't much I have not seen.

I want my money back and these things out of my life.

it's pretty sad when you think about - I was one of their biggest advocates before the equipment was delivered - Simon would email me often and let me know how things were going - now I'm lucky if I hear from him once per day and he avoids the issue of my discontent.

My heart goes out to the really nice tech guy who has to try and support these things.

My recommendation to you is this Once you start mining a coin - do not switch coins

after 8 reboots it won't go past 11.04 mh - ooops - time for the 9th reboot - the only boot this things deserves is my boot up it's ass at this point

(5s):165.0 (avg):9.151Mh/s | A:1199  R:132  HW:142  U:168.8/m  WU:26544.5/m     (5s):60.00 (avg):9.024Mh/s | A:1221  R:132  HW:142  U:169.5/m  WU:26566.8/m     (5s):120.3M (avg):11.50Mh/s | A:1234  R:132  HW:144  U:169.0/m  WU:26483.3/m    (5s):50.88M (avg):11.49Mh/s | A:1248  R:133  HW:144  U:168.6/m  WU:26384.8/m    (5s):27.57M (avg):11.52Mh/s | A:1259  R:136  HW:146  U:168.1/m  WU:26328.9/m    (5s):12.97M (avg):11.42Mh/s | A:1280  R:142  HW:146  U:168.4/m  WU:26397.7/m    (5s):14.15M (avg):11.48Mh/s | A:1292  R:146  HW:147  U:167.7/m  WU:26353.7/m    (5s):12.74M (avg):11.46Mh/s | A:1301  R:148  HW:152  U:166.7/m  WU:26278.3/m    (5s):13.26M (avg):11.50Mh/s | A:1316  R:148  HW:158  U:166.6/m  WU:26289.3/m    (5s):9.426M (avg):11.44Mh/s | A:1336  R:149  HW:161  U:166.9/m  WU:26325.3/m    (5s):8.813M (avg):11.39Mh/s | A:1354  R:149  HW:163  U:167.1/m  WU:26347.9/m    (5s):15.78M (avg):11.49Mh/s | A:1370  R:150  HW:163  U:167.2/m  WU:26283.4/m    (5s):10.84M (avg):11.45Mh/s | A:1394  R:150  HW:166  U:167.9/m  WU:26375.9/m    (5s):10.03M (avg):11.41Mh/s | A:1407  R:152  HW:168  U:167.4/m  WU:26321.0/m    (5s):14.91M (avg):11.48Mh/s | A:1424  R:153  HW:169  U:167.6/m  WU:26308.6/m    (5s):5.475M (avg):11.34Mh/s | A:1446  R:153  HW:169  U:168.1/m  WU:26318.9/m    (5s):13.82M (avg):11.42Mh/s | A:1465  R:153  HW:171  U:168.3/m  WU:26310.6/m    (5s):5.073M (avg):11.29Mh/s | A:1474  R:153  HW:172  U:167.4/m  WU:26186.1/m    (5s):1.862M (avg):11.16Mh/s | A:1501  R:154  HW:174  U:168.6/m  WU:26294.4/m    (5s):683.6K (avg):11.04Mh/s | A:1516  R:154  HW:175  U:168.4/m  WU:26229.7/m

and and this is what you get it you attempt to restart it:

Jun 13 02:15:34 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:15:39 hashracontroller single_ltc_monitor[1962]: Started LTC PRocess waiting 10 seconds to boot cgminer
Jun 13 02:15:39 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:15:44 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:15:49 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:15:54 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:15:59 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:04 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:09 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:14 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:20 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:25 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:30 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:35 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:40 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:45 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:50 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:16:55 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:17:00 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:17:01 hashracontroller /USR/SBIN/CRON[14032]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 13 02:17:05 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:17:10 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null
Jun 13 02:17:15 hashracontroller UpdateCache[13534]: socket connect(127.0.0.1,4001) failed returning null

time for a coldreboot

- ugh - it's been over an hour now just trying to switch coins,,,,

[jjj0923]

wow - this is impressive - this time after another reboot it's almost as fast as one gridseed!!!

(5s):997.0 (avg):219.5Kh/s | A:143  R:1  HW:7  U:178.7/m  WU:24306.6/m

this is it's specialty though!!!!

it's really good at this:

Jun 13 02:22:51 hashracontroller cgminer: Started cgminer 3.1.1
Jun 13 02:22:51 hashracontroller cgminer: Icarus Detect: Test failed at /dev/ttyUSB0: get 00038d06, should: 00038d26
Jun 13 02:22:51 hashracontroller cgminer: All devices disabled, cannot mine!
Jun 13 02:22:56 hashracontroller single_ltc_monitor[4706]: Started LTC PRocess waiting 10 seconds to boot cgminer

[crocko]

Any idea why the Bitcoin price is going down ? http://preev.com/

[jjj0923]

Any idea why the Bitcoin price is going down ? http://preev.com/

yes - because we just spent a lot of money on miners!!!


LOL

[iikun]

The controla software does seem to misquote the actual hashrate a lot. Mine tells me I'm running steady at 3.5Mhs but poolside at 13.5
A little annoying but as long as the rewards come to my wallet I'm okay with it.

[maxzilla]

The controla software does seem to misquote the actual hashrate a lot. Mine tells me I'm running steady at 3.5Mhs but poolside at 13.5
A little annoying but as long as the rewards come to my wallet I'm okay with it.

Restarting is a real problem with these miners. Sometimes giving the wrong hashrate, or not starting up properly, or at all. Making coinswitching a pain.
I might have found a way to switch pools without restarting cgminer by firing a socket command.
Restarting will still be a problem, but at least you don't have to do it often or at all.
I will keep you posted when there is a new release out. should be in a couple of days