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

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.

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.

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.

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?

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

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

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.

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?

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.

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

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

Scrypt ,Clevermining, 850mhz

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.

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.

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

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

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

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

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.

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?