Author

Topic: Avalon controller restarted, how can I find root cause in the logs (Read 167 times)

jr. member
Activity: 50
Merit: 1
Mining since 2018
I really appreciate the input, so thinking ahead, it’s best for to have a spare controller, spare SD card with pool settings and spare RPi wall wart ready to swap out; if needed.

Thanks to all who gave insight into cause and how to react to any future event.

Happy Mining.
legendary
Activity: 3500
Merit: 6320
Crypto Swap Exchange
fanatic26 is correct in most of the time the reboots are power related.
BUT I would say it's only 95% of the time.
SD cards go bad a lot too. I have several pieces of equipment run by RPi, not just miners. 1st thing to check is the power. 2nd thing to do is burn a new SD card.
That is if it's a "name" brand SD card, the cheap no name ones are truly bad.

But one random reboot here and there is not a big deal.

-Dave
hero member
Activity: 756
Merit: 560
I have managed a cumulative total of over 10,000 Avalons in my career and 99% of the time when an RPi reboots its because of the power brick you are using. Make sure you are using a minimum of 2 amps and make sure it is true power and not a chinese knockoff 2 amp that is normally only around 1.5
legendary
Activity: 1554
Merit: 2037
Unless it becomes a problem where it starts to happen a couple times a day it's a real non issue.

I think mine had done it 2 times in the last 3 months. Everytime it restarts and goes about it's business.

I got worried the first time because I got a pool notification, and by the time I got to my setup everything was fine. So I stopped worrying about it.
hero member
Activity: 756
Merit: 560
There is no real logging setup for the RPi. Sometimes reboots just happen, you lose like 1 minute of mining time on a reboot, not really worth expending a bunch of effort on figuring out what happened.
jr. member
Activity: 50
Merit: 1
Mining since 2018
Help please.
I know my cluster of 741s restarted  2 hours ago, I’m guessing the controller restarted, where can I find the event and trace the root cause the logs?
Jump to: