You might get a decent diagnosis here, but don't waste any time, get your RMA started with Bitmain if that's still an option. It will only drag out if you wait before getting it started. How long were they running before the failure? Sometimes cables come loose in transport so if something isn't seated right it could be reading as dead. I've had minimal exposure to Bitmain gear, but in the past I would lose a chain and not the entire board if there was suspect chip.
Topic: 3 of my miners failed the same day (Read 231 times)
hashboard only have 51 ASIC chips so the 12 ASIC chips might be dead.
Not really, this means most likely Chip number 52 is dead , but regardless, this board is as good as dead, depending on the firmware , but I would say most firmware versions by bitmain don't do well with boards that report anything below 63 chips on a single board.
The 3 images he posted look pretty normal, 2 miners with 2 hash boards, 1 miner with 2 good hash boards and 1 bad hash board, the problem is the part that says
the same day
What are the chances of 3 boards on 3 different miners , get toasted on the same exact day? op did you have any power issues? any chances the voltage has dropped? can you try different PSUs to confirm it's not a power issue? also please post the kernel log for each, use the code format when you post the Kernel log
example :
Code:
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
What do you mean by failed?
What is the issue of the miner?
According to the images above all miners are running but the two miner shows only 2 hashboards and the other one shows 3 hashboards but the 3rd hashboard only have 51 ASIC chips so the 12 ASIC chips might be dead.
Let me ask if these two miners with 2 hashboards only have 2 hashboards each? or they have 3 hashboard but the 1 hashboard not showing on the miners status?
Better explain here what exactly the problem of the miner Because you are still getting hashboard on these miners but with lower hashrate.
What is the issue of the miner?
According to the images above all miners are running but the two miner shows only 2 hashboards and the other one shows 3 hashboards but the 3rd hashboard only have 51 ASIC chips so the 12 ASIC chips might be dead.
Let me ask if these two miners with 2 hashboards only have 2 hashboards each? or they have 3 hashboard but the 1 hashboard not showing on the miners status?
Better explain here what exactly the problem of the miner Because you are still getting hashboard on these miners but with lower hashrate.
I was wondering if you could help me resolve an issue with my miner the 3 miner failed the same day
https://imgur.com/y39kDwc
https://imgur.com/j3Z5neH
https://imgur.com/0dXUN76
https://imgur.com/y39kDwc
https://imgur.com/j3Z5neH
https://imgur.com/0dXUN76
Jump to: