Hi,

 

My parity drive started showing errors towards the end of a parity check.

 

Here is what shows in the disk log shows.

Sep 4 11:09:05 Tower kernel: ata3: SATA max UDMA/133 abar m2048@0xa1122000 port 0xa1122200 irq 124
Sep 4 11:09:05 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 4 11:09:05 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Sep 4 11:09:05 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Sep 4 11:09:05 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Sep 4 11:09:05 Tower kernel: ata3.00: ATA-10: WDC WD60EZRZ-00RWYB1, WD-WX81D65D9FLS, 80.00A80, max UDMA/133
Sep 4 11:09:05 Tower kernel: ata3.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Sep 4 11:09:05 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Sep 4 11:09:05 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Sep 4 11:09:05 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Sep 4 11:09:05 Tower kernel: ata3.00: configured for UDMA/133
Sep 4 11:09:05 Tower kernel: sd 3:0:0:0: [sdd] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
Sep 4 11:09:05 Tower kernel: sd 3:0:0:0: [sdd] 4096-byte physical blocks
Sep 4 11:09:05 Tower kernel: sd 3:0:0:0: [sdd] Write Protect is off
Sep 4 11:09:05 Tower kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Sep 4 11:09:05 Tower kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 4 11:09:05 Tower kernel: sdd: sdd1
Sep 4 11:09:05 Tower kernel: sd 3:0:0:0: [sdd] Attached SCSI disk
Sep 4 11:09:36 Tower emhttpd: WDC_WD60EZRZ-00RWYB1_WD-WX81D65D9FLS (sdd) 512 11721045168
Sep 4 11:09:36 Tower kernel: mdcmd (1): import 0 sdd 64 5860522532 0 WDC_WD60EZRZ-00RWYB1_WD-WX81D65D9FLS
Sep 4 11:09:36 Tower kernel: md: import disk0: (sdd) WDC_WD60EZRZ-00RWYB1_WD-WX81D65D9FLS size: 5860522532
Sep 4 11:09:36 Tower emhttpd: read SMART /dev/sdd
Sep 4 11:09:39 Tower root: /usr/sbin/wsdd
Sep 4 11:09:42 Tower emhttpd: shcmd (22): echo 128 > /sys/block/sdd/queue/nr_requests
Sep 4 11:10:33 Tower emhttpd: shcmd (83): echo 128 > /sys/block/sdd/queue/nr_requests
Sep 4 11:11:07 Tower root: /usr/sbin/wsdd
Sep 5 04:04:52 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x70000079 SErr 0x0 action 0x0
Sep 5 04:04:52 Tower kernel: ata3.00: irq_stat 0x40000008
Sep 5 04:04:52 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Sep 5 04:04:52 Tower kernel: ata3.00: cmd 60/40:e0:a0:d1:cb/05:00:95:02:00/40 tag 28 ncq dma 688128 in
Sep 5 04:04:52 Tower kernel: ata3.00: status: { DRDY ERR }
Sep 5 04:04:52 Tower kernel: ata3.00: error: { UNC }
Sep 5 04:04:52 Tower kernel: ata3.00: configured for UDMA/133
Sep 5 04:04:52 Tower kernel: sd 3:0:0:0: [sdd] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=3s
Sep 5 04:04:52 Tower kernel: sd 3:0:0:0: [sdd] tag#28 Sense Key : 0x3 [current]
Sep 5 04:04:52 Tower kernel: sd 3:0:0:0: [sdd] tag#28 ASC=0x11 ASCQ=0x4
Sep 5 04:04:52 Tower kernel: sd 3:0:0:0: [sdd] tag#28 CDB: opcode=0x88 88 00 00 00 00 02 95 cb d1 a0 00 00 05 40 00 00
Sep 5 04:04:52 Tower kernel: blk_update_request: I/O error, dev sdd, sector 11103097248 op 0x0:(READ) flags 0x0 phys_seg 168 prio class 0
Sep 5 04:04:52 Tower kernel: ata3: EH complete

 

I ran an extended self-test and it passed it. Attaching the self-test and diagnostics below.

Can I still continue using the disk? And if so, how do I reset the error count? Otherwise all the array health reports are coming as failed.

tower-smart-20220906-1519.ziptower-diagnostics-20220906-1522.zip

 

Thanks!

It's logged as a disk problem but SMART looks mostly OK and the extended test passed, I would keep if for now, but any more errors on the next parity checks would recommend replacing.