Zeus miner just announced new prices:
http://zeusminer.com/product/week-two-hurricane-x3/
GAW announced compensations:
https://hashtrader.com/t/week-2-3-credit-options/618/3
Topic: HASHRA - LUNAR SERIES - ASIC SCRYPT MINERS - page 22. (Read 61683 times)
Those were on the "super-jupiter" units which were all used hardware and poorly packaged. Hashra packaging was nothing short of amazing.
I finally got my y Lunar Lander today and it isn't working. I tried with a laptop (downloaded the software), and with the RaspPi that is included (which I had to power with another cable because it wouldn't join the internet - thanks to the thread for heads up on that); and on both *AS SOON* as CGminer starts, the unit shuts down. I get this error in the log on the Pi:
Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 00038d26
Not feeling great about this.
My PSU is rated platinum and at 1300W - pretty sure that's not the problem. I have each plug isolated, so I don't think that is the problem. Since the error is USB related, I tried swapping out the USB cable - no dice.
I am open to suggestions.
Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 00038d26
Not feeling great about this.
My PSU is rated platinum and at 1300W - pretty sure that's not the problem. I have each plug isolated, so I don't think that is the problem. Since the error is USB related, I tried swapping out the USB cable - no dice.
I am open to suggestions.
well - don't use their power cable to power the pi - myself and other have had problems. In addition the ethernet cable they supplied did not work. In addition make sure you're nit plugging in the additional 2 wire plug from the pcie cable.
send a message to [email protected] - their tech guy is very responsive.
Thanks - I did take the forum's advice and used a different power cable for the Pi, so thanks for that. I am using my own ethernet cable, and I can browse to the Controla interface. And no, I am not plugging in the +2 on the PCI-E connections. The thing powers up fine... makes lots of noise and even some heat... but then instantly shuts down once I ask to to do some mining...
So working with Hashra support, it appears I have a defective unit. Now it gets interesting. While the support team was responsive and proactive, it will be interesting to see how this plays out. Hopefully Hashra views this as an opportunity to demonstrate excellent customer service. Stay tuned...
After a few days, and just a few questions, support confirmed my unit defective. I have sent it back to Hashra, at a significant cost. Now let's see how they handle this process. I've already lost 20 days *at least* because of the shipping "mistake" and the defective miner. Really, really trying to stay positive on this one... would certainly be easier if Hashra met me half-way.
Every ASIC thread is full of stories like this. I remember clicking pictures of KNC miners with the capacitors and other pieces just randomly falling out of the box.
I finally got my y Lunar Lander today and it isn't working. I tried with a laptop (downloaded the software), and with the RaspPi that is included (which I had to power with another cable because it wouldn't join the internet - thanks to the thread for heads up on that); and on both *AS SOON* as CGminer starts, the unit shuts down. I get this error in the log on the Pi:
Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 00038d26
Not feeling great about this.
My PSU is rated platinum and at 1300W - pretty sure that's not the problem. I have each plug isolated, so I don't think that is the problem. Since the error is USB related, I tried swapping out the USB cable - no dice.
I am open to suggestions.
Icarus Detect: Test failed at /dev/ttyUSB0: get 00000000, should: 00038d26
Not feeling great about this.
My PSU is rated platinum and at 1300W - pretty sure that's not the problem. I have each plug isolated, so I don't think that is the problem. Since the error is USB related, I tried swapping out the USB cable - no dice.
I am open to suggestions.
well - don't use their power cable to power the pi - myself and other have had problems. In addition the ethernet cable they supplied did not work. In addition make sure you're nit plugging in the additional 2 wire plug from the pcie cable.
send a message to [email protected] - their tech guy is very responsive.
Thanks - I did take the forum's advice and used a different power cable for the Pi, so thanks for that. I am using my own ethernet cable, and I can browse to the Controla interface. And no, I am not plugging in the +2 on the PCI-E connections. The thing powers up fine... makes lots of noise and even some heat... but then instantly shuts down once I ask to to do some mining...
So working with Hashra support, it appears I have a defective unit. Now it gets interesting. While the support team was responsive and proactive, it will be interesting to see how this plays out. Hopefully Hashra views this as an opportunity to demonstrate excellent customer service. Stay tuned...
After a few days, and just a few questions, support confirmed my unit defective. I have sent it back to Hashra, at a significant cost. Now let's see how they handle this process. I've already lost 20 days *at least* because of the shipping "mistake" and the defective miner. Really, really trying to stay positive on this one... would certainly be easier if Hashra met me half-way.
You need a room with air conditioner where to place your ASIC, or you have many of these you better search to rent a space on a data center.
Hey fellows,
New here. I have been following this thread but didn't register and post anything until now.
To be honest this is my first asic scrypt miner, was trying to mine with my gpu previously and god those things run slow. Will never see a ROI on those, and I actually trashed one of my GPUs in like my 2nd week. Temps were fine, somewhere around 75c.
So I got my Lunar Lander yesterday and have been trying to optimize it. So far this is the best I could.
http://i272.photobucket.com/albums/jj196/derekz87/Untitled-1_zps34aa6c09.jpg
I have also tried @300, it goes down to about 25.9mhs, however still getting about 6% error with 0.20~0.30% rejection.
what ambient temp are you guys getting, over here it's like 27~30c all year round. I hope that's not gonna be a problem for long term mining. LOL. If you're wondering, I am in Malaysia.
New here. I have been following this thread but didn't register and post anything until now.
To be honest this is my first asic scrypt miner, was trying to mine with my gpu previously and god those things run slow. Will never see a ROI on those, and I actually trashed one of my GPUs in like my 2nd week. Temps were fine, somewhere around 75c.
So I got my Lunar Lander yesterday and have been trying to optimize it. So far this is the best I could.
http://i272.photobucket.com/albums/jj196/derekz87/Untitled-1_zps34aa6c09.jpg
I have also tried @300, it goes down to about 25.9mhs, however still getting about 6% error with 0.20~0.30% rejection.
what ambient temp are you guys getting, over here it's like 27~30c all year round. I hope that's not gonna be a problem for long term mining. LOL. If you're wondering, I am in Malaysia.
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.
My HW error rate is pretty high, but the actual pools seem to report 14.4mh for me, so doesn't this mean kind of the opposite of what you said? If they can lower HW error rate, the hash rate should increase to 15-16. In other words, we aren't currently being skimmed by the high error rate, at least compared to advertised hash rate.
Since 2012, I've never seen an FPGA or ASIC miner advertised as XXX MH/s, GH/s (excluding a 6% error rate).
Look at the two hour average poolside rates for three different pools:
I always get over 14mh even with the high error rate. The miner seems to get the advertised hash power regardless of what error rate is?
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.
My HW error rate is pretty high, but the actual pools seem to report 14.4mh for me, so doesn't this mean kind of the opposite of what you said? If they can lower HW error rate, the hash rate should increase to 15-16. In other words, we aren't currently being skimmed by the high error rate, at least compared to advertised hash rate.
Since 2012, I've never seen an FPGA or ASIC miner advertised as XXX MH/s, GH/s (excluding a 6% error rate).
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.
My HW error rate is pretty high, but the actual pools seem to report 14.4mh for me, so doesn't this mean kind of the opposite of what you said? If they can lower HW error rate, the hash rate should increase to 15-16. In other words, we aren't currently being skimmed by the high error rate, at least compared to advertised hash rate.
I don't seem to be having any of the software issues people are talking about here. I'm using the original firmware with the 14mh miner (didn't upgrade). I use the Pi controller with 4 pools set and it cycles through them all fine. I have no issues with it failing to connect.
I've left the thing on for more than 48 hours and it cycles through different pools without the hash rate dropping or anything.
I did read someone say the included ethernet cable (which I didn't use) is junk and didn't work, maybe that's a possible issue? Check your connections on the back of the miner too, the USB connection that goes into the miner doesn't really hold it in all that tight.
I've left the thing on for more than 48 hours and it cycles through different pools without the hash rate dropping or anything.
I did read someone say the included ethernet cable (which I didn't use) is junk and didn't work, maybe that's a possible issue? Check your connections on the back of the miner too, the USB connection that goes into the miner doesn't really hold it in all that tight.
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.
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
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.
A little annoying but as long as the rewards come to my wallet I'm okay with it.
Any idea why the Bitcoin price is going down ? http://preev.com/
yes - because we just spent a lot of money on miners!!!
LOL
Any idea why the Bitcoin price is going down ? http://preev.com/
wow - this is impressive - this time after another reboot it's almost as fast as one gridseed!!!
this is it's specialty though!!!!
it's really good at this:
Quote
(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:
Quote
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
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
this is how bad the software is on this system
check this out - it's mining and it doesn;t even know:
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
and and this is what you get it you attempt to restart it:
time for a coldreboot
- ugh - it's been over an hour now just trying to switch coins,,,,
check this out - it's mining and it doesn;t even know:
Quote
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
Quote
(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:
Quote
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
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,,,,
What coin are you mining with Hashra's ASICs ?
not to avoid the question, but why do you ask?
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.
What coin are you mining with Hashra's ASICs ?
not to avoid the question, but why do you ask?
Silkcoin is on POW for a limited time, or try wafflepool or Clevermining.
What coin are you mining with Hashra's ASICs ?
not to avoid the question, but why do you ask?
Jump to: