Hi all -- wanted to confirm with my logs/situation what I gathered from this post, that a high Correction algorithm invocations count is not necessarily indicative of a bad drive, per the below:

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0        0         0         0    9823616     368586.466           0
write:         0        0         0         0    6846490      95087.111           0
verify:        0        0         0         0     247462          0.000           0

That said, I do see this in my syslog from yesterday, when UnRAID kicked the drive offline:

Apr 20 11:11:43 Morningstar kernel: mpt3sas_cm0: log_info(0x31120436): originator(PL), code(0x12), sub_code(0x0436)
Apr 20 11:11:43 Morningstar kernel: mpt3sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 48 TIMES] ###
Apr 20 11:14:17 Morningstar kernel: sd 10:0:6:0: [sdm] tag#1529 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Apr 20 11:14:17 Morningstar kernel: sd 10:0:6:0: [sdm] tag#1529 CDB: opcode=0x2a 2a 00 60 2e c2 bb 00 00 80 00
Apr 20 11:14:17 Morningstar kernel: I/O error, dev sdm, sector 12909417944 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 0
Apr 20 11:14:17 Morningstar kernel: md: disk11 write error, sector=12909417880

The disk11 write error repeats about 30 times before the drive goes offline. So the question is, is this a weird one-off, or a sign of trouble to come?

I did try to run a Long Self-Test, and it Aborted, but I also see there can be many reasons for that, as well.

Diags attached, and thanks for any help and advice!

morningstar-diagnostics-20260421-2241.zip morningstar-smart-20260421-2240.zip

Edited April 22Apr 22 by raqisasim

3 hours ago, raqisasim said:

high Correction algorithm invocations count is not necessarily indicative of a bad drive

It's not, SMART looks fine, and the syslog errors are not logged as a disk problem, so most likely a power/connection issue, but still good to run an extended SMART test, if it passes, replace cables or slots and retest.

On 4/22/2026 at 2:48 AM, JorgeB said:

It's not, SMART looks fine, and the syslog errors are not logged as a disk problem, so most likely a power/connection issue, but still good to run an extended SMART test, if it passes, replace cables or slots and retest.

Thanks again -- for anyone else running into this situation, I did an Extended SMART which came up clean as well, pushed some cables, and am currently doing a data rebuild based on official guidance: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself