Is disk1 my sub or disk1 in my pool?

 

both entries spam the system log 20-30 times/sec for the first 20sec after boot.

 

mpt2sas isn't marked as an error, but behaves like one, is it normal or OK to ignore?

 

actual entries:

Error;

Aug 26 07:08:34 Yoda kernel: md: disk1 read error, sector=4526248 through to about 8296128

 

Info;

Aug 26 07:08:17 Yoda kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)

numerous entries always followed by 

Aug 26 07:08:20 Yoda kernel: sd 7:0:4:0: [sdf] tag#1402 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Aug 26 07:08:20 Yoda kernel: sd 7:0:4:0: [sdf] tag#1402 CDB: opcode=0x88 88 00 00 00 00 00 00 4c 12 e0 00 00 04 00 00 00

 

I only now saw this error buried in there;

Aug 26 07:08:20 Yoda kernel: I/O error, dev sdf, sector 4985568 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 2

 

/dev/sdf responsible for all this? Is it dead?

 

sdf IS disk1 In my array. What now?

 

yoda-diagnostics-20240826-0736.zip

Edited August 26, 20241 yr by Nasha
Resolved

Reseated card and cables, error didn't persist