Post
Topic
Board Hardware
Re: HASHRA CONTROLA on Raspberry Pi for Gridseed
by
nogdog21
on 16/04/2014, 20:28:55 UTC
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!