daxxx

Changed Status to Open Changed Priority to Urgent

That's awersome, but when it will be fixed? It can lead to major data loss if one of the disks is returning random data. And user can't prevent it after reboot/array restart. It's not minor, it should be urgent.

Just tried once again and even after navigating to Shares and back to Main caused that checkbox to be ignored. Log: Jan 8 22:29:11 unraid kernel: mdcmd (38): check Jan 8 22:29:11 unraid kernel: md: recovery thread: check P Q ... Jan 8 22:29:32 unraid kernel: mdcmd (39): nocheck Cancel Jan 8 22:29:32 unraid kernel: md: recovery thread: exit status: -4 Jan 8 22:29:39 unraid kernel: mdcmd (40): check nocorrect Jan 8 22:29:39 unraid kernel: md: recovery thread: check P Q ... Seems like every first check is correcting.

All subsequent runs log: "unraid kernel: mdcmd (50): check nocorrect". But then when I stop the array and start again it's correcting.

I was trying to check the parity without correcting erros. Steps to reproduce: 1. Start the array 2. Without navigating to other pages uncheck "Write corrections to parity" 3. Start parity check Parity check starts with correction enabled. Log: "unraid kernel: mdcmd (36): check" and also "unraid kernel: md: recovery thread: Q corrected, sector=40408xxxxx" I'll try to provide more info (diagnostics also) but right now I'm in the middle of moving some data around.