I'm a bit lost on troubleshooting why the array is giving me a failure status.  There were some disk read errors during the last parity check and 2 sectors were reallocated, but smart extended tests seem to pass on that drive and nothing else is obviously amiss from what I can tell.  Diagnostics attached.  TIA.

qstore-diagnostics-20210406-2115.zip

2 reallocated on parity, nothing to worry about. You can acknowledge that by clicking on that SMART warning on the Dashboard page and it will warn again if it increases.

 

You can reset the Error counts at Main - Array Operation - Clear Stats though I have seen some reports that isn't working on 6.9.1. If not then you would have to reboot to clear stats.

 

More troubling is lots of this in syslog:

Apr  5 11:06:41 qstore kernel: EDAC sbridge MC0: HANDLING MCE MEMORY ERROR
Apr  5 11:06:41 qstore kernel: EDAC sbridge MC0: CPU 0: Machine Check Event: 0 Bank 9: cc000211000800c0
Apr  5 11:06:41 qstore kernel: EDAC sbridge MC0: TSC 0 
Apr  5 11:06:41 qstore kernel: EDAC sbridge MC0: ADDR 1a34fa000 
Apr  5 11:06:41 qstore kernel: EDAC sbridge MC0: MISC 90862202220228c 
Apr  5 11:06:41 qstore kernel: EDAC sbridge MC0: PROCESSOR 0:50663 TIME 1617638801 SOCKET 0 APIC 0
Apr  5 11:06:41 qstore kernel: EDAC MC0: 8 CE memory scrubbing error on CPU_SrcID#0_Ha#0_Chan#0_DIMM#0 (channel:0 page:0x1a34fa offset:0x0 grain:32 syndrome:0x0 -  OVERFLOW area:DRAM err_code:0008:00c0 socket:0 ha:0 channel_mask:1 rank:255)

 

I must have skimmed past that one, guess that memory is on the way out.  Acknowledging via the smart warning didn't work but I'll clear the error counts and see if it reports a as pass afterwards.

Rebooting was required to clear the read errors and return the array back to a passing status.  I've reseated the memory module and will continue to monitor the logs for that.  Feel free to mark this one solved and thank you for the assist trurl!