Bitcoin Forum

Anyone using their image ? I cant change the workers settings, everytime i save, their workers shows up back again ???

You got farther than I did. Cannot even get the Pi to boot using their image. Get an error from the keyboard that isn't even plugged in.

Depends how u write the image, what OS are u on ?

You might be using an old image.
The config file might not have the right user rights.

If you're up for it you can change this by going in the PI with putty or some other ssh client program.

go to the PI IP address: login with pi
pw hashra

and type in this command


The above command gives the apache user the ownership of the config directory.
and then just for good measures type this so everybody in the same group can change the file.


Hope that helps

i have updated the image to the latest version, 1.1 and still same bug, cant save my workers.
will try your tip tho, thanks !  :)

thk maxzilla for login information, indeed with mods proposed by you it works

it crashes after ~30 mins, anyone else having this issue ?

Where did you get the image? was it pre installed on the SDCard?
I have a feeling you have a very old image (of the SD card, not the controla).

There was a bug in the usb drivers making the pi crash everytime. You need to update your PI OS to another branch

so login to your PI and type in this code. it will take a while and then reboot.

i got the image from http://hashra.com/support/ and updated to 1.1 after

I used the ApplePi tool that is on the website. I am using OSx.

Try the win app found on PI website ,  on a win machine of course :)

I am using this on 1 pi for every 20 gridseeds. very happy with controla.

What is your current up time with 20 on the Controla?  (latest firmware 1.2.5?)

Hi,

Can we do remote management with Hashra Controla?

Still having issues, not all my miners are being picked up in the WebUI and then it goes ahead and shuts down (the UI does but it still seems to be mining). Had a similar issue when working with Scripta, but it seems the latest Hashra firmware has new login information...

Hi,
I have an issue on my gridseed.
I have set up all gridseed, and configure the raspberry. It's ok the firmware work and i can acces to rasp on browser.
All my gridseed is on power, the fan turn on, but none have a green or red light, just fan turn on and that's all.
what have i missing ?

Did you turn on the USB hub?

OK thanks, it's my power supply of usb hub that doesn't work

I'm giving this image (w/ ver 1.2.5 update) a try on a few of my GS. One problem, I can't seem to login to ssh.

None of these worked:

pi/hashra
pi/controla
pi/raspberry
hashra/controla
hashra/hashra
root/hashra
root/controla
root/raspberry


Suggestions?

same problem here  ???

Just a quick question here: does controla support setting the frequency per miner? So not just 1 frequency for all?

One frequency for all... No individual settings.

Thanks.

With v.1.2.5 in dual mode, I'm only getting 1 MH Scrypt and 60 GH SHA from 10x units... (850 Mhz)

After close inspection of the logs, I noticed that this newer firmware is using both CPUMiner and CGMiner.  Aren't they BOTH supposed to be run from CGMiner?  How can I go from 3.5 MH to 1 MH in scrypt?  I'm really frustrated with these devices, and I really think that I've been duped.

Me 3 cant get root at all

Can change pool and worker etc no problem but plug in miners and they are detected but nothing happens

i grabbed my sdcard with the hashra image and mounted it in another pi using card reader. chrooted and ran passwd. can get in as root now.

I made a new copy of Hashra, updated it to 1.2.7, then changed the passwords. It was a PITA to figure out, but it's done now. I'm sharing it with you guys to hopefully help save some others' headaches.

https://mega.co.nz/#!8R83Aa5A!YxofpkLC9PCMbpeR63a-YHZ81I7Tc_IS9IePP280wLg (https://mega.co.nz/#!8R83Aa5A!YxofpkLC9PCMbpeR63a-YHZ81I7Tc_IS9IePP280wLg)

Changes:

• 8GB card req (didn't have a 4GB handy)
• Passwords: root/darkknight pi/darkknight
• Default pools on first boot are set to mine for charity

Note: My MEGA account is free, so limited bandwidth. I'd appreciate anyone else who can redistribute it.

(Donations welcome if I saved you a headache)  ;)

BTC: 1LDYFTZhjHcxSWrgdzAwUgBT1T3b63iMf1
LTC: LcEAuGD8f7T7DRJqdRyTWhJKtGSAXDKQL3
DOGE: D5tEoH3JvXm5HRYtkbAvzun3RQTFg932T8

Hello Miners,

I have problems with my Gridseed.

While running Hashra Controla 1.27. newest update. My Dashboard still shows Harware errors and much more.


CONTROLA

Running in SCRYPT mode
Mining Session Overview (02 hrs 14 mins 53 seconds )

    3.605 Mh/s current hashrate
    3.623 Mh/s avg hashrate in last 5m
    687 / 33 Acc./Rej. 4.80 % rejection rate
    0.047 Work utility

    5 Found blocks.
    2735 Work discarded
    0 Work stale
    3 Hardware errors

SCRYPT Miners hashrate 3620 Kh/s
362 Kh/s
Scrypt Miner 1
Mining...77/79 (2.53%)
362 Kh/s
Scrypt Miner 2
Mining...52/53 (1.89%)
362 Kh/s
Scrypt Miner 3
Mining...46/52 (11.54%)
362 Kh/s
Scrypt Miner 4
Mining...78/83 (6.02%)
362 Kh/s
Scrypt Miner 5
Mining...76/81 (6.17%)
362 Kh/s
Scrypt Miner 6
Mining...83/87 (4.6%)
362 Kh/s
Scrypt Miner 7
Mining...65/67 (2.99%)
362 Kh/s
Scrypt Miner 8
Mining...67/70 (4.29%)
362 Kh/s
Scrypt Miner 9
Mining...66/69 (4.35%)
362 Kh/s
Scrypt Miner 10
Mining...77/79 (2.53%)

What do you think? Looks this normal? What can I try.

Big THX for advice.

What pool are you on? I noticed similar on a high difficulty pool but got good results on low difficulty (less rejects/errors)

Yes it depends on the difficulty and how many hashes the other players have. And it depends if you come in a round where everything is allredy counted. Then you get a high rejecto rate.

But GPU´s seem to have a lower rejecto. rate. Looks like:-)

Do you know anything about " Hardware errors "? Do you have shown hardware errors on your set up?

What means " work discarded "?

Thx and good mining to you

Ive used BFMiner, LightningAsic Controller and Hashra Controla, all seem to give around 2% HW errors. Some seem to display them differently, eg in Hashra and Lightningasic it tells me which controllers give errors and its pretty even at about 2% each miner give or take.

In BFMiner the figure is 2% but one or two miners are giving all the errors and the rest show none.

So its pretty weird but overall I think its normal - to have a small amount with these devices. Like I said for some reason pools seems to make a big difference

I am having great luck with the 1.2.7 image for my seeds.  I am in the process of doing the modifications tot overclock and needing 950mhz as an option.  It would be great if we could have increased capabilities in this regard.  I would contribute a small reward to this. 

for me hashra crashes after a few hours, tested with 19 miners, and i cant simply open the webpage after a few hours

Same here regarding "luck"... I have haven't had any drop in over 36hrs now..

edit:  nvm.. shouldn't have said anything..

looks like I have a PI that is completely down and needing a reboot.. no way to do that remotely.. and even if I could SSH in no one knows the root/pw 

Mine doesnt crash but it restarts once or twice a day.  I am guessing that is built into the Chron by default.  It's quick and I don't mind much although it should be configurable.  Does Hashra participate in the conversation about their image at all?

My Gridseeds just restart a few times a day.

Can Hashra be used with Teamviewer?

Version 1.3 of HASHRA CONTROLA will be released this week. We're testing it right now.
new features

screenshot:
https://www.dropbox.com/s/galelbi3c9il2ao/Screenshot%202014-04-02%2019.42.28.png

- removed bfg/cgminer stats which were confusing everybody.
- manual restart
- manual reboot
- clock speed can go all the way to 1200mhz now (not advisable, but for all you modders out there...it will be available)
- system settings with:
-- scheduled restart scheme in hours (0 hours for never)
-- SHA cores configuration for dual mode. You can configure the amount of SHA cores to be enabled (max 16 cores) more cores -> higher sha hashrate but will lower scrypt hashrate and vice versa.
-- you have to login with default user root / root to HASHRA CONTROLA webconsole. you can change this password if you want, in system settings.

Sounds Great.

THX ;D

Nice, I was just talking about having the option to restart/reboot via the web interface.
What is the reasoning behind only allowing overclock in 50mhz increments?

That's great news!

If someone is faster, add p'lwease a Content Slider Box or iframe etc. or similar to switch Pools, it's annoying to switch Pools with Hashra Kontrola.

That's up next.
Failover support in development

Individual miner clock would be awesome aswell :)

not sure if its possible, but a detect of dead miners and restart them would be cool. Im seeing that lightningasic got this on their v3 firmware thats just out.

That is not possible since we're using BFGMiner (not multiple CPUMiner instances like LightningAsic).
In my experience using BFGminer, I've never had to restart the miners individualy or do power cycles. It runs stable for hours on end. I plugged in 20 GS on 1 PI.

what is the password for 1.3? Stuck at the login page.

hashra hashra

If that doesn't work, try root / root, when you click on UPDATE CONTROLA link again then login with hashra / hashra. I had to fullfill last minute wishes from the big cheese..sorry about that.

When I try to save adjusted settings like the "reboot timer"  it never saves

Looks pretty stabel and the rejecto rate has gettin better.

I have a questin to let Hahra running on 900 MHZ. Is it stable witout any problems and no further configuration?
Just have my 850 MHz running;-)

Is there any way we can get the root password for the build? I'd like to be able to edit httpd.conf to allow access from outside of the local network. Also being able to install things like htop, restart Apache and reboot from SSH would go a long way!

Anybody have a 4GB image with 1.3 of Controla that I can play with?

New IMG file will be 4GB.

We will be releasing a dual version and a Scrypt only version in the coming days... (for a certain new miner coming out)

New v1.3.3 is out.. the bug saving hours per reboot under settings es fixed..

Good stuff!  Thx!

Great!   (hint:  ;) Put a link in your response, and maybe a bit of a sales pitch about an up coming sale or new "how-to" on your website.  ;) )

Link??

Github : https://github.com/HASHRA/CONTROLA (https://github.com/HASHRA/CONTROLA)

SD CARD IMG on this page is still 1.2: http://hashra.com/support/ (http://hashra.com/support/)

I was hoping someone would link to complete 4GB SD Card image with 1.3.3 loaded.

4GB IMG not up yet I'm afraid on our site... will be a day or so.
Right now you will need to download old IMG and the hit "UPDATE CONTROLA" and this will give you version 1.3.3

You can download the IMG file from hashra.com/support

We are working on a little secret project right now... In a couple of days we will be releasing our new products, hopefully you will like them.  ;)

We would like to hear how people get on with the latest updated firmware, especially being able to change to BTC cores in dual mode.

Hello!
Is it possible to switch off somehow the name "Hashra Controla" & wording about default user "hashra" on login page? it is great for security reasons :)

will Hashra Controla run on a Raspberry Model A ?!? the one with 256mb.. ?
it's cheaper than model B.. and i would like to save every dollar possible for my new gridseed rig

that's a noob question ..but i'm totally new to raspberry.. and it look a powerfull but unknown device to a rookie like me :)

Please add some functionality to configure secondary (backup) pools. This would be nice and solid.

If the primary pool become down now, mining stops. If we can configure a backup, it switches over until the primary pool become online again.

the Model A only has one USB  and no ethernet port, you could use it though you would have to have enough knowledge to set up wifi and would probably be limited to 8 or 9 gridseeds

Updated to hashra controla 1.33 but I can access anymore to the web interface nor ping the raspberry, seems having some issues with the DHCP...anyone have experienced it?

Does the yellow and green leds light up on the PI? if only the red leds light up, it means your SDCard is corrupted. If all leds light up, then the PI is alive, and probably got assigned a different IP address. Check your internal network for new devices (in the router, or FING app)

Yes the green leds are on, the image is not corrupted since I've logged directly to the raspberry and checked for the connection...a ifconfig command returns me UP BROADCAST MULTICAST for the eth0 but not IP assigned...I've also tried to assign manually the ip but still I can't see the it on the network
The raspberry is connected to a little tp-link switch and prior the 1.33 I've had no issues...any suggestion? ::) :)

Hmm no suggestions other than reinstall a fresh img on the sdcard. the firmware updates do not go outside the /var/www directory. It simply replaces the php files. So no system configuration is changed during a controla update.

sorry man.

I tought the update was related only to the web implementation but wasn't sure, thanks for confirming it...also I've just connected the raspberry to the office network and it works good (included the web interface). So the issues is related to my home connection... go figure what is, sorry for the misunderstanding ::)

i got  HASHRA on my pi with 31 grid seeds only 29 showed up. it is still mining but not i cant login via login.php i did not change the password. if i type a incorrect password/username in the login page says "Access denied" but if i use hashra/hashra if just reload the page. any advice beside rewite to card or do a manualy restart on how to gain access. or how to get it to see all my devices?


Thanks

too many devices on The pi. it's been tested to run properly on 20 devices. 25 max

Is it software or hardware thats the limiting factor?

I will pay 5 LTC for anyone who can help me figure out why my 20 seed rig on raspberry pi crashes everytime on startup.  10 seeds works fine, 15 seeds works fine, 20 seeds auto crash.  Payment to the person who solves it!  Running Controla image on the pi.  2x10 port shitty ass USB hubs but I dont see why they would be the issue I have tried many diff hubs and get the same result.  Powered by 2x360w12v30a power supplys.

-Andrew

Not to be a dick but why not just get another rPi?  They're cheap as dirt.

I am running 100 Gridseed units on 5 pi's same results over 40 tested units/2 pi's now.  It is not the pi as far as I can tell.

(edit)  The next 20 seed system i tested can only run 13 seeds without auto crash.

Which version of controla are you running? and in what mode? Scrypt or SHA/Dual? the latter does not work well with so many devices, because it uses cgminer.

In my case it helps to connect only one USB-Hub with the PI and plug the further hub in the plugged. Don't know why, but the pi can handle now 20 devices stable without any reboot since 14h  :)

Try to daisychain your hubs insted. so hub2 -> hub1 -> pi - with just 1 usb cable.

Could be an issue with conflicting data on the hubs or so.

For 5 LTC you could split the load, and buy anpther pi, it's probably the usb hubs though,

Interesting, I will try this.  Have you had any issue with the powered USB ports?  Do you know if it has to be a certain amperage capability?

500mA

I have seen this 500ma number thrown around a lot however there is no 10 port usb hub that I can find that actually supports 5AMPS across 10 ports to have 500ma/port.  Can anyone post a link to a usb hub they are using which works for them with 20 units and a pi?  The ones I have are trash its just odd that they would work for 15 units but not for 20...

Has anyone else found this version of the Controlla to be even more unstable than the previous version?  I keep dropping some or all of my units.  Restarting or rebooting doesn't help, only physically shutting down power and restating works.  And then I get maybe a couple of hours and it happens again.

Could you tell me which USB hubs you are using?  ;)

I still don't get why you guys are running your miners on Rpi's, that shit is so unstable, mine would crash with just 10 miners connected.
For $20 shipped you could buy yourself a Tp-link 703N and install Lightningasic firmware, and run 50+ miners on it (or 100+ if you have modded the RAM to 64MB).

Where do you get lightning asic firmware?

https://bitcointalk.org/index.php?topic=554542.0

Please just keep in mind that it might brick on flash.. (as happend to mine).

It is possible to solder a serial -> usb connection onto the controller, but it requires some soldering skills.


Im running hashra 1.3.3 and its been rock solid since i set it up.

This software is compatible with a wifi module? My router is in a difficult place to connect the ethernet cable...
Thanks

Two questions:

1. In v1.3.3 what's the login/pass for getting into the Pi with SSH?   

2. The official open source project page is listed on GitHub, but the update.php script pulls the following bitbucket project when checking for updates: https://bitbucket.org/api/1.0/repositories/purplefox/hashra-public-firmware; which one is canonical?

I really want to get a mod working that supports separate frequencies per GS along with auto-determination of the most productive clock frequency for each GS.  I was going to try LightningAsic until I bricked my Wiibox trying to flash the latest version.  I prefer to work with the Pi since it's much more extensible and accessible.

Just wanted to chime in and say I have 4 pi's running the Controla with different combos (63 total) and have had essentially zero issues... (have reboots set to 6hrs on all of them).

thumbs up!

Happy to hear :) I didn't understand why people are having stability issues with it. Mine has been running unattended for a week now. max hashrate.

The next version will have failover support.

In my case, it depends in which pool is mining:

-Wafflepool: Very stable
-Hashcows: After a few hours stops hashing
-Poolwarz: Same as Hashcows
-WemineLTC: Very stable

Could it be related to the fact that in both with stability issues you can mine and keep different coins?

I have no Idea. I only tried with
Wafflepool, (stable)
Clevermining, (stable but loads of rejects and HW errors (but this is supposed to be normal for clevermining according to the support forum)
Ghash (super stable, this is my testing pool)

I even tried dual (with 10 miners, 20 will crash)
sha cores set to 5 cores
stable for days.
Got 3mhs Scrypt and 35 Ghs BTC

Btw,

Did anybody notice hashra has released the Gridseed blades for 1500 bucks?
http://hashra.com/gridseedblade/ (http://hashra.com/gridseedblade/)

Using their image to run 20 seeds on a rpi - running for a week straight now.

Both repos are identical.
setting individual clockspeeds for the miners requires rework on BFGMiner. Since this is used for scrypt mining. I don't think this build of BFGMiner supports it.

Will the Hashra Controla work with the gridseed 80 chip blade mixed in with the 5 chiip gridseeds or does it need a special version of the program?

yes, but you need to use the blade version of controla, which has scrypt mode disabled

Dont you mean SHA256 mode disabled?

Sorry, yes, that's what I meant :)

\i don't really want to bother with the importing of the gridseed blade from hashra as after vat and import tax I would be worse of if I got one it would be from minereu.com

My point is can you get the hashra controla for the blade in a download anywhere

Not sure that's true....  ;)

But yes, we'll have the new HASHRA BLADE CONTROLA free to download on our site. :)

Does anyone know what the default SSH login for the Hashra Controlla image is? I've tried hashra@'ipaddress' PW hashra and no go...Also how do you set the miner to reboot after a set amount of time and/or reboot in case of crashing...?  Thanks!

I actually figured out how to set the restart timing its just in the settings on the GUI.  Weird though when I click save the n number of hours i set to restart in defaults back to zero?  Has it logged the number I entered or is it not functioning properly?

In the UK $1500 imported would be plus 2.1% import tax plus 20% VAT which could be around $1840 unless you were very lucky and it got  through customs without anybody tagging it

Can't see the script only version of the CONTROLA on the hashra site

Hi, You're using the version which still has the saving bug.. you can click on the upgrade controla button to solve this

Just a quick FYI for those running the gridseed without the fan

My hardware errors were creeping up so I have linked 4 of the fans into the stack at 6V which is almost silent and in three hours at 850Mhz I have had one hardware error out of a total of 13 miners

So the gridseed probably does need a bit of cooling in script  but not the amount that is the default

Thanks I will upgrade.  What version fixes this issue?  I thought I was on the most recent one...  Anyone having issues with crashing every 20 hours or so?  Would programming a miner restart every 4 hours or so fix this issue?

No it doesnt!!  Same issues in v1.3.3

Ok I think I understand the bug now. a background process created the config files before you did. So when you want to edit the file through the gui, you don't have write access to it. I've fixed the bug on version 1.3.3.1
can you click update again ?

Yes 1.3.3.1 has fixed the issue.  Thanks!  However I do still have random crashing of a couple machines but I guess thats another battle...

[/quote]

Yes 1.3.3.1 has fixed the issue.  Thanks!  However I do still have random crashing of a couple machines but I guess thats another battle...
[/quote]


Hashra controla  on the pi has been running fine without a glitch for me for days so it must be some sort of hardware problem at your end, power problems or an faulty sd card spring to mind.

The BLADE CONTROLA will be up on our site by the end of the week, for those that purchase from us will get it pre-loaded on an SD card.

Blades shipping now? Looking at getting one.

Due to strong demand

https://www.dropbox.com/s/knd7lxgvtvb8d82/Screenshot%202014-04-16%2008.13.52.png

Failover support added in CONTROLA 1.4.0

It's being tested right now and will be released later this week.

You can only upgrade by downloading the img file and burning it to an SDCard. From then on updating through the update link will be possible again. Sorry to have to do that. But since there will be multiple flavors of CONTROLA coming out (e.g scrypt only, blade etc), there was no easier way.

The failover will make it possible to rent out your mining rig to rental services like betarigs.com. It will go to your favorite pool automatically when no rental session is going on and it will keep polling the betarigs pool in case somebody wants to rent your rig.

And CONTROLA also displays on screen when your pool is dead (wrong worker config, url or portnr)

Blades shipping out towards the end of this week...  :)

We will make sure everyone gets a copy of the BLADE CONTROLA on an sd card that buys from us, you will also be able to download it though from our website.

Looking forward to this - screenshot looks good like the layout of the failovers

I note that you get the error that I do

bfgminer[30513]: JSON-RPC non method decode failed: (null)
bfgminer[30513]: Unknown stratum msg: {"id":null,"result":[],"error":true}

is this just a quirk of bfgminer?

Can anyone assist me on this issue?  It seems to crash at the point that it is set to autorestart, I guess it just forgets about the restart part...  they dont all crash at the same time.  I has one crash after 4 hours then 3 crashed at 8 hours then the last one at 12 hours.  Very odd and I have not sure where to go from here...  any help would be VERY much appreciated.  Thanks.

How many MINI's you have on the Pi?

We suggest 20 in Scrypt.... 10 in Dual mode.

I have 20 units on a single Pi.  They boot up and all run perfectly fine until the shutdown command gets sent from the GUI and they just don't boot back up it would seem.  I'm running them off a 30AMP 360w 12v power brick which I really doubt is an issue as they run flawlessly when they are online... Could the Pi SD card be corrupted?  Keep in mind I have 100 units across 5 Pi's and this is happening on all machines so whatever the issue is it would have to apply to everything not just one or two machines.  And since they dont all seem to crash at the same intervals the issue gets a bit more convoluted.... Hopefully someone can assist.  I really like the Controla interface so I hope that is not the issue.

-Andrew

20 units should be fine with Controla at 850 Clock speed.

What USB hub you using? sounds alike it could be a hardware issue. Really want to use really good quality powerful HUBs if possible, does make a big difference.

I am using these hubs

http://www.amazon.com/Plugable-USB-Port-Power-Adapter/dp/B00483WRZ6/ref=sr_1_3?ie=UTF8&qid=1397679929&sr=8-3&keywords=10+port+usb+hub

which I think to be pretty decent quality hubs.  The ones I got shipped when I bought the units were trash 6 dollar hubs from china.  Not a single one of them worked properly.  I wasn't even able to boot a pi with 20 units.  Since I bought these hubs everything boots up and runs fine its just a matter of working out the shutdown issue.  Can I work around this problem by maybe entering a large number like 500 for an 'n' value of time between restarts on the GUI?  As I mentioned the issue seems only to occur when the GUI sends the command to restart.  A hard reboot works fine and they come right back up and start hashing.. Also would there be anyway to program the pi to hard reboot the machine every set amount of time?  Thanks for the help!

The error comes from Pool 0, so wafflepool. The glitch is there

If you think the restart is causing the hanging, you can set this to 0, which means, it will never restart the mining process. But still, It's strange, It should run fine with 20 miners. I am using a different hub though. What model PI are you using ? the model B?

If model B has the dual USB ports then yes it is model B.  Yes I find this issue very odd as well... The only thing I can figure is that is must be the GUI is some way whether it is corrupt on the SD card or otherwise.  Would be odd for it to be corrupted across all 5 cards however...  Some people recommend daisy chaining the USB hubs together rather than utilizing both ports on the Pi but it doesnt seem to be an issue on startup so I dont see why that would cause a problem on a restart...  Also not that this is related but I notice when I go to manually restart the machines that the GUI has completely locked up and sends me to a nearly blank html page that looks like an empty repository or the like.  This will sometimes occur after a few minutes of mining and the GUI will not be available to me until a fresh hard boot of the Pi...  The machines continue mining through this issue so I never really thought it was a huge problem but perhaps my intermittent ability to access the GUI is related to a corrupted image or a bad kernel?

In fact now that I think on it this inability to access the GUI may be why the machines only seem to fail when they attempt to restart after the programmed 'n' number of hours as the GUI has locked up and does not become an issue until this command is sent...  This seems plausible but I am still totally in the dark as to why the GUI would do such a thing... I guess that it points more toward a corrupted SD card or bad kernel of the Controla software however.

I wanted to post a picture of the message I am seeing on the GUI when it locks up,  this may point to me having received trashy SD cards or possibly a corrupted image file on the cards.  I am going to use Apple Pi Baker to re image the SD cards to see if this fixes anything tonight.http://s1.postimg.org/9tqfsmr27/Screen_Shot_2014_04_16_at_5_47_20_PM.png

Yes, think this is wise to do. Make you obviously click update firmware once downloaded to make sure you have the latest version running.

Thanks for all the help unfortunately the re imaged Pi did not seem to resolve any issues, still recurring instability across the machines.  Could I have been sent bad SD cards somehow?  Really not sure where to go from here..

are you mining scrypt, sha or dual?
what's the freq?
what pool?

I had the same issue after I did the last update. And again the other night. Stayed up all night trying to fix it.
Came across a very useful article and I followed the steps and it worked.  If you have 2 or more SD cards, its probably the image is corrupted on it. Which seems to happen from time to time with the PI.

Use one of your good cards and back up the image on it. "clone" it.  Then use the clone for any cards that might have a problem.  It worked for me.

I am using the darkknight modified image updated

https://litecointalk.org/index.php?topic=18096.0

and that works fine without any lock ups, What I suggest you do is burn this image to an sd card update it then set your pools then make an image to copy to the sd cards that don't work.

His image the root password is darkknight but it is easily changed with the passwd command, just use halt to stop the pi before you remove the card to make an image.

Scrypt ,Clevermining, 850mhz

As I mentioned I re imaged the cards multiple times with no success.

For the love of god does anyone have a fix for this?  I can't figure it out for my life...

i know you said you have re-imaged multiple times, but have you used the same image file each time? Maybe thats the issue. Try re-downloading the file and go from there if you havnt already.

Thanks AmDD I will try that.  I am also buying some class 10 Sandisk 8gb cards to see if maybe I got a bad batch of NOOBS cards shipped with the Pi's...always a possibility.  Not much more I can try if that doesn't do the trick.

Anyone else having this issue with the Controla software or can I pretty safely say that I am having some type of hardware issue?  What is everyone using for USB hubs for 20 miners?

DOuble check that class 10 cards will work. I seem to remember back when the pis first came out that class 10 didnt work well. I could be wrong tho.

Im using 3 Rosewell powered hubs and have 22 seeds running on a single pi.

It's unlikely that hub problems are crashing the pi all they will do is drop the gridseeds that said I am using the Etekcity® 10 Port USB 2.0 Hub Powered External with 3A Power though it may be called something else in your country.
http://www.amazon.co.uk/gp/product/B00ELPSEVW/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1

Raspberry Pi crashes are down to a faulty/damaged SD card image or the pi not getting enough stable power

I've had PI crashes because of unstable power. A good way to tell if you're having unstable power is if the red power LED is flickering. TP1 and TP2 on the RPi should measure above 4.75V with the Pi active and hashing away. Best to use a known good power adapter (like a good original phone charger that's at least 1A capable).

I hope someone can help.

Card make and model: kingston SDV10/8GB

I get this same image on my pies but if I reboot them they simply won't start anymore. If I then remove power and read the SD card in a windows 8 laptop it is shown as a 2TB removable card in easeus partition master with a master boot record signature of FFFFFFFF so that is obviously broken.

Now if I try and have the software rebuild the MBR I get this message: "There are some errors occurred while writing sector on disk".
If I try to flash a new image onto it(with win32diskimager) I get the message that the disk is write protected.

Putting the card into a USB reader shows it as being 7.48GB in size(this is correct) and having a MBR signature of 55555555.
Nothing else changes.(still cannot write to it)


These have been running correct for one full week but after the last weekend the issues started.
This has so far happened to two cards on monday, 1 more on wednesday and now another one on friday so I would really like to know what is going on.
I already contacted kingston and they basically said that because I used the SD card in a raspberry they wouldn't be able to help me.

Does anyone have any idea what is going on/how to solve this?

Also if this is just the wrong model card or something: what do you reccomend?

Is it possible that the power adapters that came with the Pi are not suitable for stable power delivery?  I do have all my equipment plugged into the same outlet for each rig, maybe I should separate the Pi's to a different outlet.  Anyone recommend a power supply with a micro usb connection thats good quality for the Pi?  Thanks guys.

This sounds like good reasoning.  Is it possible that the cards themselves are faulty?  Or just the image?  I have re-imaged the cards many times so if the image keeps becoming faulty the cause of that would be bad SD cards maybe?  Or perhaps the fact that the Pi is crashing and hard booting, I suppose this might corrupt the SD card.  But that still wouldn't explain why the Pi's are crashing.  And also when I say the Pi's are 'crashing'  all I mean is that they are locking up, the hashra interface GUI is inaccessible and mining has stopped.  They dont actually shut off.

I want to clarify when I say the Pi is 'crashing'  I mean that the GUI locks up, mining stops and I get the message from the pictures above when trying to log into the Pi over the web GUI.  For all intents and purposes the Pi looks like it is still running but only a hard reboot will get me back in.  The things stop mining every like 6 hours at this point and I am baffled as to what could cause this.  Some of them also seem to stop mining at the exact same time and I cannot figure out why that would happen either.  They aren't linked to each other in any way.

at the moment I am using a 8Gb KINSTON SD SD4/8GB CLASS4

http://www.scan.co.uk/products/8gb-kingston-sdhc-memory-card-class-4

which has been fine for weeks


the image is the  darkknight version (see above) written with the applePi-Baker then updated

maybe you have a problem with your electrical supply something that is putting an intermittent high draw on the power or adding noise to the line

Is it possible that the power draw to the Gridseed units changes depending on what coin they are mining?  I am using a multipool stratum (clevermining.com)  If certain faster or slower coins caused the power draw to change I could see this being a possibility. 

I wish I had purchased this now, but I bought Sandisk class 10 8gb cards.  Hopefully they will work.  Right now the machines are running off of the NOOB cards delivered with the Pi.

What are you using for USB hubs and for a power supply?  I'd be interested to know all the components of a working system.  Do you run 20 Gridseeds on a single Pi?  Thanks!!

On the next update could we get the ability to tune individual miners?

Spot on… Yes please try this out.

Regarding HUBs we suggest to use the most powerful you can get, the 20 port versions we have on our site for the Atlantis is one we get made to order here in Shenzhen… uses 90W power… I am sure there was a stability increase when we started using these.

I'm sure someone is selling these on ebay.

We made a decision not to go for this for now I'm afraid.

Could you link me to this exact hub by chance?  Thanks!

Can anyone successfully running 20 GRDS on a single Pi give me a full list of the hardware they are using from USB hubs to power supply and everything in between so I can keep troubleshooting this.  I have so far not discovered the reason for the random crashing.  Would be very helpful to know what is working for people.

Normal raspbian OS with all the dependencies to build cgminer.
Not sure which cgminer 3.7.2 it is, andareed or girhes. https://i.imgur.com/clzwtn2.jpg?1
USB hubs http://goo.gl/Ify5L3
Lutro power plugs
Monoprice USB cables.

Thanks man I appreciate that, what are you using for power to the gridseed units?  What kind of SD Card with the RPi?

Power cables
http://lutro0-customs.com/products/gridseed-pci-e-modded-power-cables
SD card
http://www.amazon.com/gp/product/B003VNKNEG/ref=oh_details_o06_s00_i01?ie=UTF8&psc=1

Yes sorry, that would help…

http://www.aliexpress.com/item/DHL-Free-Shipping-20-Port-USB-Hub-2-0USB-High-Speed-Industrial-Grade-TF-Card-U/1657611461.html

Hey Hashra

Any idea if/when you guys are gonna be working on individual clock speeds and/or auto-tuning as there is in the lightningasic controller?

Ditto.. this would be a huge benefit, esp for those of us that are running multiple units.  Right now I have to downclock to the weakest unit, I have 14 others that can run 50-100 Mhz faster, it's a huge disadvantage to using your product, but I really like the rest of it.  Another feature I'd like is in addition for each unit showing the shares/reject like it does now, is to show the HW errors for each unit, it would make it a lot easier to figure out which units are having issues when running so many of them.

And set a failover pool..or long shot add load balance between pools.

what is the algorithm for auto tuning? the slower the unit the lower the clock speed? measured by pool hashrate and hw errors?

if you really want to set different clock speed per miner, this also possible with CONTROLA btw, it's a hack, but it works. I don't know if it will have any effect in overall mining performance though.

PM me if you want to know how to do this.

failover is already available in version 1.4.0

Quick question for you guys. I have 20 gridseeds running on controlla. would it be worth it to dual mine? also if it is worth it i have a spare seasonic 1050watt psu, would that be enough power?

Please see hashra.com/support to download version 1.4.0

Now called "HASHRA MINI CONTROLA" as we will have a version for BLADE and another for ATLANTIS.

"MINI" is what we are now calling the Gridseed "5 Chip Devices".

Personally I don't think it's worth it.

I've tested it with 10 miners. 20 makes controla unresponsive in dual mode. I set the btc cores to 5 in system settings. It get's like 3.5 gh for sha and 300k for scrypt per miner. So for a 10 unit, 35ghs / 3mhs

BTC mining on the gridseed  would probably  not even pay for the electric used these days, it's a feature that when designed was at a difficulty that would have been making money but that ship has long since sailed.

what's the root password for 1.4?

 it's not root, hashra or pi

Sorry Bexwhitt but the user and password will not be public for this version.

We are working on some features for the future where having the user and password public is just not going to work.

Sorry about that.

LA coder explained a bit here:

I have changed the algo meanwhile, https://github.com/siklon/usb-miner/blob/master/software/cpuminer/gc3355.h
Getting 3700 KH/s poolside consistently with 10 miners, unmodded.

Feel free to compile it for Rpi.

Just wanted to say thank you to the Hashra guys and everyone else who helped me narrow down the possible issues with my machines.  As it turns out a bad ethernet hub was creating a data collision domain with all the machines.  Once removed all was well.  Thanks again!!

-Andrew

Good to hear!

When will the BLADE version be released?

so there in no safe way to shut down the pi if I need to make some adjustments, clever

Under the current Hashra controla, you can't do an update?

So I just want to confirm, I have to load the image to the sd cards manually?

You do, it was mentioned earlier that the 1.4 will need a new image.

The SD card I got with my PI is a 16GB.  I read that some of you able to use 8GB!  Will the new 1.4 fit on an 8GB?  What class of cards better to use with PI?

New IMG file is 3.88GB, I would suggest to use an 8GB card.

Please see this list for details on SD cards best for the Pi.
http://elinux.org/RPi_SD_cards

I have used a class-4 8GB card with no problems


but hashra controla will work with a 32GB card as it is Up my stairs ATM

First I want to thank Hashra for making the image available for download. Now I need some help setting up the Controla. Looking at the output below, it appears that only one gridseed mini is working. Does anyone know what I may be doing wrong?

1.036 Mh/s current hashrate 1.019 Mh/s avg hashrate 69 / 20 Acc./Rej.
28.99 % rejection rate
3 Hardware errors

SCRYPT Miners hashrate 1017 Kh/s

Scrypt Miner 1
Mining...5/5 (0%)339 Kh/s
Scrypt Miner 2
Mining...64/67 (4.48%)339 Kh/s
Scrypt Miner 3
Mining...0/0 (0%)

Total hashing listed on clever mining is 363.

I think your clock speed might have been set too high ?

I have it set at 800, but I've tried going as low as 700.

hmm strange. What kind of hub are you using?

Rosewill 10 port hub. I've used this hub with several pi's previously.

I've seen a few posts similar with this issue using Clevermining, Multipool and a few others... it's your rejects - out of 69, 20 of them were rejected by the pool, that's pretty high - for example on Rapidhash I'm only averaging about a 2% reject rate at most... so it looks to be a pool side issue.  You can see others are having the same issue over at the Cleverming thread here.. https://bitcointalk.org/index.php?topic=448649.3840

*edit -never mind - looking closer your miner #3 is not doing anything, and #1 is not doing much at all. I've had a few hang, the best practice I've found is to power up the hub and Gridseeds first, until the red light comes on with each unit, then boot the Pi.

Thank you, I'll give that a try.

HASHRA,

I like the new feature on the mini controla that I can add multiple pools.  Finnally I don't have to cut/paste all the time.

I would like to see you guys add the ability to get some more mining control settings though, like in scripta.  The reason is, I like to mine on p2pools and I need to tweak the settings for optimum mining.  With scripta it's possible.  NOT with Hashra.

Another thing is, it would be nice for us to know what you are changing or tweaking in every update so that we could give you feed backs.

Still, over 850Mhz is not possible to mine without huge HW

and still "some" HW under 850Mhz speeds.

I am getting alot less errors with new 1.40. I am also running a blade. I am running minis at 850 and blade at 800. shows 2 340 Mhs on 1.40 but 5.40 Mhs on logs and more or less in pool. Thank you.

I tried for the first time to bump up the core speed to 1000Mhz.  Suprisingly, I got no HW!! However, I get no shares and I'm not even able to connect to the servers anymore??
Not even big pools like wafflepool or multipool.  The smaller pools don't show me hashrate and I don't get any shares too!!

Anyone can help out with this?

you need to use The blade version of controla, which will show the correct hashrate.

1000 MHz will not work unless your miners are modded. you have to set the clock back to 850

So what's the point of Hashra showing different clock speeds in the controla?

people who modded their miners wanted the option to be available... so it's there now

so then in Hashra mini controla, the hash rate it shows when I have it set at 1050Mhz, is not correct?

probably not. the local hashrate is an estimation based on the amount of chips and clock frequency.
setting the clock speed to 1050 will skew that estimation, when it's not modded. I've seen people running their modded miners on 1250, making them hash around 500kh ... but this uses 20w power. to mod your miner you need to replace the resistors on the chips to overvolt them.

Thanks Sandor111
Great job on the auto-tuning. Although I'm not sure if I'm ever going to implement this, since GS has announced to stop production of these little miners.

Thanks for the input.

Were working on it and will take what you said on board, thanks.  :)

Anyone know if certain script coins require more power (electricity) to mine?

Should need more power regardless of what you're mining as long as the frequency they are running on is the same. Assuming they are being supplied with work all the time.

I installed ControlA 1.4.0 a couple of days ago on my Raspberry Pi and the unit is running well.

This morning, I attempted to log into the web interface (I left the defaults for the moment) and it simply stays n the login screen.  Any ideas other than resetting it?


GS

Just had the same issue. Can't really do anything other then to reset it at this point. Would like to add that the unit itself is still hashing away. So I think it's just the front end that's down.

Noticed this issue as well with 1.4.0...

Sorry, maybe I'm missing something, but where is the software to run the blade?

not enough information for me to go on I'm afraid.
how many miners to a pi? it should run stable with 20 miners.
what mode ? scrypt, dual, sha?

It could be anything. Last time it was a bad router or ethernet hub which was causing the problem.

I'm not in front of mine right now..

But - when attempting to login it would loop back to the login screen.  If I entered the wrong password it would spit back invalid creds (red font)...  but trying to retry the good creds, it would almost seem like it would think for a second then just redirect to the login screen, blank out the creds..

I haven't tried a hard reboot (as the hashing was going just fine looking at pool stats).. I figured once my auto 6hr reboot occurred I would be able to get in.. but still haven't been able to.

I may be able to dig more up later if I have time.

Current config - was 18 miners on the PI split into two powered hubs, scrypt mode.  I have 3 other PIs setup with the older version still (havent had time to reflash all card).. no issues logging in to the older ones (going thru same router/hubs/etc).

sounds like what mine did. turned out the disk was full because hashra image logs a ton of stuff and doesn;t seem to cleanup the logs. perhaps it is a result of an older image being updated, but i have a script that cleans the log files now every so often.

I have been told HASHRA BLADE will be available on the support page "in just a few hours"!!!!   ;D

hmm plausible... although logrotate is installed on the image..that should clean the logs every now and then.
you can also mount the image on a linux box and use gparted to resize the partition to 8 or 16 gigs. The 3.8 gig image should have around 1 gig free space.

Not sure if anyone else has had this problem - but after every couple hours I'm unable to log into the web interface.

Curiously I get a "The requested URL /index.php was not found on this server." error message. Seems like something on apache is borked but I can't SSH into the damn thing to do any kind of troubleshooting.

Any thoughts would be appreciated. I'm getting ready to give up and just install raspbian and bfgminer and write a script to autolaunch the miner since the web interface isn't working on this version anyway....

Up and running with a blade but can't push it past 800 Mhz, will you guys be adding more gradual steps up to 850Mhz?

I got my blade as high as 5550 khs at 800 mhz. Seems stable. No HW errors. Nice Job on the software! Thanks.

I seem to have a lot of HW issues with the firmware. I've been mining at Nicehash @850. I have two sets of 10 miners running on the hardware Hashra sent. 10 miners per rpi. Any ideas on what is causing this?
https://i.imgur.com/dPaYodS.jpg
https://i.imgur.com/zNDecqY.jpg

1.4 runs for a few hours then you can't connect to the web interface, I get

Forbidden

You don't have permission to access / on this server.

if you look at the raspberry pi output it's doing this


https://www.youtube.com/watch?v=48bALCHC0qI&feature=youtu.be (https://www.youtube.com/watch?v=48bALCHC0qI&feature=youtu.be)


the miners seem to be still working though

hmm, it looks like the controla files are gone?

we don't officially support hacked images... because now I can't tell what happened to it.

But let's have a go.

can you go to that directory?


are all files there? like the one it's complaining about? monitor.sh ?

also to check if the disk is full can you type in this command?


and copy paste the result here?
The 3.8 gig image should have almost 1 gig free disc space

This is plenty as the logs get zipped and cleaned after a while.

also please make sure you don't use the PI for anything else other than controlling the miner! Using it for other things other than a controller might flood the logs faster than the logrotator can clean.

We have tested the images extensively on multiple devices, on different locations, Hongkong and  Europe ( but only with our own hardware) without problems.

How is it showing up on the pool side? Does your shares go through fine? Are you getting pay outs as expected?

Can you also try another pool? Do you get the same HW? if not then it's pool related. The pool might be mining a different algo coin, like scrypt-n which is not possible with gridseed chips

Here is my history from Nicehash
https://www.nicehash.com/?p=miners&a=0&d=1&addr=192wH2yhWVyjiUkzf2qppnATSvmQkuMsxA

They use a different stratum port for sha and nscrypt. If you compare my log to many of the other miners, mine looks very unstable.
https://www.nicehash.com/index.jsp?p=miners

according to the pool stats  you should be getting around 5.6 btc/gh/day = 0.0056 btc/mh/day = 0.0364/6.5mh/day (assuming you have 6.5 mh)
Today in 12 hours you got paid 0.028 btc already. so it's inline with the pool stats if not better.

I'm guessing the hw errors are the pool sending you scrypt-n hashes which will give an invalid nonce.
Compared to other miners, yours looks normal in my opinion, around 2% mhs reject rate.
I wouldn't worry about it.

It's an unmodified image and when you reboot it works again for a while, It actually got 20GB of space as I gparted it as you suggested it may be the SD card that's the problem I will try it with one I know has worked for over a week

It looks like it can't access that file for some reason, I have a feeling it might be the card aswell.

Hello All,
Dloganbill: How are displaying your pi on your phone? What software/app are you using for that?

you can open controla in your iphone with your phone browser. It will scale itself to display properly on a mobile device.

I ordered a TP-Link 703n and am going to try Lightning Asics firmware.  I'm planning to do a side-by-side comparison of LA vs Hashra with 10 miners each.

I am trying to set up controla now, but can't extract the zips? I am getting the error 'Unknown format or damaged archive' with both the hashra-mini-controla-v1.4.0.zip as well as the hashra-atlantis-controla-v1.4.0.2.zip.

I am on windows, and using winrar, which has always worked up till now.

This is the exact same problem I am having. The PI keeps hashing away though but the web server is not accessible. If I reboot, it works for an indefinite period of time, usually a few hours.

The Pi and SD card have worked together with other images. This seems to be a problem with the image, since more than one person is having it.

I had this happen twice to me... once it was a bad connection to one of the Gridseeds, after resetting all the cables it fixed it... the other time it ended up being a gridseed that went bad, took me awhile to find out which one was throwing all the hardware errors (which is why I wish they showed HW errors per each device in addition to the submitted/accepted).. once I replaced it I've been fine.  I'm running 12 off a single powered usb hub @ 850.  I also have mine restart the miner every 6 hours.  Been rock solid stable the last few days... which is good since I'm going to be gone the next 3 days and I hope they keep going no problems during that time.

I have imaged 1.4 on the card that's been in use for weeks, we will see if that falls over or not

what was the file size? it should be around 1.04 gig. I suspect it prematurely stopped downloading.

How did you track down which miner went bad?  I've noticed one has a fan that stalls out.  If I give it a push, it will start up again, but the next day when I check on things, it has stopped.  The lights seem to be blinking normally on it, so I've always assumed the board was fine and was a fan only issue.

I had to do it the hard way - I started unplugging them one by one and restarting Hashra and seeing if I got any hardware errors after letting run for a bit.. I lucked out and the 4th one was it, after that all the hardware errors disappeared.. (also no difference on the lights, it looked like the others) Now with 12 of them running at 850 over a 6 hour period at most I get a single hardware error, and about a 2% rejection rate which is on par with the pool rate.  If you suspect one already I'd start with that one.

HASHRA, what about adding functionality to assign a pool to each piece of hardware?  (Ex. w/ Blade point Scrypt Blade 1 at Pool A and Scrypt Blade 2 at Pool B)

Yeah, it was around 1.04gb. I tried it three times now, and the last download seems to work. I am writing the image to sd card now.

hey guys,

I've noticed that the pool "running" is green sometimes but after a while it turns RED.  Any idea's as to why it switched from green to red?

I also had to remove backup pools because it sometimes switches to the backup and doesn't switch back to the main pool that I want to mine on.  Anyone noticed something like this?

What pool are you mining on? that pool might be unstable. The whole reason for failover is to switch to your secondary pool when the primary pool turns red.

Thanks for that… Good advice.

The miners are still accepting shares, yet it turns from green to red but still says running! Why red? and what does it mean?

I recently downloaded the new 1.4. I was previously running the 1.331 I believe. How can I get the new username and password?

Any help would be appreciated.

Thank you
Posted from Bitcointa.lk - #7NRbvttgEufWPWX8

It should be the default one.  hashra/hashra

I guess I should clarify, I am trying to log into the PI via SSH... Anyone know that username/pw
Posted from Bitcointa.lk - #8buH1fIAgqgdLcbE

they are keeping the password secret which is sad, I used this info to add the user pi so I am not interfering with the setup

http://rpi.tnet.com/project/faqs/resetpasswd

Worked perfectly.... Thanks I really appreciate it
Posted from Bitcointa.lk - #o92Qv1bpAqkObHJH

I have had controla working fine for two days now. Is there any chance hashra will update it with more frequencies? I used to run them at 875mhz, but now I can only choose 850 or 900.

working on advanced mode, where you can tune each miner individually (no auto tune though)

Since every time I've tried hashra 1.4 across 3 cards and 2 rpi's it crashes every few hours giving me the
"Forbidden
You don't have permission to access / on this server."

I gave up and made my own image with a simple startup script running the new version of CPUminer with autotune.

It now has a text user interface and API json stats output, you should consider using this in the hashra image since autotune is a lovely feature.

(If anyone is interested in my image PM me. It requires configuration by manually editing the startup script to match your setup and pools but, it seems solid and autotunes per-chip.)

I think the new image in some way puts stress on somewhat faulty sd cards that work with other stuff, since I have changed card it's been fine

Curious. All the cards I tried have been similarly generic el-cheapo cards that worked with minepeon. I'll throw a sandisk at it and see if that helps.

I'm using 1.4.0.1 with a blade. For me, it is stable as a rock. Up and running almost immediately. Stabilizes after 1 minute or so. Apparently it reads hash rate from the pool (I cannot remember where I saw this, but my pool hash rate is not always similar). I need a link to quote that, but cannot remember where I read it, so treat that last bit as only a possibility. I don't care for the frequency intervals it allows you to clock the miners (as a whole, not per device) at (only 800, 850, 900, etc). It does not graph hash rate, it does not monitor temps (can you monitor temps with Gridseeds?). The log output is kinda rough as it does not maintain the buffer for you to go back and look at items as they pass.

Like I said, it is extremely stable and I am at least happy with it for that. I am going to try Mox's Scripta at some point soon.

Yes the blade version calculates the hashrate differently. It counts the average amount of difficulty 1 hashes being submitted to the pool in 1 second (not taking in to account rejected work).
Other versions of CONTROLA calculates the hashrate by core frequency + the amount of Gridseed chips (calculated by BFGMiner), which is just an estimation. BFGMiner has the amount of chips defined as a constant (not configurable) so it still thinks it's mining with the 5 chip units instead of the blades, hence it shows just 360khs per blade instead of 2.6Mhs. I didn't have the time to fork BFG, change the code, build it for the blade... It's much easier to just calculate the hashrate by submitted shares (just like how a pool would do it).

Any plans to do a fork? Or include the miner Mox is using in his scripta image?

I just updated my mini controlla but haven't seen any changes. Can you start posting change logs here when you release updates?

forking as we speak.

Sorry man, just did some prep work in a development branch, no new functionality yet, I forgot the detection script looks at the whole repository, not just one branch.

Niceman from Coinmine.pw changed up somethings on his pool to optimize it for BFGMiner. I ran my gridseed minis and blade last night and had close to 0 rejects. Pool ran super smooth. Give that pool a try with Hashra Controla and let me know what you guys think.

Thanks

Made a fork of BFGMiner 3.10.0 (not 3.99.0, that version is a lot slower then 3.10??? anybody experiencing this?)

added support for loads more frequencies (838 is in there)
added an extra bfg parameter --gridseed-chips (default 5) but is set to 40 for the blades. So hashrate calculation will be local hashrate instead of pool hashrate

This will all be in CONTROLA version 1.4.5

I have gridseed minis on 1.4.0 and run same speeds as 1.3.0
Only ever ran blade on 1.4.0.1

I will update it all when I get home. Thx.

I am running the hashra controlla for blade with a mixed 5 chip 40 chip setup will the new version totally screw this up?

No. shouldn't make a difference, the chips setting is just for local hashrate calculation. If you mix and match devices, the numbers wouldn't make sense anymore though... need to figure out how to display the proper hashrate for different devices in the same list

Just checking - prolly me...

When I load up the web GUI for one of my gseed batches..  on 1.4 it says there is a newer version available.. of course I hit "yes" upgrade.. then it reboots.. and still tells me there is an update available... went through it three times now..  perhaps I need to reburn the image?

wow .. my topic really got popular  :D

btw, now im using the latest gridseed firmware on gridseed controllers, uptime is great, over 4 days since im using it

This is a bug. I have to fix it in the future. Simon (HASHRA) or I will announce when the new firmware is out. sorry about this.

Since no one has announced it yet, 1.4.5 update is available, just updated now  :)

Fantastic update as always, can now set individual frequencies! Great job :)

Is there a changelog of the changes in this release?

Thanks again

Glad you liked it :)

As you can probably tell, it has the advanced tab now, where you can set individual clock frequencies. No need to restart the miner, it can do it in realtime.

And it has support for these frequencies:

600, 650,
    700, 706, 713, 719, 725, 731, 738, 744,
    750, 756, 763, 769, 775, 781, 788, 794,
    800, 813, 825, 838, 850, 863, 875, 888,
    900, 913, 925, 938, 950, 963, 975, 988,
    1000, 1013, 1025, 1038, 1050, 1063, 1075, 1088,
    1100, 1113, 1125, 1138, 1150, 1163, 1175, 1188,
    1200, 1213, 1225, 1238, 1250, 1263, 1275, 1288,
    1300, 1313, 1325, 1338, 1350, 1363, 1375, 1388,
    1400

The advanced tab shows the pool hashrate, so you can immediatly see if the tweaking has helped.

It also shows which miner is giving the hw error. which was missing in the previous version

It has a modified BFGminer with support of the above frequencies + blade support (40 chips per blade) for local hashrate calculation.

I was just about to make a comment how rock solid the 1.4 release has been (20 GSD >1 RPi) and you go and update to 1.4.5! Amazing. Just seeing if it's available for the mini GSDs... it is! I'm going to wait for someone else to try this out, yup I'm a big baby like that :D

the individual cpu tweeks are great most of the minis will run at 875 with no hardware errors the blades at 850 with minimal errors.

Quick question as the miners set themselves up in a different order on reboot does are the individual cpu speeds set to the serial of each miner or the listed miner?

Also as I can see which is the blade the serial on both is 48..... (the mini are all 6d.... or 8d.....) me being able to set 5 or 40 chip to correct the display would be nice.

Does 875 bring any hashrate gains? I was under the impression that increments of 50 was the best way to go, although that could be attributed to older versions of mining software.

The clock settings are mapped to the serialnumber of the miners. The chip amount setting is now an all or nothing deal I'm afraid, no individual configuration for that part. If you want to see a representative hashrate you can switch to the advanced tab.

Can you work with Nicehashdev from Nicehash to make your software more compatible? I get over 28% rejects there.

Unless the changes were made recently, when I tried it couple of weeks back, there was allot of rejects.  I tried the Canadian server thinking it will be closer and better for me being in Canada, it was worst than the US server.

I hope the change is recent.  Will give it a try.

Maxzilla,

When mining on a pool, I mentioned a while back that it turns red but still saying running.  I tried this on several pools.  Including wafflepool which Hashra does it's testing on, and I still get that.  It doesn't stay green.  Any ideas?
The other question I have is, will I be able now with the new firmware to up the hash rate from 850? As you mentioned earlier to me that the higher rates are for modified gridseeds.

I have never seen it myself, Where are you located? in canada? (maybe it's the internet connection) The red colour means the server is dead temporarily. I don't think it will show the server as running, if it does, then it's a bug. can you make a screenshot when this happens (with the syslog visible)?
I'll have a go at nicehash and test it myself

GREAT!  ;D

Seems most of you have already found out but yes…. please now update!

Should now be on version 1.4.5 for your CONTROLA.
This is for BLADE, MINI and ATLANTIS.


We have now added more frequency options. (Magic number for BLADE is 838)

Advanced settings section giving individual clock speed control.

New drop down menu for easy selection of clock speed.

Now comes with per "Miner" control.


Good Luck!  :)

I love the improvements! I've thought of a few features I'd love to see added:

• Implementation of Sandor111's(Siklon on GitHub) auto-tuning cgminer: https://github.com/siklon/cpuminer-gc3355 (https://github.com/siklon/cpuminer-gc3355)
• Graphs for hashrate, shares, HW errors etc
• An average of hashrate reported by the pool
• Downtime per pool
• The ability to set x hours mining a pool before disabling said pool
• Notifications for new updates
• Temperatures? I don't know if it's possible but it would be a great feature

+1 on this.  I would also like this to be enabled for scrypt only mining.  I have used it with a TP Link 703N and it is very stable and MUCH fewer rejects.

And while you are looking at improvements, check this link out regarding BFGminer:
https://bitcointalk.org/index.php?topic=562238.msg6560478#msg6560478

many of the rejects on nicehash are missing jobs which you get paid for if you look at your nicehash page you will see the rejects are far less.

I wish that were always true.  Pool side rejects range from 5-25% and sometimes spike higher.

how to update ?
should we use update menu or download firmware image ?

I am guessing use menu. Not on website yet.

He made the changes on May 1. Im on on coinmine.pw. One of my 20 gridseed mini setups is running at 7800+ Mhs on 863 setup. 18 hw but no rejects yet.
My blade setup didn't like 838. I have blade 1 at 813 running at 2.85 and blade 2 running at 800 2.68. If I push blade 2 to 813 it drops to 2.45.

Took the plunge and updated to 1.4.5 about 12 hours ago. This update ignores your reboot miner function and resets it back to zero in the background, but it still shows your X time. Changing it, and changing it back fixed it and now it's back to rebooting after a specific time.

GUI wise there is now duplicity. The whole dials look can now be removed, and use the advanced tab as the main control panel. You could add a 'lock/unlock' button for messing around with frequencies. Possibly using less resources being gobbled up by your front end on the RPi?

Otherwise a really solid update, nice one.

I updated and now I cannot login. Login button is dead.

EDIT: I got in now, no explanation why. Cannot reproduce. Upon getting to the dashboard, blades are showing offline. Any attempts to make changes are met with long delays, sometimes not even processing changes.

EDIT2: I had to reimage to get mining again, but upon doing so started experiencing an error I've experienced before and I want to find out more about it. Since we aren't allowed to touch the underlying filesystem (shame on you guys!), how can we fix name resolution problems?? I am hooked straight to a router with no problem with other devices


What gives? This almost always happens upon reboot.

Is there a D/L link for 1.4.5 anywheres?

http://hashra.com/support/  ?

There is no img for 1.4.5

If you don't have version 1.4, you can download the img first and then click on the update controla link

I have a card for 1.4 but I wasn't running it because I have one gridseed that runs well at 1000mhz while the rest need 850 - so I was using an auto-tuning image to achieve that.

Now that hashra supports per-device speed I'll give it a shot but I was hoping to set up the card before even booting it. Not a big deal though! Thanks.

I downloaded "hashra-firmwareimg-v6" today as I couldnt get any other IMG files running with these GS

Straight in, away we go and theyre sitting stable at 362Mhs scrypt only mode.

I -did- do an update as soon as I logged into it by calling the IP from my laptop, and its stable, 4 hours later...

** just trying to find out how to add backup pools **

I don't think that version has failover yet. You can download the latest img from the hashra support page. the MINI and ATLANTIS are versions for your gridseeds I think. ATLANTIS is scrypt only

New version firmware doesn't restart when you set a time under settings!


Anyone noticed that?

I noticed that... still trying to figure out why that is. Apparently there is a workaround for this a if you read a few posts back.
Changing the number, save it, and then change it again or something.

I tried that too.  I'll give it another try and see if it does it and update you.  I got the pics for you for the status going RED. but I don't know how I could attach the pics here.

Great work with 1.4.5!  The individual settings and showing HW errors for each device is awesome, I've now been able to tune each miner almost perfect, maxing out each ones optimum setting. Interesting how some devices I can run at 900 with no errors, and some only at 850.

I know it's a real long shot and not required, but any chance of adding options like load-balance for mining with multiple pools?  I use this option with no quotas set for my GPU rigs and it works real well maxing out the work each rig does, and I can even mine different ones at the same time by sharing my hashrate and letting it pick the most efficient one.  Thanks for your hard work on this!

Good news Ladies & Gentleman…

We have now decided to release the SSH login details for the Gridseed Based products using the CONTROLA Firmware:

USER: pi

PASSWORD: 3K4Hb8FMeZjQZJEX6scYzZa

ENJOY!  :)

thank you!

what command do you use to reboot this thing? Im unable to login to the web interface an tried to reboot it via ssh. I tried sudo shutdown -r now and it says its shutting down but never does...

did you try just sudo reboot?

For anyone interested, I did a 24 hour head-to-head test against a new RPI setup called Minera.  Results in thread linked below.  Spoiler Alert: Hashra won this round.
https://bitcointalk.org/index.php?topic=596620.msg6624743#msg6624743

I think your pi is flooded. How many miners are connected to it?
before rebooting, can you also run this command?


This is like the windows taskmanager, what is hogging up all the resources?

I have 22 seeds connected. It seems to run fine for a few days and then will not allow me to login, although it continues mining just fine.

yea, that might be the problem. I don't know why but the pi becomes unstable when there are more than 20 miners connected to it. It's not logging in because it can't process the request properly. 20 should be ok though. I connected 25 on 1 pi once, I can log in, but the pi becomes horribly slow

i know I have seen you and others mention the 20 unit limit, i just assumed 22 would be fine. I'll try removing two and see what happens. I have a second pi but I wanted to run them all from one if possible.

Its odd how much processing power is required to manage miners. The pi is a fairly powerful system and you would think it can handle dishing out requests (or whatever it actually does). I have an older Core 2 Duo system with win7 and Bitcoin Core, solo mining with 7 Block Erupters and it brings that system to a halt! Its insanely slow while mining!

Thanks for the info tho, i'll give it a try!

I also find this strange.  A TP Link 703N can handle 50.
https://bitcointalk.org/index.php?topic=554542.0

If your RPi is not dealing with a heavy load and providing your running the unit on a good power supply, just overclock the RPi,  overclocking is now built into the standard OS Hashra has built their image on just login via SSH, and run:

sudo raspi-config

The RPi config screen will be shown, just choose overclocking and pick an option, this will not void your RPi warranty.

when is 1.5 dropping

how can we autoconnect wifi from restart?

With 20 GSD connected, after 24 hours unable to login via web interface but hashing away in the background. Here's the top output

https://i.imgur.com/1yVnBgv.jpg

Anything out of the ordinary?
Is it possible to force restart RPi every 24 hours without superuser via cron?

I have a noob question, I've been using several grids on windows and they all work fine.  I ordered a few pis to hook the grids up to for testing and I am having all sort of strange issues.  This is what I have so far.

latest scripta image, can load into the web interface for a few minutes then internet lights and connection cuts out.
latest hash-master image, internet will not cut out but will not detect my gridseeds whether connecting 1 or 2 directly into the 2 usb ports on the pi or thru an etekcity 2.0 hub same thing.
latest hashra controla image, boots up fine, sees 1 grid but then loses internet connection and can no longer access the web interface.
I accidentally unplugged all usb from the pi and internet connection stays on forever, I was able to update the controla to the latest update and set all the pools etc.  the min I plug in 1 gridseed into it, internet connectivity will cut out after a minute or so.
I was able to get the scripta image from the litecointalk forum to see 1 grid and hash.  however when I plug the 2nd one in and restart, it will not find any of the gridseed and will lose internet connection.  network lights go out on the pi.

This is really frustrating, what am I doing wrong?
I have tried 10 different raspberrys and 5 images on different sd cards, those are not it.  the grids were working on the same hubs in my windows machines.  Any help would be appreciated.

How are you powering your Pi?

with the usb wire that goes into the wall.  looks like an iphone charger except usb on 1 end and plugs into the square socket to plug into the outlet.
got scripta to hash fine with 1 grid, when I put a 2nd grid into the other usb port, both will not detect and shortly after going into the web interface, onboard Ethernet stops working. only way is to unplug and plug the power to get back in with 1 grid connected

forgot to mention after i remove the scripta sd card and put the latest control sd card into the same unit that was mining.  when hashra boots up.
in the log window i can see it found GSD 0 however it does not show under the graphical interface, there are no grids listed to the left.  Also after 30 sec ethernet disconnects and the lights go out on the pi, only the red power light stays on and occasionally flash red or free i forget,  but the ethernet light stays off

also forgot to mention, i do not think it is defective merchandise as we have a couple hundred grids to try, 10 raspberry pis and 5 extra sd card that i am burning various images on.  got several usb hubs to try as well.  thanks for the help

Unfortunately I can't login, I'm getting an access denied. More people with that? I've updated to the latest version (if that matters)

SSH login or CONTROLA login? the CONTROLA login through the browser is hashra/hashra

SSH

What version of CONTROLA do you have? if it's lower than 1.4.0 then you're using an older img with a different password.
You can download the latest img from the HASHRA support page. That img has the aforementioned password

Hero! That explains a lot ;)

I'll update my rigs tonight, thanks man!

Has anyone had success using a wireless dongle on the rPi with Controla?

I've tested my rPi with a single Gridseed, directly connected to my router, and it seems to hash successfully. Although, the Controla web page is really not accessible while the Gridseed is hashing (I can see the results from the pool side however).

If I try this very same setup, but with a wireless dongle instead, Controla doesn't even recognize that there is a Gridseed attached.

I'm thinking that maybe the wireless dongle is overloading the USB interface on the rPi, but I'm pretty new to the rPi. I did try the same test with a Scripta image and had the same results basically.

This is the wireless dongle that I have been testing: http://www.amazon.com/dp/B00FADTN14/ref=pe_385040_30332190_TE_M3T1_ST1_dp_2

Here are the results from my head-to-head comparison against Hashra.  I have two identical RPI setups with qty ten 5-chip miners each.  Since there is no way to distinguish between rigs on Nicehash's website, I used my BTC address for Hashra Controla and Michelem's donation BTC address for the Minera controller. 

Hashra's Dashboard and Nicehash stats
https://i.imgur.com/lC9WPJzs.png (https://www.dropbox.com/s/5ij4f8z5vvbr4g0/HASHRA%20MINI%20CONTROLA%27%3DDashboard.png)  https://i.imgur.com/2Vl3Tu7s.png?1 (https://www.dropbox.com/s/3r8o58ghh4h8jx6/Hashra-NiceHash.png)

Minera's Dashboard, Settings, and Nicehash stats
https://i.imgur.com/QNXG15vs.png (https://www.dropbox.com/s/khbaqw68ng5idtg/Minera%20-%20Dashboard.png)  https://i.imgur.com/K9FQg20s.png (https://www.dropbox.com/s/3fiash8qw6a60o0/Minera%20-%20Settings.png)  https://i.imgur.com/km5GNUKs.png (https://www.dropbox.com/s/wgxrv2lzd6you5d/Minera-NiceHash.png)

Looking through the log, it looks like it took about 6 hours for the autotune process to finish.  Minera had FAR fewer rejects and HW.  It's hard to tell from a short run like this which is the ultimate winner, but I think that Minera has a solid edge over Hashra.

Has anyone got Hashra working with DualMiners (usb sticks) ?

Hmm.. I like the graphs..  will try out a copy of this other program.

I have 5 RPIs setup with Hashra at the moment

Nice job

Got an ODD problem I'm hoping someone can diagnose...

Using the Hashra Controla v 1.4.0 image from the Hashra site, updated to 1.4.5 via the web console...

2 days ago, we switched our mining to LTC coins.  After updating the URL to point to and doing a Save and Restart, I saw only 9 of our 11 GridSeed miners come up  (Miners 1 thru 9 came up...).  The remaining 2 say "loading" on the advanced tab.

Last night, I pressed the web button to "Restart" and saw 10 of our 11 GridSeeds come up (Miners 1 thru 10 came up...).

Any ideas what I can do to get all 11 GSD's up?

I noticed it appears the Raspberry Pi seems to be using a specific program for LTC mining that's different from what it uses for other lite coins.


Thanks!

GS

hi greyscale,

Please email to info@hashra.com screenshot of the activity log when you start the miners and we will help : )

HASHRA Team

Love this image...has worked really well for me!  How many seeds can the HASHRA Atlantis support per Rasp Pi??  When I tried to run over 20 on a regular wheezy install it would bomb out after a few hours.

Hi,

The CONTROLA can support 20 Gridseed minis max.

minera works damn good too

minera seems to have problems with the 40chip blades other than that its fine.

BFGMiner 4.0 has been released... fyi

link?

here is story
http://www.cryptocoinsnews.com/news/bfgminer-4-0-officially-released-multiminer-3-0-officially-released-tandem/2014/05/24http://www.cryptocoinsnews.com/news/bfgminer-4-0-officially-released-multiminer-3-0-officially-released-tandem/2014/05/24

so quiet.....  ???

That's because gridseeds are pretty much a discontinued and out dated product now. You can still pick some up cheap, but for the price per Mhs they are not worth it with whats being released now and in the next 2-3 weeks.

Maybe for the pros, but for the hobby miner or somebody just getting their feet wet their still interesting at bargain prices.

What is being released that is better?? aside from knc titan which is not in yet...

I'm interested in an update that would include BFGMiner 4.0

Everyone is talking about the Zeus miner products but no one wants to discuss how far off-target their power consumption is. Considering that against the availability (US Customers have not received any orders) the overclocked Gridseed 80-chip blades are still the best MH/KW/$ at 6.2-7.5 MH. Since SevenGnomes is selling them with guarantees, its worth considering.

Same goes for overclocked 5-chip miners.

I don't think we'll see anything really threatening to the price ecosystem until/if Alpha Tech ships their new 50/250MH miners in July or when KNC ships their big guns.

I've had great luck pushing stock blades to 5.6 using Minera with manual freq. settings.  On the 5-chip side, I just switched back to Hashra after using Minera for a little over two weeks with my 20 seed setup. While Minera was always posting 7.4MH with little rejects/HW errors, poolside at WafflePool responds better using Hashra to the tune of a few hundred KH.

When it comes to stability though, Minera all-the-way.

Hi,

I have 3 Gridseeds and I think I have the same issue.
2 Gridseeds start without issue but the 3rd device never comes up automatically after the reboot of Pi. (offline)
I always need to restart the service manually by pressing "restart" button.

I'm using the latest image downloaded from Hashra website a few days ago.
Updated to 1.4.5.
Once I restart the service manually, all goes well so I guess the power (electricity) to Gridseeds is supplied well.

Can one of you shed me some lights on this?
Thanks!

Cheers,
Otaku

Lots of products.. in fact Hashra who developed this software doesn't even sell gridseeds anymore, so I'm sure they are focusing their programing and development efforts towards their newer products now, I'm not expecting to see any vast improvements to the software for the gridseeds, especially since they have now unlocked them making it easy for others to update modules. We will probably see a version of Hashra that is designed to work with their newer products, but unkown if those will still work with the older gridseed products - they have released different versions so far for each type of hardware.

That should be fixed. Minera should run 8/9 GBlades (16/18 boards) now on the same rpi. (You must have good powered USB hub)

I keep a desktop on my network running teamviewer.

Cheers,

J

Hi.

I’m sorry if I’m annoying someone with this question, but here it goes:
I have a config with a Pi + 2 Gridseed G-blade and changed to HASHRA CONTROLA a few hours ago and I have this issue with HASHRA CONTROLA: I’m unable to “see” my workers on the pool side.
If I look at HASHRA CONTROLA, everything is apparently normal (STAT = RUNNING), hashing like if there’s no tomorrow (best software 4 my Pi till now! No lock ups.).
But… if I look at the pool side, it reports “zero” workers…

At the moment I’m using stratum+tcp://multi.ghash.io:3333 (multipool).

Am I doing something wrong?
Is multipool the reason 4 “zero” workers?
Since I also have some GHS… I’m not sure where my miserable BTC are coming from (GHS or my G-Blades).

Can anyone help, pls? Tks.

Just wondering if there is a Hashra Controla image for Gridseed Blade that will work with the new RPi B+ board. ...

It would appear as though the current image doesn't include the correct firmware ..

Cheers

Have you tried Minera from www.getminera.com (http://www.getminera.com)?? It's legit!

I second that. I ran the controla first but after switching to Minera I got about 10-15% more hashes :)

Hello all,

Does anyone have a download link to the latest release of Hashra as the website hashra.com seems to be down and not coming back up for a while. Either a download link for the newest Hashra or the URL from the update section on the web GUI.

-Tom

Here are several downloadlinks for Hashra, don't know if all of them are the newest or are still working: http://cryptomining-blog.com/tag/hashra/

Thanks for your reply :)

It seems there is only one link on there that works and that link is out of date. Do you have the update URL for the latest version of Hashra, perhaps this would allow me to update?

If you dont do you know any other Gridseed compatible software for Raspberry Pi that allows me to mine SHA256 and Scypt?

-Tom :)

So far I've checked both my external harddrives and neither of them have the file anymore. Removed most of the images when I stopped my minifarm of Gridseeds.

Have you tried Minera with adding an extra mining instance for SHA256?