August 14, 201312 yr I just noticed I had 348 sync errors on the last monthly parity check. Checked the drives and I saw no errors so I decided to run another parity check with no correction. Now at 12% complete I have over 21,000 sync errors. Could it be the drives are correct and the parity drive is wrong or does anyone see a specific drive that is bad. No red balls, all green. Should I remove the parity drive and redo parity? Any help is appreciated. Thanks! syslog-2013-08-14.txt
August 16, 201312 yr The drives look fine. Although, sdl overheated in the past. Do you know how long ago this was? If the sdl overheated long before this issue then it's not likely to be related. What PSU model?
August 16, 201312 yr Author The overheat issue was long ago and even then it wasn't what I call an overheat issue, no more than any other drive I've had and none of those had the issue. I have a PC Power and Cooling 750 watt power supply. I don't think it would be power supply related but I can replace it if you think it will help.
August 17, 201312 yr Author Mem check ran all night and completed with no error. I restarted the server and it wanted to do a parity check so I let it. 8% in and I have 21187 sync errors and that's how many I had on the previous parity check. Seems like it's somewhere between 1% and 8% that is gets the sync errors and then either stops recording sync errors or that's all it has. Any ideas?
August 18, 201312 yr Author Yes, all my cables click into place and I've checked them. If it was a cable then why would the sync errors only be between 1 and 8%? I get that cables can be the issue but it seems to me there would be more errors throughout the process, not just at the beginning.
September 1, 201312 yr Author I did nothing since I reported this issue because I didn't know what was wrong but apparently during this month's parity check it started and then at some point drive SDS went into red status. I stopped the array, shut the server down, replaced this drive with a new one, and I upgraded to final 5.0 while it was down. It started up fine, I assigned the new drive in it's place, it rebuilt the data with no issues, and now it's doing a parity check. It has zero sync errors and is already ahead of where it started getting the previous sync errors so I'm assuming that drive was the issue even though smart didn't detect any known issues with that drive. Can't explain it but at least it's fixed. Thanks everyone for the advice!
Archived
This topic is now archived and is closed to further replies.