Quote from: jstefanop on June 16, 2019, 05:47:13 PM

Quote from: peetee on June 16, 2019, 01:51:57 PM

Hi everyone. I had a nice long run with my Apollo on 1.0, with few to no issues. About a month ago I moved it to a new location which I visit once a week or so, and upgraded it to 1.1. Since then, on two occasions it has stopped mining. Because this is a remote site, I put an IP-enabled power switch at the location so I could remotely power cycle equipment at the site. Unfortunately, my Apollo is connected to an HP server power supply with a breakout board, which requires me to *also* physically press a button to turn power back on.

Anyhow, on the first occasion I tried power cycling the IP-enabled power switch, forgetting that the breakout board meant that I couldn't get the system restarted. So I don't have much diagnosis to go on. But on the second occasion when it stopped mining, I happened to be at the remote site. Before power cycling it, I could not get into the Apollo at all -- it wouldn't respond to SSH, ping, etc. It was down hard. I can presume, but cannot confirm, that the first lockup was similar.

I've since rebooted it and it is now mining successfully again. Is there anything I can look at -- log files, journal, etc. -- that may help diagnose what caused it to lock up? I had several months of successful running on 1.0 with no issues, and now two lockups on 1.1 within a month. (It may be mere coincidence, I'm just pointing it out.)

I'd like to get to the bottom of it, since I won't have the ability to remotely power cycle this thing except on weekends... until my Futurebit PSU shows up :-)

Could be your SD card starting to corrupt, which a re-flash would fix. Can you have someone physically check the device and see if its stuck on a red light? That would indicate some sort of hardware fault (Fan issue/MCU or ASIC overheat etc).

Thanks for the reply. If it happens again, I'll let it sit until I get to lay eyes on it myself. I just re-flashed it recently to 1.1, so I'm less inclined to think it's the SD card. We'll see if it happens again, and I'll report back.