Antminer S19 95TH setup

[boggym777]

I checked the speed and it is 10Mbps, and, from what I understood that the server would need some 5Mbps, it should be enough no?
Thank you

If you are running one unit 10mbps should be beyond enough the important is the internet you provide to the unit is should stable and use a pool server that gives you low latency like if you are in the US then use the US pool server or if you are living in Asian country then use Asia pool server.

Thank you very much. I managed to increase the speed to 20Mbps, so I think I am good.
Have a great weekend.

[1714648501]

1714648501

[1714648501]

1714648501

[1714648501]

1714648501

[1714648501]

1714648501

[boggym777]

Hi all,

Right now I am about to set the combinations of cables that philipma1957 sent me, and configure my antminer.
I would have another question though. I let's say I want to have a cabling solution involving an electrician, and later on I will switch to that solution, what are the proper steps to take the antminer down and plug it into the other cabling solution?
Do I have to follow a specific procedure, succession of steps, or just unplugging it should be enough?

Thank you

[boggym777]

I checked the speed and it is 10Mbps, and, from what I understood that the server would need some 5Mbps, it should be enough no?
Thank you

If you are running one unit 10mbps should be beyond enough the important is the internet you provide to the unit is should stable and use a pool server that gives you low latency like if you are in the US then use the US pool server or if you are living in Asian country then use Asia pool server.

So,
Is there a specific procedure to turn off an Antminer S19 for cleaning or for replacing network cables? Or simply unplug the power cords would be enough?
Thank you

[BitMaxz]

So,
Is there a specific procedure to turn off an Antminer S19 for cleaning or for replacing network cables? Or simply unplug the power cords would be enough?
Thank you

This unit does not have a switch or button to turn it off this unit you just simply unplug the unit from the power source.

Or you can use the reboot button from the dashboard you can find it under the system and then once the unit LED light turns off unplug the unit from power source.

[boggym777]

So,
Is there a specific procedure to turn off an Antminer S19 for cleaning or for replacing network cables? Or simply unplug the power cords would be enough?
Thank you

This unit does not have a switch or button to turn it off this unit you just simply unplug the unit from the power source.

Or you can use the reboot button from the dashboard you can find it under the system and then once the unit LED light turns off unplug the unit from power source.

Thank you very much

[boggym777]

Hi guys,
I managed today to turn on my Antminer S19 95TH, and it is working!!! An electrician helped me with a 220V line, so from this point of view everything is nice and dandy.
I was so excited to see the hashrate going to 96T, however, after a while, it went to 64, and then to 62, and it is still oscillating between those two.
Can I do anything? Did I configure it wrongly?
I already took contact with ViaBTC to see what is going on, and I am waiting for their response.
The miner is very noisy, and the basement is getting pretty warm now. It is good that we are approaching winter, so it will be good.
Thank you

[DaveF]

It sounds like one of your hashboards died. There are 3 each doing a bit over 30TH so dropping to the 60s really sounds like one of them just stopped working.
What does the web gui show for the boards? Also post the debug log if possible.

Did you get any kind of warranty on the unit? If you did, it might just be easier to send it back for a different one then spend time troubleshooting the problem.

-Dave

[boggym777]

It sounds like one of your hashboards died. There are 3 each doing a bit over 30TH so dropping to the 60s really sounds like one of them just stopped working.
What does the web gui show for the boards? Also post the debug log if possible.

Did you get any kind of warranty on the unit? If you did, it might just be easier to send it back for a different one then spend time troubleshooting the problem.

-Dave

Hi Dave,
You are right. I checked on the UI on the browser, and initially it showed hash board 1 not working, and I did a restart from the UI.
After it restarted, it showed only board 2 and 3.
Yes, I have warranty on the unit. So should I let it running with just 2 boards, or should I turn it off.
If I have to turn it off, should I just click on the restart miner button, and then un plug it? Or simply unplug it?
Thank you

[DaveF]

It sounds like one of your hashboards died. There are 3 each doing a bit over 30TH so dropping to the 60s really sounds like one of them just stopped working.
What does the web gui show for the boards? Also post the debug log if possible.

Did you get any kind of warranty on the unit? If you did, it might just be easier to send it back for a different one then spend time troubleshooting the problem.

-Dave

Hi Dave,
You are right. I checked on the UI on the browser, and initially it showed hash board 1 not working, and I did a restart from the UI.
After it restarted, it showed only board 2 and 3.
Yes, I have warranty on the unit. So should I let it running with just 2 boards, or should I turn it off.
If I have to turn it off, should I just click on the restart miner button, and then un plug it? Or simply unplug it?
Thank you

Just let it run. If the board is not hashing it's not pulling power so it's not like it costs more power to have it just sit there. You are just loosing profit.

You can try making sure the cables from the controller are in all the way and a full power down and cool off cycle and see if that fixes it, but since you do have a warranty I would just get a new miner.

-Dave

[boggym777]

It sounds like one of your hashboards died. There are 3 each doing a bit over 30TH so dropping to the 60s really sounds like one of them just stopped working.
What does the web gui show for the boards? Also post the debug log if possible.

Did you get any kind of warranty on the unit? If you did, it might just be easier to send it back for a different one then spend time troubleshooting the problem.

-Dave

Hi Dave,
You are right. I checked on the UI on the browser, and initially it showed hash board 1 not working, and I did a restart from the UI.
After it restarted, it showed only board 2 and 3.
Yes, I have warranty on the unit. So should I let it running with just 2 boards, or should I turn it off.
If I have to turn it off, should I just click on the restart miner button, and then un plug it? Or simply unplug it?
Thank you

Just let it run. If the board is not hashing it's not pulling power so it's not like it costs more power to have it just sit there. You are just loosing profit.

You can try making sure the cables from the controller are in all the way and a full power down and cool off cycle and see if that fixes it, but since you do have a warranty I would just get a new miner.

-Dave

Thank you Dave,
I am letting it run for the time being, and I am waiting for a response from the customer service of the seller. I got this from Amazon, and the seller is QIO TECH, so I am a bit reluctant to open it up to check what you were suggesting. It could be that there is a loose contact from transportation, however it would also void the warranty, right?
I will see what they respond, and I hope they have someone local that would take care of repairing the unit, otherwise I would have to send it back to China, and wait for a resolution...
Eventually, according to how the warranty process is working with them, I would send it back for a full refund, and I will see if I purchase a new one.
I will see first how they respond, and what their warranty response is.
Have a great day

[philipma1957]

try to restart it maybe it will go back to 3 boards.

Sometimes it is just a glitch and not a bad board.

[boggym777]

try to restart it maybe it will go back to 3 boards.

Sometimes it is just a glitch and not a bad board.

Hi philipma1957,
I already did that 2 times, hoping what you were suggesting, and every time only 2 boards appeared, 2 & 3. Number 1 is not appearing.
Prior to my first restart, on the GUI, as I saw the hash rate dropping, I checked the boards and number 1 appeared in red with 0 hash. After I restarted the unit the first time, the board #1 did not appear anymore. Only 2 & 3.
It could be, as Dave suggested, that a contact got loose during the transportation, however I am reluctant of opening up the unit as this might void the warranty, so I am waiting for customer support to respond to my messages, and take it from there.
Thank you

[BitMaxz]

I already did that 2 times, hoping what you were suggesting, and every time only 2 boards appeared, 2 & 3. Number 1 is not appearing.
Prior to my first restart, on the GUI, as I saw the hash rate dropping, I checked the boards and number 1 appeared in red with 0 hash. After I restarted the unit the first time, the board #1 did not appear anymore. Only 2 & 3.
It could be, as Dave suggested, that a contact got loose during the transportation, however I am reluctant of opening up the unit as this might void the warranty, so I am waiting for customer support to respond to my messages, and take it from there.

Can you share your miner logs I just want to check the logs if the 1st hashboard is still detected while it's not running properly we can maybe find the issue under the logs and give you some suggestions to try.

I guess that the 1st hashboard might had poor contact with the copper bar cleaning it with sandpaper might solve this.

[boggym777]

I already did that 2 times, hoping what you were suggesting, and every time only 2 boards appeared, 2 & 3. Number 1 is not appearing.
Prior to my first restart, on the GUI, as I saw the hash rate dropping, I checked the boards and number 1 appeared in red with 0 hash. After I restarted the unit the first time, the board #1 did not appear anymore. Only 2 & 3.
It could be, as Dave suggested, that a contact got loose during the transportation, however I am reluctant of opening up the unit as this might void the warranty, so I am waiting for customer support to respond to my messages, and take it from there.

Can you share your miner logs I just want to check the logs if the 1st hashboard is still detected while it's not running properly we can maybe find the issue under the logs and give you some suggestions to try.

I guess that the 1st hashboard might had poor contact with the copper bar cleaning it with sandpaper might solve this.

Hi BitMaxz,
Thank you for the offer. The only think about checking the contacts, I do not know how to do that w/o voiding the warranty, OK?
In the meantime, here are the logs:

free_area_init_node: node 0, pgdat c0b3c040, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf0000 s19916 r8192 d21044 u49152
pcpu-alloc: s19916 r8192 d21044 u49152 alloc=12*4096
pcpu-alloc:

• 0
• 1

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 209652K/245760K available (6317K kernel code, 243K rwdata, 1932K rodata, 1024K init, 232K bss, 19724K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090e410   (9242 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b3cda0   ( 244 kB)
       .bss : 0xc0b3cda0 - 0xc0b77024   ( 233 kB)
Preemptible hierarchical RCU implementation.
   Build-time adjustment of leaf fanout to 32.
   RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 6652K (cd47b000 - cdafa000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma:    DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 159, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
cdns-i2c e0005000.ps7_i2c: 100 kHz mmio e0005000 irq 154
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: disable subpage write
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: NAND_ECC_HW
nand: NAND_ECC_HW_SYNDROME
mtd->writesize = 2048
ecc->strength = 1
ecc->size = 2048
mtd->writesize = 2048
chip->ecc_strength_ds = 4
chip->ecc_step_ds = 512
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
8 ofpart partitions found on MTD device pl35x-nand
Creating 8 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-dts-marker-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000005200000 : "sig"
0x000005200000-0x000006000000 : "reserve1"
0x000006000000-0x000007000000 : "upgrade-ramfs"
0x000007000000-0x00000a800000 : "upgrade-file"
0x00000a800000-0x000010000000 : "reserve2"
nf_conntrack version 0.5.0 (3635 buckets, 14540 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
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)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs warning (device ram0): ext4_update_dynamic_rev:746: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr,errors=remount-ro
devpts: called with bogus options
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 262741923
ubi0: available PEBs: 36, total reserved PEBs: 28, PEBs reserved for bad PEB handling: 4
ubi0: background thread "ubi_bgt0d" started, PID 729
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 733
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, small LPT model
ubi2: attaching mtd4
ubi2: scanning is finished
ubi2: attached mtd4 (name "reserve1", size 14 MiB)
ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi2: good PEBs: 112, bad PEBs: 0, corrupted PEBs: 0
ubi2: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi2: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 3994070786
ubi2: available PEBs: 0, total reserved PEBs: 112, PEBs reserved for bad PEB handling: 4
ubi2: background thread "ubi_bgt2d" started, PID 740
UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 744
UBIFS (ubi2:0): recovery needed
UBIFS (ubi2:0): recovery completed
UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "misc"
UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi2:0): FS size: 11935744 bytes (11 MiB, 94 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
UBIFS (ubi2:0): reserved for root: 563754 bytes (550 KiB)
UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID 8AD8078B-085C-4B45-9E34-14F0A432C028, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
random: avahi-daemon urandom read with 2 bits of entropy available
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfbc8000
*base_vir_addr = 0xb031
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized


===========================================Miner log===========================================
1970-01-01 00:00:09 Miner compile time: Tue Nov 16 19:22:45 CST 2021 type: Antminer S19
1970-01-01 00:00:10 This is fix-freq version
1970-01-01 00:00:10 Miner compile time: Tue Nov 16 19:22:45 CST 2021 type: Antminer S19
1970-01-01 00:00:10 commit version: 386747fa 2021-10-21 19:58:45, build by: jenkins 2021-11-16 19:40:24
1970-01-01 00:00:10 opt_multi_version     = 1
1970-01-01 00:00:10 opt_bitmain_ab        = 1
1970-01-01 00:00:10 mid_auto_gen          = 0
1970-01-01 00:00:10 opt_bitmain_work_mode = 0
1970-01-01 00:00:10 mmap fpga_mem_addr_hal = 0xb5800000
1970-01-01 00:00:10 HASH_ON_PLUG V9 = 0x7
1970-01-01 00:00:10 Note: front fan is power on!
1970-01-01 00:00:10 Note: rear fan is power on!
1970-01-01 00:00:10 start the http log.
1970-01-01 00:00:10 httpListenThread start ret=0
1970-01-01 00:00:10 start listen on 6060 ...
1970-01-01 00:00:11 load machine NBS1902 conf
1970-01-01 00:00:11 machine : NBS1902
1970-01-01 00:00:11 chain_num 4, chain_domain_num 38, chain_asic_num 76, domain_asic_num 2
2023-10-29 17:24:18 miner ID : 8010e44a6f41a854
2023-10-29 17:24:18 FPGA Version = 0xB031
2023-10-29 17:24:18 HASH_ON_PLUG V9 = 0x7
2023-10-29 17:24:18 ==========================capability start==========================
2023-10-29 17:24:18 board num = 3
2023-10-29 17:24:18 board id = 0, chain num = 1
2023-10-29 17:24:18    chain id = 0
2023-10-29 17:24:18 board id = 1, chain num = 1
2023-10-29 17:24:18    chain id = 1
2023-10-29 17:24:18 board id = 2, chain num = 1
2023-10-29 17:24:18    chain id = 2
2023-10-29 17:24:18 ==========================capability end============================
2023-10-29 17:24:18 chain num = 3
2023-10-29 17:24:20 [chain 0]
2023-10-29 17:24:20 0x0000 11 4A FA 5C 6A 9C 6E 93   26 CE 55 4E 8B 35 BB 15
2023-10-29 17:24:20 0x0010 F5 59 CE 2E 6B DA 99 B4   1C 8D FF 0E 32 71 AE BF
2023-10-29 17:24:20 0x0020 EC 99 B6 C0 DD 7C BB 9F   43 C3 72 A0 8C AB 37 10
2023-10-29 17:24:20 0x0030 8A C4 3B F4 D5 E3 48 A3   17 C6 FC 3E 66 F4 96 74
2023-10-29 17:24:20 0x0040 E4 61 44 82 D7 10 23 95   C2 F7 FF FF FF FF FF FF
2023-10-29 17:24:20 0x0050 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x0060 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x0070 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x0080 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x0090 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x00A0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x00B0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x00C0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x00D0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x00E0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:20 0x00F0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF 5A
2023-10-29 17:24:20
2023-10-29 17:24:22 [chain 1]
2023-10-29 17:24:22 0x0000 11 4A FB 3B FC AB D6 54   62 F8 79 5D E2 81 07 67
2023-10-29 17:24:22 0x0010 81 08 9D 36 C6 EA FD 57   04 4E C1 6F 7A E0 0A 7D
2023-10-29 17:24:22 0x0020 D3 55 71 41 0E F0 B2 7A   95 73 65 0B 0E 85 7C 50
2023-10-29 17:24:22 0x0030 F0 D2 D2 9F 7D 2A 69 D3   FD C7 34 2C C4 7D 93 FF
2023-10-29 17:24:22 0x0040 B6 6A 4F 36 32 72 07 E2   91 7F FF FF FF FF FF FF
2023-10-29 17:24:22 0x0050 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x0060 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x0070 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x0080 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x0090 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x00A0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x00B0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x00C0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x00D0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x00E0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:22 0x00F0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF 5A
2023-10-29 17:24:22
2023-10-29 17:24:24 [chain 2]
2023-10-29 17:24:24 0x0000 11 4A 34 31 DA 3B 23 24   F1 2D FA 4D A3 F8 B7 FC
2023-10-29 17:24:24 0x0010 F1 70 6B 84 CB 26 AE 6E   D8 5D 85 A1 3B DA A0 11
2023-10-29 17:24:24 0x0020 61 32 4F D5 BB 2C 66 9D   52 70 95 D9 71 67 34 23
2023-10-29 17:24:24 0x0030 75 12 1C 64 CA C8 80 97   EA 62 AC 6F A7 9F 02 DC
2023-10-29 17:24:24 0x0040 3B DE AF 17 00 56 08 7D   20 6A FF FF FF FF FF FF
2023-10-29 17:24:24 0x0050 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x0060 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x0070 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x0080 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x0090 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x00A0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x00B0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x00C0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x00D0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x00E0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF
2023-10-29 17:24:24 0x00F0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF 5A
2023-10-29 17:24:24
2023-10-29 17:24:24 fan_eft : 0  fan_pwm : 100
2023-10-29 17:24:24 create thread
2023-10-29 17:24:24 fixed working voltage = 1380
2023-10-29 17:24:24 Chain

• PCB Version: 0x0146

2023-10-29 17:24:24 Chain

• BOM Version: 0x0200

2023-10-29 17:24:24 Chain [1] PCB Version: 0x0146
2023-10-29 17:24:24 Chain [1] BOM Version: 0x0200
2023-10-29 17:24:24 Chain [2] PCB Version: 0x0146
2023-10-29 17:24:24 Chain [2] BOM Version: 0x0200
2023-10-29 17:24:28 Fan check passed.
2023-10-29 17:24:29 chain[0] PIC jump to app
2023-10-29 17:24:30 Check chain[0] PIC fw version=0x89
2023-10-29 17:24:31 chain[1] PIC jump to app
2023-10-29 17:24:33 Check chain[1] PIC fw version=0x89
2023-10-29 17:24:34 chain[2] PIC jump to app
2023-10-29 17:24:36 Check chain[2] PIC fw version=0x89
2023-10-29 17:24:36 create thread
2023-10-29 17:24:36 max sensor num = 4
2023-10-29 17:24:36 temperature_monitor_thread start...
2023-10-29 17:24:40 power type version: 0x0074
2023-10-29 17:24:40 Enter sleep to make sure power release finish.
2023-10-29 17:25:55 Slept 74 seconds, diff = 5.
2023-10-29 17:25:55 set_voltage_by_steps to 1500.
2023-10-29 17:26:01 start up min temp by 75a = 25
2023-10-29 17:26:01 set UART baud to 115200
2023-10-29 17:26:01 chain avg vol rise to 15.13
2023-10-29 17:26:08 Chain[0]: find 0 asic, times 0
2023-10-29 17:26:16 Chain[0]: find 0 asic, times 1
2023-10-29 17:26:24 Chain[0]: find 0 asic, times 2
2023-10-29 17:26:25 Chain 0 only find 0 asic, will power off hash board 0
2023-10-29 17:26:28 chain avg vol rise to 22.69
2023-10-29 17:26:33 Chain[1]: find 76 asic, times 0
2023-10-29 17:26:39 chain avg vol drop to 15.12
2023-10-29 17:26:40 Chain[2]: find 76 asic, times 0
2023-10-29 17:26:40 pulse_mode = 1, ccdly_sel = 0, pwth_sel = 0
2023-10-29 17:26:43 min freq in eeprom = 675
2023-10-29 17:26:43 fixed frequency is 675
2023-10-29 17:26:43 Bring up temperature is 25
2023-10-29 17:26:43 set UART baud to 12000000
2023-10-29 17:26:43 set_voltage_by_steps to 1380.
2023-10-29 17:26:50 STATUS_INITED: soc init done!
2023-10-29 17:26:50 create thread
2023-10-29 17:26:50 create thread
2023-10-29 17:26:52 start to init...
2023-10-29 17:27:02 Init done!
2023-10-29 17:27:02 STATUS_OKAY
2023-10-29 17:27:02 start the cached job
2023-10-29 17:27:02 Version num 8
2023-10-29 17:27:02 Mask num 0xe000
2023-10-29 17:27:02 freq = 675, percent = 90, hcn = 14560, timeout = 524
2023-10-29 17:27:02 set_start_time_point total_tv_start_sys=182 total_tv_end_sys=183

I hope you will find something.
Thank you

[DaveF]

Could be the power bar, could be the cable.
I would wait to hear back from the seller.
Here in *theory* taking it apart and checking the cables should not invalidate the warranty since you do have to pull miners apart now and then to clean out the dust.
In reality, since you bought it from a reseller through Amazon, they can make any rules they want about what you can and cannot do. I would wait to see what they say.

If they don't respond or fix it for you get Amazon involved as early in the process as possible.

-Dave

[boggym777]

Could be the power bar, could be the cable.
I would wait to hear back from the seller.
Here in *theory* taking it apart and checking the cables should not invalidate the warranty since you do have to pull miners apart now and then to clean out the dust.
In reality, since you bought it from a reseller through Amazon, they can make any rules they want about what you can and cannot do. I would wait to see what they say.

If they don't respond or fix it for you get Amazon involved as early in the process as possible.

-Dave

They sent me a video on how to remove the upper housing to check the contacts for the connectors.
I am going to do that, and if it does not solve the issue, I hope they will send me another miner. Till now they were very friendly.
I hope it is a loose contact due to the transportation. It worked for a short while, and I had awesome hash rates, but very short.
In case they try to pull my leg, I will involve Amazon soon enough.
Thank you

[boggym777]

Could be the power bar, could be the cable.
I would wait to hear back from the seller.
Here in *theory* taking it apart and checking the cables should not invalidate the warranty since you do have to pull miners apart now and then to clean out the dust.
In reality, since you bought it from a reseller through Amazon, they can make any rules they want about what you can and cannot do. I would wait to see what they say.

If they don't respond or fix it for you get Amazon involved as early in the process as possible.

-Dave

Hi Dave,
I talked to Larry from customer service and after all the things he suggested I do (I reseated the connectors that are underneath the above lid, upgraded the firmware, and restarted the miner), there were still 2 boards. Number 1 was still not available.
So now I have to send the Antminer across the country to Richmondhill, BC for repairs.
It looks a bit wrong as I have a brand new product that will become a "repaired" product that actually does not have the same value as the brand new one. He offered 80$ for the loss I would have in mining till the miner will be back from repairs. I am not too happy about the whole outcome, however if I talk to Amazon, I guess they will stick to the seller, and I will get my money back, if I get it back, in 30 days.
So I will send the miner for repairs in the end, and see what becomes from that.
I will call Amazon just to see what they say, however I am a bit disappointed in how they solve such issue.

[BitMaxz]

I hope that you try checking the cable first by switching to another hashboard to confirm if it is just a cable or clean the copper bar with sandpaper as I suggested in my previous post but the sad part you end up sending it for repair.

Next time do some troubleshooting first before sending it for repair because sending it back for repair had a shipping cost.

Anyway, I'd like to give you a link that you can use for troubleshooting in the future and I hope it will be useful in the future if you experience some issues listed from the link below.

- https://support.bitmain.com/hc/en-us/articles/4406645619097-Common-Problems-and-Solutions-for-ANTMINER-19-series-

[boggym777]

I hope that you try checking the cable first by switching to another hashboard to confirm if it is just a cable or clean the copper bar with sandpaper as I suggested in my previous post but the sad part you end up sending it for repair.

Next time do some troubleshooting first before sending it for repair because sending it back for repair had a shipping cost.

Anyway, I'd like to give you a link that you can use for troubleshooting in the future and I hope it will be useful in the future if you experience some issues listed from the link below.

- https://support.bitmain.com/hc/en-us/articles/4406645619097-Common-Problems-and-Solutions-for-ANTMINER-19-series-

Thank you very much MitMaxz for your reply.
I did not try to swap the cables. I just reseated them, i.e. unplugged/plugged them back where they were, and it did not make any difference.
I will try eventually to do what you say, however I would like to send the unit to be repaired as soon as possible, i.e. today, so that I can have it back as soon as possible.
Have a great day

[boggym777]

Hi guys,
After the whole discussion with the seller's and Amazon's customer services, I decided to return the miner.
Also, after making a short calculation, due to increasing electric energy prices in ON, the mining of BTC using this miner is loosing money. The miner is consuming some 10$/day, and I barely made 8$ in 2 days.
So, I am sorry to have to leave this community I was beginning to enjoy so much.
Thank you very much for your support guys!