HASHRA CONTROLA on Raspberry Pi for Gridseed - page 6.

fivejonnyfive

sr. member

Activity: 294

Merit: 250

Quote from: bexwhitt on April 28, 2014, 12:42:31 PM

Quote from: fivejonnyfive on April 28, 2014, 11:59:51 AM

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.

bexwhitt

newbie

Activity: 50

Merit: 0

Quote from: fivejonnyfive on April 28, 2014, 11:59:51 AM

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

fivejonnyfive

sr. member

Activity: 294

Merit: 250

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.)

maxzilla

member

Activity: 112

Merit: 10

Quote from: maardein on April 28, 2014, 09:00:12 AM

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)

maardein

sr. member

Activity: 420

Merit: 250

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.

Lossgenius

newbie

Activity: 3

Merit: 0

Quote from: bexwhitt on April 26, 2014, 01:22:38 PM

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

bexwhitt

newbie

Activity: 50

Merit: 0

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

Lossgenius

newbie

Activity: 3

Merit: 0

Quote from: compumine on April 26, 2014, 10:17:50 AM

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

compumine

sr. member

Activity: 252

Merit: 250

Quote from: Lossgenius on April 26, 2014, 09:48:00 AM

Quote from: HASHRA on April 20, 2014, 12:06:59 PM

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.

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

Lossgenius

newbie

Activity: 3

Merit: 0

Quote from: HASHRA on April 20, 2014, 12:06:59 PM

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.

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

compumine

sr. member

Activity: 252

Merit: 250

Quote from: maxzilla on April 26, 2014, 03:50:38 AM

Quote from: compumine on April 25, 2014, 08:46:09 PM

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.

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

HASHRA

member

Activity: 112

Merit: 10

HASHRA - MINING TO THE MOON

Quote from: vaudvaud on April 25, 2014, 04:12:29 PM

Quote from: dloganbill on April 25, 2014, 03:15:26 PM

Quote from: vaudvaud on April 25, 2014, 02:01:17 PM

Quote from: dloganbill on April 25, 2014, 12:02:39 AM

I seem to have a lot of HW issues with the latest 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?

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.

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.

Thanks for that… Good advice.

maxzilla

member

Activity: 112

Merit: 10

Quote from: compumine on April 25, 2014, 08:46:09 PM

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.

compumine

sr. member

Activity: 252

Merit: 250

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?

maardein

sr. member

Activity: 420

Merit: 250

Quote from: maxzilla on April 25, 2014, 02:11:11 PM

Quote from: maardein on April 25, 2014, 01:24:10 PM

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.

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

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.

lajz99

hero member

Activity: 756

Merit: 500

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)

vaudvaud

member

Activity: 60

Merit: 10

Quote from: dloganbill on April 25, 2014, 03:15:26 PM

Quote from: vaudvaud on April 25, 2014, 02:01:17 PM

Quote from: dloganbill on April 25, 2014, 12:02:39 AM

I seem to have a lot of HW issues with the latest 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?

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.

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.

dloganbill

full member

Activity: 126

Merit: 100

Quote from: vaudvaud on April 25, 2014, 02:01:17 PM

Quote from: dloganbill on April 25, 2014, 12:02:39 AM

I seem to have a lot of HW issues with the latest 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?

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.

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.

maxzilla

member

Activity: 112

Merit: 10

Quote from: maardein on April 25, 2014, 01:24:10 PM

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.

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

bexwhitt

newbie

Activity: 50

Merit: 0

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

Topic: HASHRA CONTROLA on Raspberry Pi for Gridseed - page 6. (Read 39584 times)