0 GH/s 00000-000000-000000-00000 S5

[SunnyIgor]

wtf

just hw errors tried everything
different controller board
different cabels
different freq

I don't know what could be the problem....

I could try differnt pool,
once had an s1 that did the same but only on nicehash.

[1715279323]

1715279323

[1715279323]

1715279323

[pj40]

wtf

Obvious questions...

1. Latest firmware?
2. Pool information correct?
3. Tried a reboot?

[SunnyIgor]

just updated first post

[pj40]

just updated first post

What kind of PSU are you using?  Are you using all 4 PCIe cables to power it up as well?  Is this a new(used) unit to you or did this just start happening?

Also, do you have pools defined on MRR?  You need to have a pool defined in the webui there otherwise your miner won't hash through them.  I don't know if it would fail over to your third pool, kano.is, because I haven't tried that.

[SunnyIgor]

just updated first post

What kind of PSU are you using?  Are you using all 4 PCIe cables to power it up as well?  Is this a new(used) unit to you or did this just start happening?

Also, do you have pools defined on MRR?  You need to have a pool defined in the webui there otherwise your miner won't hash through them.  I don't know if it would fail over to your third pool, kano.is, because I haven't tried that.

this is one of the last of 20 s5's tested same psu (lepa 1600) and config
so there should be no problem from those things

[VirosaGITS]

just updated first post

What kind of PSU are you using?  Are you using all 4 PCIe cables to power it up as well?  Is this a new(used) unit to you or did this just start happening?

Also, do you have pools defined on MRR?  You need to have a pool defined in the webui there otherwise your miner won't hash through them.  I don't know if it would fail over to your third pool, kano.is, because I haven't tried that.

this is one of the last of 20 s5's tested same psu (lepa 1600) and config
so there should be no problem from those things

Pool info seem to be correct, since they read as alive. You could still try different pools but anyways;

Swap one board into a working S5. If it still read dead, then test with the other board to be certain but it sound like it could be possible that both board are dead.

[SunnyIgor]

swapped psu's now somthing like:
xxxxxxx-xx0xxx-xxxxox-ooxxx

just hw and no hashrate

guess I will add them to the pile of dead boards

[VirosaGITS]

swapped psu's now somthing like:
xxxxxxx-xx0xxx-xxxxox-ooxxx

just hw and no hashrate

guess I will add them to the pile of dead boards

If they are really dead then i guess thats too bad. At least you can get something back for dead S5 boards. Just wondering if those are actually dead. Let me know if you need to know what to do with your dead boards.

[GriffinHeart]

Have you checked your pool's settings, make sure that it actually works?
Also, the boards might actually not be dead, just run power tests on each side of them. I wonder how both could break, possibly a power surge? This whole situation seems quite queer to be honest. Are you sure of your vendor who sold you that miner?

[J4bberwock]

swapped psu's now somthing like:
xxxxxxx-xx0xxx-xxxxox-ooxxx

just hw and no hashrate

guess I will add them to the pile of dead boards

If they are really dead then i guess thats too bad. At least you can get something back for dead S5 boards. Just wondering if those are actually dead. Let me know if you need to know what to do with your dead boards.

Mine, they are all mine

I've offered what I believe is a fair price for the dead boards.

[usenet]

It is a symptom of a damaged hashing board. A huge number of errors and string 0X. Of course, the speed of either 0 or half the nominal speed suggest damage both or one board.