t33j4y Posted September 3, 2017 Share Posted September 3, 2017 During the monthly parity check, several disks in the array reached temps of 45-48 degrees due to a malfunctioning fan control (manual). The array threw a number of read errors on one of the disks. I also received a warning mail stating that there were read errors: Event: unRAID array errors Subject: Warning [TOWER] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 5 - ST4000DM000-1F2168_Z3015S7L (sdf) (errors 168) and a mail reporting a SMART issue: Event: unRAID Disk 5 SMART health [187] Subject: Warning [TOWER] - reported uncorrect is 1 Description: ST4000DM000-1F2168_Z3015S7L (sdf) Importance: warning The SMART report for disk 5 (attached) now shows 1 error. The parity check has concluded now and states "0 errors" which surprises me. I am no wondering what the next step should be. a. Should I run parity check again now at adequate temps to see if the error reproduces? b. Should I rush out and buy a replacement disk, pre-clear it and replace the offending disk? c. Count to 10, calm down and have faith in unRaid when it tells me that there are no parity errors and chalk this one up to temperature induced anomaly? Thanks for any feedback :-) log.txt ST4000DM000-1F2168_Z3015S7L-20170903-1302.txt Link to comment
JorgeB Posted September 3, 2017 Share Posted September 3, 2017 There weree no sync errors because unRAID successfully wrote back the problem sector(s) using the other disks + parity. It does look like a disk problem but it may be OK now, you can confirm by running an extended SMART test. Link to comment
t33j4y Posted September 3, 2017 Author Share Posted September 3, 2017 Will do that immediately! Thanks :-) Link to comment
t33j4y Posted September 3, 2017 Author Share Posted September 3, 2017 SMART test came back and said "Completed without errors" so I will assume everything is ok :-) Link to comment
JorgeB Posted September 3, 2017 Share Posted September 3, 2017 OK for now, if there are more problems with that disk on the near future consider replacing, if that error had occurred during the rebuild of another disk there would be some file corruption. Link to comment
t33j4y Posted September 3, 2017 Author Share Posted September 3, 2017 Just now, johnnie.black said: OK for now, if there are more problems with that disk on the near future consider replacing, if that error had occurred during the rebuild of another disk there would be some file corruption. Will certainly keep an eye on it. I would hope that my dual parity would have helped, had the error occurred during a rebuild? Thanks! Link to comment
JorgeB Posted September 3, 2017 Share Posted September 3, 2017 1 minute ago, t33j4y said: I would hope that my dual parity would have helped, had the error occurred during a rebuild? Yes, it should. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.