my parity drive was disabled the other day, checked cables/attempted to rebuild parity and it dropped off with the same error which google might suggest means a drive failure at some particular sectors. As a result I ran an extended smart self test which I thought checks every sector to verify, this passes ok though so now I'm unsure if the drive is really dead or not. Any help appreciated, the smart report is attached

parity_smart_report.txt

kicked off another attempt to rebuild parity,  diagnostics also attached

zalaga-unraid-diagnostics-20241207-0915.zip

fortunately rebuild consistently fails v quickly

 

Dec  7 09:17:23 zalaga-unraid Parity Check Tuning: Parity Sync/Data Rebuild detected
Dec  7 09:19:25 zalaga-unraid kernel: mpt2sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
Dec  7 09:20:02 zalaga-unraid kernel: sd 7:0:7:0: device_block, handle(0x0010)
Dec  7 09:20:03 zalaga-unraid kernel: sd 7:0:7:0: device_unblock and setting to running, handle(0x0010)
Dec  7 09:20:03 zalaga-unraid kernel: sd 7:0:7:0: [sdi] tag#4840 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=48s
Dec  7 09:20:03 zalaga-unraid kernel: sd 7:0:7:0: [sdi] tag#4840 CDB: opcode=0x8a 8a 00 00 00 00 00 03 11 95 e8 00 00 04 00 00 00
Dec  7 09:20:03 zalaga-unraid kernel: I/O error, dev sdi, sector 51484136 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2
Dec  7 09:20:03 zalaga-unraid kernel: md: disk0 write error, sector=51484072

and then reams of errors before it takes the device offline again

 

it's attached to an 8 port pcie card and I've already switched from one port to another on that so I guess this really does mean the drive is dead as the problem follows the drive?

Edited December 7, 20241 yr by mattkhan

Make sure you also try with different cables, both power and SATA, if it keeps happening it's likely a bad disk.