Hi,
The title is the TL;DR; and I could be being stupid about this but before I try and get my drive replaced I would like to be sure.
This week whilst a parity check was running on my unRAID sevrer (I didn't realise until later) I was doing some moving of files using unBalance and got a warning that some permissions were wrong. To fix this I did what was advised which was to run the "New Permissions (Docker Safe)" tool which I did. While this was running the parity check stopped (failed) and the parity check aborted with an error.
I assumed that this was because I ran the permissions tool and immediately started another parity check which finished reporting no errors. The Dashboard status shows:
Last checked on Mon 16 Jan 2017 10:41:37 AM GMT (three days ago), finding 0 errors.
Duration: 17 hours, 57 minutes, 48 seconds. Average speed: 123.7 MB/sec
I later noticed that the parity device is showing as Disabled on the Main tab of the UI, with 17 errors listed but this is where my confusion starts. I looked in the system log and found:
Jan 15 16:25:40 DavidServer kernel: blk_update_request: I/O error, dev sde, sector 6445719816
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719752
Jan 15 16:25:40 DavidServer kernel: blk_update_request: I/O error, dev sde, sector 6445719688
Jan 15 16:25:40 DavidServer kernel: blk_update_request: I/O error, dev sde, sector 6445719808
Jan 15 16:25:40 DavidServer kernel: blk_update_request: I/O error, dev sde, sector 6445719744
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719760
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719768
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719776
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719784
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719792
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719800
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719808
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719624
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719632
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719640
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719648
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719656
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719664
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719672
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719744
Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719680
So my question is how did the parity check run through and pass with no errors on 16th if the disk failed on the 15th?
Looking on the properties of the drive all of the SMART tests come back as PASS and no errors are shown on the page so I am unsure whether I really have a faulty drive or something funny went on with the Parity check and Permissions fix running at the same time.
Any advice appreciated on how to test further and prove whether there really is a fault with this drive.
Thank you
David