March 9Mar 9 I had one read error a few weeks ago on disk 3.Passed short and long self-tests. See the attached diagnostics.Is there a problem?carbonblack-diagnostics-20260309-1932.zip Edited March 10Mar 10 by 12_purple_giraffes
March 9Mar 9 Community Expert Looks like it was probably a problem communicating with the disk, cable or controller, but hasn't repeated. SMART looks OK and you even successfully completed an extended self-test.Post a screenshot of Array Operation.
March 9Mar 9 Community Expert 10 minutes ago, trurl said:Post a screenshot of Array Operation.The part I was specifically asking for is below the part you took a screenshot of.
March 9Mar 9 Author 22 minutes ago, trurl said:The part I was specifically asking for is below the part you took a screenshot of.Sorry
March 9Mar 9 Community Expert Solution You can reset that error count with the CLEAR STATS button. Not sure that will make FCP quit reporting it though, it might just be scanning syslog. Reboot will take care of it.The reason I asked for the screenshot is because that button seems to have disappeared on some later Unraid version. I had a similar occurrence during my last monthly parity check but when I looked for that button it was gone. I rebooted to get FCP to quit reporting it.Your Unraid version is over a year old, and has a deprecated mover tuning plugin installed.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.