disk4 write error - not sure how to proceed...

[onyx00]

Woke up to an error via email and looking at the unraid dashboard it showed disk4 (sdj) was disabled and showing "1" in the r/w error column.  I've attached the diagnostics file, and below is what I saw in the syslog.  A short SMART test passed without issue and the extended test is currently running.  Also, will point out that a parity check found 0 errors on 5/1.

 

Based on provided details is there any suggestion of how I proceed?  Especially if the extended smart test passes without issue.  Do I look at cables...?  Or just ignore and rebuild the disk?

 

May 10 01:01:44 Tower emhttpd: read SMART /dev/sdd
May 10 01:03:12 Tower kernel: sd 1:0:6:0: attempting task abort!scmd(0x000000008ab633e3), outstanding for 15295 ms & timeout 15000 ms
May 10 01:03:12 Tower kernel: sd 1:0:6:0: [sdj] tag#3223 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
May 10 01:03:12 Tower kernel: scsi target1:0:6: handle(0x000f), sas_address(0x4433221105000000), phy(5)
May 10 01:03:12 Tower kernel: scsi target1:0:6: enclosure logical id(0x500605b004cd7430), slot(6) 
May 10 01:03:16 Tower kernel: sd 1:0:6:0: task abort: SUCCESS scmd(0x000000008ab633e3)
May 10 01:03:16 Tower kernel: sd 1:0:6:0: [sdj] tag#3276 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
May 10 01:03:16 Tower kernel: sd 1:0:6:0: [sdj] tag#3276 Sense Key : 0x2 [current] 
May 10 01:03:16 Tower kernel: sd 1:0:6:0: [sdj] tag#3276 ASC=0x4 ASCQ=0x0 
May 10 01:03:16 Tower kernel: sd 1:0:6:0: [sdj] tag#3276 CDB: opcode=0x8a 8a 08 00 00 00 00 ae ac 00 d0 00 00 00 08 00 00
May 10 01:03:16 Tower kernel: blk_update_request: I/O error, dev sdj, sector 2930507984 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
May 10 01:03:16 Tower kernel: md: disk4 write error, sector=2930507920
May 10 01:03:16 Tower kernel: sd 1:0:6:0: [sdj] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
May 10 01:03:16 Tower kernel: sd 1:0:6:0: [sdj] tag#5 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00
May 10 01:03:16 Tower emhttpd: read SMART /dev/sdj
May 10 01:03:26 Tower crond[1174]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
May 10 01:03:28 Tower emhttpd: read SMART /dev/sdh
May 10 01:03:28 Tower emhttpd: read SMART /dev/sdg
May 10 01:03:28 Tower emhttpd: read SMART /dev/sde
May 10 01:03:28 Tower emhttpd: read SMART /dev/sdf

 

tower-diagnostics-20230510-1630.zip

[JorgeB]

SMART looks fine and error was during spin up, so likely this issue: