2 problems with S9 - need help | Bitcointalksearch.org

Raymond_B

member

Activity: 504

Merit: 71

Just Getting Started...

Quote from: MedvedTrader on March 31, 2018, 11:09:56 PM

I use a short (3ft) standard Cat5 ethernet cable, but it comes from a TRENDnet Powerline adapter plugged into a 110 power outlet (with the other TRENDnet Powerline adapter plugged into my router). The connection is there when there is no hashing - I can reach the S9 on the LAN no problem.

I didn't save the log but IIRC, didn't see anything alarming in it. Had stuff like:

Check Chain[J8] ASIC RT error: (asic index start from 1-63)

but all the chips seemed to be showing as working on Miner Status although the Status of the Pool Connection was showing as Dead. Next time this happens I will save the log...

I will also save the log next time I reboot and it takes a long time.

Just an FYI, but Slush had some AWS issues last night and all my miners failed over to their EU address. Failed back this morning after it was fixed.

MedvedTrader

newbie

Activity: 25

Merit: 1

I use a short (3ft) standard Cat5 ethernet cable, but it comes from a TRENDnet Powerline adapter plugged into a 110 power outlet (with the other TRENDnet Powerline adapter plugged into my router). The connection is there when there is no hashing - I can reach the S9 on the LAN no problem.

I didn't save the log but IIRC, didn't see anything alarming in it. Had stuff like:

Check Chain[J8] ASIC RT error: (asic index start from 1-63)

but all the chips seemed to be showing as working on Miner Status although the Status of the Pool Connection was showing as Dead. Next time this happens I will save the log...

I will also save the log next time I reboot and it takes a long time.

philipma1957

legendary

Activity: 4256

Merit: 8551

'The right to privacy matters'

how long is the ethernet cable?

is it cat 5 or 6 or 7?

tim-bc

full member

Activity: 538

Merit: 175

During a time when the S9 is not hashing to slush, can you still ping it? If so, look towards the bottom of the kernel log for fatal errors. Sometimes, you will see two different "fatal error" messages repeating. For example, one line might say "Fatal error: fan lost!" and the other be like "Fatal Error: network connection lost!". I have seen a lost network paired with fatally high temperatures (>125C) as well as with a fan that has died. Basically, if a fatal error arises sometime after the boot cycle is complete, the miner will drop the ethernet connection and flash the red fault LED, even if the miner could still be hashing.

Your issue #2 sounds strange. While the miner is booting and the status page is blank, you can still view the kernel log and observe anywhere that it hangs or spends excessive time. 2 hours is rather extreme, 15-20 mins should be the max. You can also tail your dhcp/dns just in case you have a network issue.

MedvedTrader

newbie

Activity: 25

Merit: 1

1. Twice in the last two weeks the S9 just lost connection to slushpool. Internet connection is fine, the S9 is functioning correctly, all the boards are ok, the ethernet connection to LAN is obviously fine since I can access it, it just doesn't connect to slushpool. First time that was for 2 days before I noticed, so it doesn't correct itself.

2. ... and could be related to 1 - when I rebooted, both times it took more than 2 hours to start hashing. Before that the Miner Status was showing blank - no boards, no stats, nothing. No BMMiner version on the system page either. After 2+ hours it started hashing.

So - what, other than a reboot, can I do with (1) - and why does (2) happen when I see that others see it hashing 20 min after reboot?

Thanks.

Topic: 2 problems with S9 - need help (Read 159 times)