- Minor
When there is a high activity on the server (eg parity check/rebuild) I get a lot of those errors :
Jul 22 13:16:26 hlf-data3 kernel: mpt2sas_cm1: log_info(0x31120100): originator(PL), code(0x12), sub_code(0x0100)
Jul 22 13:16:26 hlf-data3 kernel: mpt2sas_cm1: log_info(0x31120100): originator(PL), code(0x12), sub_code(0x0100)
Jul 22 13:16:26 hlf-data3 kernel: sd 10:0:1:0: device_block, handle(0x000a)
Jul 22 13:16:28 hlf-data3 kernel: sd 10:0:1:0: device_unblock and setting to running, handle(0x000a)
Jul 22 13:16:28 hlf-data3 kernel: sd 10:0:1:0: Power-on or device reset occurred
sometimes it is preceded by read errors :
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241360
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241368
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241376
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241384
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241392
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241400
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241408
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241416
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241424
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241432
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241440
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241448
Jul 22 13:06:30 hlf-data3 kernel: md: disk4 read error, sector=193241456
Jul 22 13:06:31 hlf-data3 kernel: sd 10:0:1:0: device_unblock and setting to running, handle(0x000a)
Jul 22 13:06:31 hlf-data3 kernel: sd 10:0:1:0: Power-on or device reset occurred
I checked drives, cables, and SAS cards. It doesn't looks like it's hardware related.
after searching on the net I found that someone had the same behavior on debian12 and it was related to the mpt3sas driver version 43.100.00.00 :
It's the exact same version unraid uses (even on the v7 beta).
Is there a way to have a kernel with a different version to see it if resolves the issue ? (at least 47.00.00.00)
thanks 😊