Antiminer E3 not hashing/mining
Greetings!
I just bought an Antimer E3, updated to the latest firmware (E3_V540_0327). However, it won't hash/mine. Here are my settings:
It seems that the pool is getting jobs, but no hash/mining activity.
Kernel log shows: Chain [2] Still Waiting For Flag, Flag[0]->[0], Flag[1]->[0]
Any ideas?
Thanks!
-
1) In USA & colder
2) Awesome MIner3) No issues until Nov & ETH2
4) Wont boot up - reboots consistently around 26 - 28 min during the bootup. Lag time at the 25 to 30 Mark 6000+ms on awesome miner but ping is less then 1ms from command prompt
5) March 2020 Firmware
6) Room Temp 66 F, second room temp 75 F -
I am also having the same problemMiners will reboot after about 30 min - if they last longer then 30 min it will usually boot up
***BOOT UP TAKES 1 HOUR if it does stay online & mineIt is very odd behavior that started about the time ETH2 kicked in
I have 4 - E3's ALL are behaving ths way for weeks Glad to see its not only me
We may need a firmware update???I have same message in kernel logs
[2020-12-12 15:57:36] (03377)->[bmsc_fill_eth_work]: Chain [12] Still Waiting For Flag, Flag[0]->[0], Flag[1]->[1]
[2020-12-12 15:57:38] (03377)->[bmsc_fill_eth_work]: Chain [13] Still Waiting For Flag, Flag[0]->[0], Flag[1]->[1]
[2020-12-12 15:57:38] (03377)->[bmsc_fill_eth_work]: Chain [9] Still Waiting For Flag, Flag[0]->[0], Flag[1]->[1]
[2020-12-12 15:57:42] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-12 15:57:45] (03377)->[bmsc_fill_eth_work]: Chain [1] Still Waiting For Flag, Flag[0]->[0], Flag[1]->[1]
[2020-12-12 15:57:48] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-12 15:57:51] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-12 15:57:53] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-12 15:57:53] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-12 15:58:07] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-12 15:58:11] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-12 15:58:12] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-12 15:58:23] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
-
I have 4 antminer E3's also, all started having issues around the Nov time frame and not running consistently, now I cant even start them. I have put the intakes on top of my gpu card rigs in a rack and taking the heat off of them and also reloaded the new firmware again. I'm awaiting my results 17 min in. And I'm also using awesome miner so T Thompson is the same setup as me. 40 ish min to go. the room is 66F and in our datacenter. I'm from North Dakota and the weather gets very cold up here.
-
So in an interesting turn of events I was able to get one backup and running.
Steps
moved miner to a 75 F room
changed default password
statically set IP address,subnet,gateway, dns to 8.8.8.8
in awesome miner set API access to privileged on the e3
rebooted and waited 1hr 7min for it to come up and it did
I don't know if it was the room temp or what made it come up but it did,
It is something with the firmware for sure. not the dag
I'm trying the same setup in the one in the 66F room and seeing if it works
-
Since Bitmain Antminer will not comment on any thing
POINT ALL E3's to Prohashing_com (stratum+tcp://prohashing.com:3339)
E3's WILL hash at 190 Mh
They have IRS form to fill out at OVER $600 = JUST CREATE A NEW ACCTIt is a great US Pool I completely forgot about
GET PAID IN ANY CRYPTOENJOY I AM ALREADY UP & MINING AGAIN
Configure miner specifically for ETH ETC or Profit Switching
https://prohashing.com/tools/miner-configurator/Ethash
-
Hey,
If u compare V560 from Edmund and V540 from March, they are the same files with same size.
I would expect if there is new firmware, there would by some new files or old but with another size.
Im not a software engineering but for me it makes sense.
Maybe im wrong.
I havent tried it yet but i´ll do as soon as i can. -
Hello everybody. I have been working with firmware 5.6.0 since September, I received it from Bitmain by email when contacting me directly, this firmware does not allow us to continue mining today, this is confirmed by Bitmain specialists. At the same time, some of my E3s worked until December 20.
-
Firmware 5.4
Config: I just set up one pool (no backup ones)
egem.digipools.org:4202
Worker: [YOUR EGEM ADDRESS]
Password: xMore at https://egem.digipools.org/#/
-
Thanks Tthompson7, my E3 works at https://egem.digipools.org/#/
-
We all have the right firmware. Again this issue started showing itself badly around ETH2 implementation.
Around Nov 1 when the temp's started dropping in USA for winter.
This is a E3 issue with the firmware created in March. It seems to me it is having a REALLY hard time doing any thing if it "considers 48 C" too cold.
It will attempt bootup for approx 26 - 28 min & reboot. Look at that kernel log above - that is what they all will say right before reboot - CRC FAIL. It almost seems like now cold weather is here the firmware cant start up the hardware due to cold temps?? Even warming the room does not help necessarily.
Hardware is made to run in cooler environments... why would firmware do that???? Maybe 10 C but not 45 C......Have some one look at the FIRMWARE PLEASE - ITS THE FIRMWARE NOT THE MINERS OR HARDWARE per say. Just have a developer check it & see if they can do "anything to improve it"!? Maybe have a devel review that log & give their input?
Also, can any one answer WHY: E3 firmware takes 1 HOUR to boot up to start mining???? Why 1 hour to boot & mine? An entire 1 HOUR to bootup so it cant start mining?
TYIA
-
Believe it or not I literally caught 1 right before it rebooted. Again, I have 4 E3's - none had problems until Nov colder weather, NEW MARCH FIRMWARE & ETH2. Thats all I can say. I also am a miner of 4+ years with 36 running atm
What I have noticed as consistency:
1) It will reboot if it cant come online at 26 - 28 minutes every time
2) Response Time goes off the wall right around that time. Can start at 50ms & got to 5600+ (**Dont say its the IO card, it is NOT, I have replaced 1 with same exact behavior)
3) My room is at 51 F - E3's running at 53 C - 78 C (1 runs hot) - All 4 can have this issue recently4) Kernel log above is same thing at some point over & over & over no matter WHICH MINER it is - I would love for a DEVEL to review it & give us advice.
HA to answer your Q.... I literally took 1 about 2 days ago & moved it BEHIND my miners - where the air is warmer & after about 30 min to an hour... it did start to come online & has been mining since. No joke, its why I made the suggestion especially if you are in USA & it is now COLD?
1 other thing that may be coincidence is I will upgrade firmware again hoping it triggers something. A couple times miners have started after wards but it may be 100% coincidence.
Good luck keep me posted any one with suggestions please help. Hopefully a devel can enlighten us. We know for a fact we are not the only people experiencing this.
1) Why does it take 1 hour to bootup & mine?
2) Does temperature affect if a E3 can come online??
Images showing everything I just said
(**UPDATE - the Response Time may be coincidence. The miner was at 26 min & ms was very good like 31ms & it just rebooted)??
**Rebooted AGAIN right at 26+ minutes if not running. CRC Check Failed - PLEASE have a devel check these logs/errors "consistently rebooting during bootup at 26 -28 min"
TYIA
-
Nick... awesome & TY for the feedback & input. I have not taken my room that warm "yet" but I will bet you... if those miners have stayed online to 40 min... they will boot up! It may take a few times but once the cards warm up.... I'll be eager to hear.
Please let us know & TY again for the honest input.I had similar issue with S15's & too cold to boot up. Difference was... the Kernel logs actually said it... this E3 firmware does not
Consistencies:
1) In USA & colder
2) Awesome MIner3) No issues until Nov & ETH2
4) Wont boot up - reboots consistently around 26 - 28 min during the bootup?
5) March 2020 Firmware
6) Room Temp 55 FMy 1st pool F2Pool... what about yours?
**Confirmed which Pools do not matter - same behavior no matter what pool tried as well as Nick confirmed Antpool -
Nick, great job and yes.... something in these steps will trigger them to connect
I shut off Awesome Miner 100% at the moment. Not running on 1 pc or even in Task Area.At this current moment, JUST LIKE OTHERS STARTING TO SHOW UP HERE, they are temperamental & may or may not boot up
**WILL REBOOT AROUND 26 - 28 min consistently
At this moment 3 of my 4 are running = 1 wont come on line but sometimes unplugging it will bring it up, reflashing firmware, reboots etc...
CAN WE GET TECH SUPPORT TO SAY & DO ANY THING TO HELP THE GROWING ISSUE FOR THEIR CUSTOMERS?Have your devel read the kernel logs = WE ARE NOT THE ONLY PEOPLE WITH THESE PROBLEMS
And CAN TECH SUPPORT AT LEAST SAY & ACKNOWLEDGE THIS ISSUE ...... Thank you we are working on it???????????Thanks again to Nick & all others trying to get this resolved.
THE E3 FIRMWARE NEEDS REVIEWED -
3 of my 4 are back offline & wont start back up? Just reboot
Come on Bitmain is this the best we get?All 4 went from mining to "LOOKING LIKE THEY MINING" but the Asics were all CC instead of oo
I'll post pic later... its on diff pcNot sure what in the ETH network is causing miners to go offline, reboot constantly & not reconnect but I know I'm not the only 1
Any suggestions or help is appreciated
TYHere is how I knew the E3's ONLY stopped mining... none of my other pools (Antpool BCH Poolin ZEC & DCR Litecoin.org LTC) show this crash?? NONE OF THEM
**Same as NIck's case below... 1 mined until 4days 12 hours then the image you see below - it sent ALL 4 offline - Again Asic show CC they should be oo
The image below that is what the miner looks like... it says its hashing, ITS NOT you can see that by the F2Pool going to 0
-
***Updating Firmware with SD Card does NOT get same behavior as through Web Interface***
Now to muddy the water
1) Update firmware using the SD Card & moving jumper back & forth
2) You will notice the behavior to bootup is completely different
3) E3 will start up bootup ASICs 1 at a time at 6 - 7 min
4) At the 8 min mark some asics will show xx - miner will reboot
5) I confirmed this by doing 2 more E3's 1 at a time... I am about to do the 3rd
6) Again I noticed my ONLY miner still online was dine with the SD CardIf any one can confirm would be appreciated
Looks like we are on our own*****FACTS on testing with SD Card
It did in fact alter the bootup process/behavior
If you update using SD card it will "attempt" to boot the asics at 8 min
And WILL REBOOT in about 8 min after that
I did all 3 remaining E3's this way & all had same behavior
Grew so frustrated last night I took 1 & updated through web interface & let 2 run on SD update & 1 ran on web interface update & the web interface was online & running this AM
The other 2 were not
I immediately updated those on web interface & they still have not connected & do nothing but reboot every 26 - 28 min
So Nick NO... although it "looks like a better option to boot up"
My E3's never did -
nick my update to my comments is above
Still NOTHING from Antminer or Bitmain
At the 26 - 28 min mark this is all the E3's keep saying in Kernel Log
[2020-12-22 17:08:57] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-22 17:09:28] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-22 17:09:32] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-22 17:09:32] (00431)->[_WorkerThread]: CRC Check Failed! Drop!
[2020-12-22 17:09:41] (03377)->[bmsc_fill_eth_work]: Chain [3] Still Waiting For Flag, Flag[0]->[0], Flag[1]->[1]
[2020-12-22 17:09:44] (03377)->[bmsc_fill_eth_work]: Chain [9] Still Waiting For Flag, Flag[0]->[0], Flag[1]->[1]
PLEASE GIVE TO A DEVELOPER WE NEED NEW FIRWARE
请先登录再写评论。
评论
89 条评论