Topic: A4 Dominator - Pre-Order Group Buy - 280mh, roughly 1000w, $1800 + shipping - page 14. (Read 122571 times)

If L3 is anything like S9 you gonna all what you saved for reapairs and shipping miner back to China. When thinking about Scrypt vs SHA256 and ETH/equi Scrypt is least affected by electricity prices, so unless you mine just LTC you can gain money even with elect prices. So L3 gain over A4 is much smaller than for example S9 vs it's competitors.

If L3 would like 1kW and 450MHash/s that would have sold me, now i don't think so.  A4 still pumping hard.

So what's the average for users now? In terms of speed, uptime and stability? Does anyone think inno might lower the prices considering bitmains new miners seem very solid and stable? I'm leaning more towards bitmain but always open to get persuaded back to inno

Pool problems, Dropped boards? Nicehash?

My a4 will hash great at rated speed for a couple days and then speed drops by almost 100 mhs. Not sure the cause...

Update on this, ran fine for 3 days then yesterday around 5am this problem started again. I didn't catch it until today. I again deleted the cgminer.lock file and rebooted the pi manually as mentioned above and it seems to have corrected the problem for now...

Lost 24 hours of mining because I wasn't watching it...

I guess next step is to take another copy of 2.0.2 on an SD card and go swap it out.

Anyone know of a good way of changing the default IP address without a 2nd Pi to change it from? I can see the necessary files in the image but can't find a successful method of editing it from Windows... maybe it can be done from Linux?

Update:

I have shipped the Jig on to the next person.

When I received the Jig, the card inside had become detached and was only being held by 1 corner of glue. At the direction of Innosilicon I re-secured the Jig before shipping it to the next person.

I used specific flexible adhesive hot glue and not regular hot glue as the hot glue previously used got hard and had come off during the 1st shipment.

Images of the repair are in the Jig Reflash Thread: https://bitcointalksearch.org/topic/m.17472203

Best I can tell it's a temp file that gets created that contains information while the miner is running.

From my research, when the raspberry pi reboots, its supposed to clear the tmp directory. However when you just flip the power switch and shut it off, the Pi doesn't have the opportunity to clear this file. I only recommend doing this if you're having issues getting your A4 to mine or if its in a 5 minute reboot loop like mine was.

I took a guess and manually cleared the file/directory by performing the following steps.

1. Make SURE the miner is stopped (note: I had issues with the thing starting itself up even with Manual Start configured)
2. SSH Into the Pi
3. Navigate to tmp directory in the root
4. Clear contents of tmp directory with command
5. Restart the miner

I observed this file was re-created when the miner started again.

Over 16 hours now since I did this and its working fine again.


If you notice I also set the time/date correctly on the Pi finally so that's accurate in this screen capture.

Yes, check the 'Get Failures' stats for Getwork failures first, and then look at Pool Rejects for high Pool stales.

Questions:
1. what is the function of cgminer.lock?
2. what event possible triggers occurrence this cgminer.lock?
3. do we need to clear tmp directory regularly?

Thanx for this. Bookmarked this

Think I figured it out.

Had to SSH into the PI and clear the tmp directory which contained a cgminer.lock file

Once I cleared that, it appears to be running normally again... almost 10 30 mins now without a reboot and prior it would reboot around 5 minutes like clock work.

Owners of the A4, I recommend you take note of this because if it happened to me, its bound to happen to you -- All I did was power it off and move it.

Can try reseting PI and also reformating SD card adding new image.

Something is definitely up with 2.0.2 or the image I have installed.

I have it set to manual start and the miner keeps auto starting itself while I'm trying to work on the pi. If i'm not watching it, once it gets to about 5 mins it reboots itself.

I guess I need to put a fresh copy on another SD Card and try that but for now I'm trying to figure out why its doing this.

Guess you have to msg Inno or someone smarter than me with Pi.

Already did that before I left the site, did it twice in fact.

Did you do hard restart. By shutting down PSU and unplugging it? Just to be sure

Network is different yes but I used this same A4 onsite for weeks before I reflashed it to B3, ran it for a week at my home, took it back, now this.

Nothing has changed network side and I honestly don't believe its the PSU.

I just got back to my computer and literally it runs for just over 5 minutes and then reboots itself, doesn't make any sense. It's like a timer is kicking it to restart even though its hashing normally.

Something is up with the Pi is my guess or the image the system the SD card has.

I was SSH Into it during one of its reboots and got this. Then it disconnected me.

I also vote on network. Had similar issue just yesterday.

So basically all started 3 days ago. Was happily minning, when internet went down. Turns out ISP antenna broke during storm, and as a normal Eastern Europe company nobody works during evening and etc. So that crap was fixed next and broke down again after 4 hours. ANd finally it got fixed next day. So until i went to sleep miner did random restarts sometimes 10 mins apart, sometimes one in hours. Internet on computer also was wokring like good, good and then started to lag.  Guess they or it itself fixed over night so i had like one small restart today (hash spike didnt even go to 0 in MRR, oposed to yesterday's drops where it was like 3 minutes not hashing.).

P.S. can try doing hard restart, turning PSU off. But it didn't help this time. Helps with dropped cards, if it happens.

Network would be different as well. Might be useful to do some analyzing of connection latency as well. I'm not sure how the A4 work but perhaps if it thinks there is network issues it reboots as well?

Well Sadly, I may have spoke too soon.

My A4 ran without a hiccup for over 5 days.

Today I shut it down, packed it up and took it to my remote site with better cooling for its full time placement.

I was gonna get a screen cap showing it running for over 5 days but forgot before I shut it down.

Transported the A4 and set it up at new location and it literally runs for 5 minutes and then reboots itself.

The only thing that has changed in this transition is the PSU but the same (2880) was previously running 2 s7's and now is running 1 S7 plus this A4, the S7 is doing fine.

Cards aren't dropping and this whole experience may be coincidence or maybe the PSU is having an issue as its the only thing that changed but either way.... more issues for me to deal with.

While I was typing this I just witnessed it reboot itself again.

That's the 6th reboot in about 30 minutes.

I'm pretty upset right now as this angers me more than words can describe so right now this is just the facts. I will share my thoughts about this later.

Same A4, Same Pool, Same Settings, different PSU and its rebooting every 5 minutes.

My guess its the PSU so I'm going to approach it from that standpoint.

In the interim this thing is probably going to hash upwards of a few days like this with 5 minute reboots... maybe it will magically start working? Who knows.