UTiCkAOR

Yep.. looks like the drive was botched in some way. Put a new one today and it worked right out of the box.

I'm really starting to think it's the drive. I've got two more drives on the way to try those out as well.

The same. 8,001,563,222,016 bytes [8.00 TB] New Drive Ironwolf 8,001,563,222,016 bytes [8.00 TB] Parity Drive WD RED Log is full of disk read errors: ar 4 00:09:56 Tower emhttpd: shcmd (369): xfs_growfs /mnt/disk8 Mar 4 00:09:56 Tower root: meta-data=/dev/md8 isize=512 agcount=8, agsize=268435455 blks Mar 4 00:09:56 Tower root: = sectsz=512 attr=2, projid32bit=1 Mar 4 00:09:56 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 4 00:09:56 Tower root: = reflink=1 Mar 4 00:09:56 Tower root: data = bsize=4096 blocks=1953506633, imaxpct=5 Mar 4 00:09:56 Tower root: = sunit=0 swidth=0 blks Mar 4 00:09:56 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 4 00:09:56 Tower root: log =internal log bsize=4096 blocks=521728, version=2 Mar 4 00:09:56 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 4 00:09:56 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 4 00:09:56 Tower emhttpd: shcmd (370): mkdir -p /mnt/cache Mar 4 00:09:56 Tower kernel: ata50.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 4 00:09:56 Tower kernel: ata50.00: irq_stat 0x40000001 Mar 4 00:09:56 Tower kernel: ata50.00: failed command: READ DMA EXT Mar 4 00:09:56 Tower kernel: ata50.00: cmd 25/00:08:00:2a:81/00:00:a3:03:00/e0 tag 12 dma 4096 in Mar 4 00:09:56 Tower kernel: res 53/04:08:00:2a:81/00:00:a3:03:00/e0 Emask 0x1 (device error) Mar 4 00:09:56 Tower kernel: ata50.00: status: { DRDY SENSE ERR } Mar 4 00:09:56 Tower kernel: ata50.00: error: { ABRT } Mar 4 00:09:56 Tower kernel: ata50.00: configured for UDMA/133 (device error ignored) Mar 4 00:09:56 Tower kernel: sd 50:0:0:0: [sdi] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Mar 4 00:09:56 Tower kernel: sd 50:0:0:0: [sdi] tag#12 Sense Key : 0x5 [current] Mar 4 00:09:56 Tower kernel: sd 50:0:0:0: [sdi] tag#12 ASC=0x21 ASCQ=0x4 Mar 4 00:09:56 Tower kernel: sd 50:0:0:0: [sdi] tag#12 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 2a 00 00 00 00 08 00 00 Mar 4 00:09:56 Tower kernel: blk_update_request: I/O error, dev sdi, sector 15628052992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Mar 4 00:09:56 Tower kernel: ata50: EH complete Mar 4 00:09:56 Tower kernel: ata50.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 4 00:09:56 Tower kernel: ata50.00: irq_stat 0x40000001 Mar 4 00:09:56 Tower kernel: ata50.00: failed command: READ DMA EXT Mar 4 00:09:56 Tower kernel: ata50.00: cmd 25/00:08:00:2a:81/00:00:a3:03:00/e0 tag 16 dma 4096 in Mar 4 00:09:56 Tower kernel: res 53/04:08:00:2a:81/00:00:a3:03:00/e0 Emask 0x1 (device error) Mar 4 00:09:56 Tower kernel: ata50.00: status: { DRDY SENSE ERR } Mar 4 00:09:56 Tower kernel: ata50.00: error: { ABRT } Mar 4 00:09:56 Tower kernel: ata50.00: configured for UDMA/133 (device error ignored) Mar 4 00:09:56 Tower kernel: ata50: EH complete Mar 4 00:09:56 Tower kernel: ata50.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 4 00:09:56 Tower kernel: ata50.00: irq_stat 0x40000001 Mar 4 00:09:56 Tower kernel: ata50.00: failed command: READ DMA EXT Mar 4 00:09:56 Tower kernel: ata50.00: cmd 25/00:08:00:2a:81/00:00:a3:03:00/e0 tag 10 dma 4096 in Mar 4 00:09:56 Tower kernel: res 53/04:08:00:2a:81/00:00:a3:03:00/e0 Emask 0x1 (device error) Mar 4 00:09:56 Tower kernel: ata50.00: status: { DRDY SENSE ERR } Mar 4 00:09:56 Tower kernel: ata50.00: error: { ABRT } Mar 4 00:09:56 Tower kernel: ata50.00: configured for UDMA/133 (device error ignored) Mar 4 00:09:56 Tower kernel: ata50: EH complete Mar 4 00:09:56 Tower kernel: ata50.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 4 00:09:56 Tower kernel: ata50.00: irq_stat 0x40000001 Mar 4 00:09:56 Tower kernel: ata50.00: failed command: READ DMA EXT Mar 4 00:09:56 Tower kernel: ata50.00: cmd 25/00:08:00:2a:81/00:00:a3:03:00/e0 tag 14 dma 4096 in Mar 4 00:09:56 Tower kernel: res 53/04:08:00:2a:81/00:00:a3:03:00/e0 Emask 0x1 (device error) Mar 4 00:09:56 Tower kernel: ata50.00: status: { DRDY SENSE ERR } Mar 4 00:09:56 Tower kernel: ata50.00: error: { ABRT } Mar 4 00:09:56 Tower kernel: ata50.00: configured for UDMA/133 (device error ignored) Mar 4 00:09:56 Tower kernel: ata50: EH complete Mar 4 00:09:56 Tower kernel: ata50.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 4 00:09:56 Tower kernel: ata50.00: irq_stat 0x40000001 Mar 4 00:09:56 Tower kernel: ata50.00: failed command: READ DMA EXT Mar 4 00:09:56 Tower kernel: ata50.00: cmd 25/00:08:00:2a:81/00:00:a3:03:00/e0 tag 21 dma 4096 in Mar 4 00:09:56 Tower kernel: res 53/04:08:00:2a:81/00:00:a3:03:00/e0 Emask 0x1 (device error) Mar 4 00:09:56 Tower kernel: ata50.00: status: { DRDY SENSE ERR } Mar 4 00:09:56 Tower kernel: ata50.00: error: { ABRT } Mar 4 00:09:56 Tower kernel: ata50.00: configured for UDMA/133 (device error ignored) Mar 4 00:09:56 Tower kernel: ata50: EH complete Mar 4 00:09:56 Tower kernel: ata50.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 4 00:09:56 Tower kernel: ata50.00: irq_stat 0x40000001 Mar 4 00:09:56 Tower kernel: ata50.00: failed command: READ DMA EXT Mar 4 00:09:56 Tower kernel: ata50.00: cmd 25/00:08:00:2a:81/00:00:a3:03:00/e0 tag 26 dma 4096 in Mar 4 00:09:56 Tower kernel: res 53/04:08:00:2a:81/00:00:a3:03:00/e0 Emask 0x1 (device error) Mar 4 00:09:56 Tower kernel: ata50.00: status: { DRDY SENSE ERR } Mar 4 00:09:56 Tower kernel: ata50.00: error: { ABRT } Mar 4 00:09:56 Tower kernel: ata50.00: configured for UDMA/133 (device error ignored) Mar 4 00:09:56 Tower kernel: ata50: EH complete Mar 4 00:09:56 Tower kernel: ata50.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 4 00:09:56 Tower kernel: ata50.00: irq_stat 0x40000001 Mar 4 00:09:56 Tower kernel: ata50.00: failed command: READ DMA EXT Mar 4 00:09:56 Tower kernel: ata50.00: cmd 25/00:08:00:2a:81/00:00:a3:03:00/e0 tag 0 dma 4096 in Mar 4 00:09:56 Tower kernel: res 53/04:08:00:2a:81/00:00:a3:03:00/e0 Emask 0x1 (device error) Mar 4 00:09:56 Tower kernel: ata50.00: status: { DRDY SENSE ERR } Mar 4 00:09:56 Tower kernel: ata50.00: error: { ABRT } Mar 4 00:09:56 Tower kernel: ata50.00: configured for UDMA/133 (device error ignored) Mar 4 00:09:56 Tower kernel: sd 50:0:0:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Mar 4 00:09:56 Tower kernel: sd 50:0:0:0: [sdi] tag#0 Sense Key : 0x5 [current] Mar 4 00:09:56 Tower kernel: sd 50:0:0:0: [sdi] tag#0 ASC=0x21 ASCQ=0x4 Mar 4 00:09:56 Tower kernel: sd 50:0:0:0: [sdi] tag#0 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 2a 00 00 00 00 08 00 00 Mar 4 00:09:56 Tower kernel: blk_update_request: I/O error, dev sdi, sector 15628052992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Mar 4 00:09:56 Tower kernel: Buffer I/O error on dev sdi, logical block 1953506624, async page read

checked them and also replaced the SATA cable and still same result. I can see it as a device, but all the SMART "show" buttons have nothing to show. My other devices at least output "no errors" or that data it has. Using the Start Short Smart test button immediately flashes to stop then back to start again with no result. Also tried swapping the new disc with an older drive that i connected to another port to verify cables. New drive also does not respond to attempts to "spin it up" 🤦‍♂️

Have 8 disk array, went to replace a 3TB drive with a newly purchased ironwolf 8TB, but new drive would not show up to be selected. At first thought it was LSI card config, so then got a new SATA non-raid 8 port ASMedia ASM1064 and that too did not work. The drive would display in the drop down to replace the drive, but then go blank once i selected it. Finally tried connecting the drive to an empty on board SATA port and still nothing. Attached Diag tower-diagnostics-20220303-2315.zip