BelviGER

I just ordered a new drive because sooner or later I'd need it anyways - and it was the drive So brand new drive arrived dead

I don't think I can run a SMART test because I can't choose it for a smart test because its only available for mounting, it can't be mounted When I select it here it disappears from the list Will order a replacement cable though and try that

tower-diagnostics-20231112-1946.zip

unRaAID v6.12.4 "Fix Common Problems" Plugin and thats it Hey, I had to replace my parity drive(sdc). Replaced a 14tb ironwolf with a 14tb wd red. When booting the server the drive will show up as an available drive, but after selecting it it disappears. It remains visible as a drive in Tools>System Devices The log throws a bunch of I/O Errors though. Nov 12 10:40:01 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 12 10:40:01 Tower kernel: ata5.00: irq_stat 0x40000001 Nov 12 10:40:01 Tower kernel: ata5.00: failed command: READ DMA EXT Nov 12 10:40:01 Tower kernel: ata5.00: cmd 25/00:08:80:ff:df/00:00:5d:06:00/e0 tag 0 dma 4096 in Nov 12 10:40:01 Tower kernel: res 53/40:08:80:ff:df/00:00:5d:06:00/40 Emask 0x9 (media error) Nov 12 10:40:01 Tower kernel: ata5.00: status: { DRDY SENSE ERR } Nov 12 10:40:01 Tower kernel: ata5.00: error: { UNC } Nov 12 10:40:01 Tower kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1 Nov 12 10:40:01 Tower kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1 Nov 12 10:40:01 Tower kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1 Nov 12 10:40:01 Tower kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1 Nov 12 10:40:01 Tower kernel: ata5.00: configured for UDMA/133 Nov 12 10:40:01 Tower kernel: sd 5:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Nov 12 10:40:01 Tower kernel: sd 5:0:0:0: [sdc] tag#0 Sense Key : 0x3 [current] Nov 12 10:40:01 Tower kernel: sd 5:0:0:0: [sdc] tag#0 ASC=0x11 ASCQ=0x4 Nov 12 10:40:01 Tower kernel: sd 5:0:0:0: [sdc] tag#0 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00 Nov 12 10:40:01 Tower kernel: I/O error, dev sdc, sector 27344764800 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Nov 12 10:40:01 Tower kernel: ata5: EH complete Nov 12 10:40:01 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 12 10:40:01 Tower kernel: ata5.00: irq_stat 0x40000001 Nov 12 10:40:01 Tower kernel: ata5.00: failed command: READ DMA EXT Nov 12 10:40:01 Tower kernel: ata5.00: cmd 25/00:08:80:ff:df/00:00:5d:06:00/e0 tag 5 dma 4096 in Nov 12 10:40:01 Tower kernel: res 53/40:08:80:ff:df/00:00:5d:06:00/40 Emask 0x9 (media error) Nov 12 10:40:01 Tower kernel: ata5.00: status: { DRDY SENSE ERR } Nov 12 10:40:01 Tower kernel: ata5.00: error: { UNC } Nov 12 10:40:02 Tower kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1 Nov 12 10:40:02 Tower kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1 Nov 12 10:40:02 Tower kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1 Nov 12 10:40:02 Tower kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1 Nov 12 10:40:02 Tower kernel: ata5.00: configured for UDMA/133 Nov 12 10:40:02 Tower kernel: sd 5:0:0:0: [sdc] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Nov 12 10:40:02 Tower kernel: sd 5:0:0:0: [sdc] tag#5 Sense Key : 0x3 [current] Nov 12 10:40:02 Tower kernel: sd 5:0:0:0: [sdc] tag#5 ASC=0x11 ASCQ=0x4 Nov 12 10:40:02 Tower kernel: sd 5:0:0:0: [sdc] tag#5 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00 Nov 12 10:40:02 Tower kernel: I/O error, dev sdc, sector 27344764800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Nov 12 10:40:02 Tower kernel: Buffer I/O error on dev sdc, logical block 3418095600, async page read Nov 12 10:40:02 Tower kernel: ata5: EH complete This error repeats every minute. Is the drive DOA, did I forget something, or is it something else?