Topic: Innosilicon releases A9 Zmaster 50ksol/s Equihash miner at 620W - page 25. (Read 45686 times)

Miners, I need help.

I am going crazy.  

Every single day 1 or 2 out of my 5 A9 miners goes offline and then I have to drive to the mining site to power it off and then turn it back on. Then it works fine. The worst is when this happens at night because then it's not mining for 8 hours until I wake up the next day.

It's driving me bonkers because I never know when it will happen.

Can anyone please help me and tell me why this keeps happening.

It's completely random and not the same miner every time. It happens to all of them. Sometimes it's 1, other times it's 2 at the same time.

Please help.

I see this pop up in my logs too...but my miner still hashes at advertised speeds.  This could actually point to a SPI bus issue if Innosilicon said it was a bad hashboard.  Anyone else see this in their logs?

As much as I've been trying to fault the SPI as a possible problem on these unit. I've been ignoring this, since it always comes after a work restart request/New block found. Happens on my Good and Bad unit at the exact same time since they're in the same pool. But Maybe chip resetting relates to the slow units somehow. Im surprised Inno told the one guy to send it back when its hashing properly. Pretty sure that was a mistake.

Can anyone help with this?

Miners, I need help.

I am going crazy.  

Every single day 1 or 2 out of my 5 A9 miners goes offline and then I have to drive to the mining site to power it off and then turn it back on. Then it works fine. The worst is when this happens at night because then it's not mining for 8 hours until I wake up the next day.

It's driving me bonkers because I never know when it will happen.

Can anyone please help me and tell me why this keeps happening.

It's completely random and not the same miner every time. It happens to all of them. Sometimes it's 1, other times it's 2 at the same time.

Please help.

I would not expect anything positive from Inno. They been absolutely horrendous to work with. You may hear from them in 2 - 3 days. I have never had a worse customer experience than working with them. I asked them to refund my last order because of how long they were taking. They never ship when they say they will.

Hey Everyone,
Stupid question, but I haven't purchased from INNO since Dec. of 2013!

Yesterday I pulled the trigger on the A9 deal.
Can you tell me how quickly you received a response from shipping after confirming wire transfer?

Rough maths show some pretty good returns, especially if the free Sept. batch ships.
I'm game.

I've been hashing ZEC getting 48-55k/sols both sides so it's working correctly just intermittently receive ERROR in log?

I see this pop up in my logs too...but my miner still hashes at advertised speeds.  This could actually point to a SPI bus issue if Innosilicon said it was a bad hashboard.  Anyone else see this in their logs?

I receive same ERROR, sent this to Innosilicon Support:

Jul 31 16:20:58 InnoMiner sgminer[1717]: Got nonce for chain 0 / chip 1 / job_id 1
Jul 31 16:20:58 InnoMiner sgminer[1717]: Accepted 751fc454 Diff 0/95999 HLT 0 pool 0
Jul 31 16:21:00 InnoMiner sgminer[1717]: Stratum from pool 0 requested work restart
Jul 31 16:21:00 InnoMiner sgminer[1717]: [ERRO:2018-07-31 16:21:00.945] ERROR - spi recv data invalid: 04|00
Jul 31 16:21:00 InnoMiner sgminer[1717]: chip 1 clear work failed
Jul 31 16:21:00 InnoMiner sgminer[1717]: [ERRO:2018-07-31 16:21:00.974] ERROR - spi recv data invalid: 04|00
Jul 31 16:21:00 InnoMiner sgminer[1717]: chip 1 clear work failed
Jul 31 16:21:01 InnoMiner sgminer[1717]: [ERRO:2018-07-31 16:21:01.031] ERROR - spi recv data invalid: 04|00
Jul 31 16:21:01 InnoMiner sgminer[1717]: chip 1 clear work failed

support said Hashboard is bad, ship Hashboard back, no additional explanation?

I'm getting lots of these errors frequently, it's always chip 1:


Firmware is latest.
Seems the firmware update didn't work altho it indicated success & rebooted.
Version is still b29+_20180706_042116

I have had great experience with my A9.  It hashes at around 51-52ksol/s depending on the pool Im connected to.  Some pools work terribly with ASICs still and I think some of the people responding in this thread are using bad pools...

Other people in here do seem to have legitimate issues with some of their cards, though

Also, I purchased mine through a reseller so I cant help with your other questions...but yes I do believe that is the real innosilicon website as that is where I download my firmware from.

It wasnt very helpful, I was hail marrying. but for the sake of education/experimentation I'll share

I killed cgminer process with

systemctl stop cgminer

and ran directly from SSH, this would throw error msgs for bad commands and was easier for messing around. I'd use CTRL C to quit
This chain chip limiting command worked. never tried messing with the clock values, as im not exactly sure what clock it would be changing. I didnt error check this but it was something like:

cgminer -o stratum+tcp://us-east.equihash-hub.miningpoolhub.com:20575 -u USER -p x --api-listen --api-port 4028 --api-allow W:127.0.0.1 --T1noauto --T1Pll1 1250 --T1Pll2 1250 --T1Pll3 1250 --T1VID1 185 --T1VID2 185 --T1VID3 185 --A1Fanspd 100 --A1Fanmode 0 --bitmine-a1-options 0:0:0:6 -debug

How did you use the bitmine commands? I'm not aware of this interface.

Can anyone please post the number of cores reported when you miner initializes?  After PLL Clock and VID is set it comes up in the log.

or by SSH cgminer-api -o stats | sed 's/,/\n/g' | grep 'cores'

My 28ksol:
Num cores=370
Num cores=373
Num cores=373

My 50ksol:
Num cores=384
Num cores=375
Num cores=377


its not exactly a direct relation in performance to core count but im curious if the lower hashing units always have lower core counts.

I haven't Bought a new Oscilloscope yet as im still behind from buying my A9's. Dont even have a good multi meter here. But I see very little variation in 'cgminer-api -o stats' Min/Max voltage and nVol per chip. Its incredibly stable. I would suspect its not updating but I did see a very slight difference in reported value over time in performance mode. Think it was 0.001 Volts. lol.  Over and Under volt does nothing significant to performance. I may have gotten another 1ksol avg from overvolting, but i haven't done a comparison with hard data. Hardware Errors vs Valid Nounces seems to be what I need to compare. Whats crazy is underclocking down to 230Mhz didn't effect the error rate. And the errors are randomly spread across chips in a steady ratio.


cgminer-api -o stats | sed 's/,/\n/g' | grep -E 'found|HW'
00 HW errors=140
00 Nonces found=71
01 HW errors=146
01 Nonces found=74
02 HW errors=177
02 Nonces found=31
03 HW errors=89
03 Nonces found=117
04 HW errors=120
04 Nonces found=73
05 HW errors=103
05 Nonces found=112
06 HW errors=137
06 Nonces found=53
07 HW errors=104
07 Nonces found=118
08 HW errors=146
08 Nonces found=67
09 HW errors=77
09 Nonces found=121
10 HW errors=118
10 Nonces found=102
11 HW errors=61
11 Nonces found=136
00 HW errors=106
00 Nonces found=105
01 HW errors=113
01 Nonces found=107
02 HW errors=125
02 Nonces found=78
03 HW errors=54
03 Nonces found=149
04 HW errors=100
04 Nonces found=121
05 HW errors=100
05 Nonces found=122
06 HW errors=197
06 Nonces found=28
07 HW errors=84
07 Nonces found=138
08 HW errors=13
08 Nonces found=198
09 HW errors=156
09 Nonces found=35
10 HW errors=132
10 Nonces found=87
11 HW errors=179
11 Nonces found=22
00 HW errors=67
00 Nonces found=137
01 HW errors=80
01 Nonces found=135
02 HW errors=204
02 Nonces found=7
03 HW errors=55
03 Nonces found=159
04 HW errors=14
04 Nonces found=183
05 HW errors=63
05 Nonces found=139
06 HW errors=24
06 Nonces found=199
07 HW errors=102
07 Nonces found=98
08 HW errors=64
08 Nonces found=184
09 HW errors=42
09 Nonces found=175
10 HW errors=51
10 Nonces found=149
11 HW errors=68
11 Nonces found=155


So I don't know. My gut says these are bad chips and the supporting hardware is fine. But I cant really know that for sure until I get in there and do some measurements.

I was also playing around with
'bitmine-a1-options 0:0:390:0' to try and limit the spi speed - no idea if it did anything, took the command tho.
'bitmine-a1-options 0:0:0:6' to disable 6 chips in each chain. Workedm I got roughly 1/2 sols. but not exactly as poor hashing chips are randomly placed. Didnt really let it ramp up.