Brian B. Posted June 18, 2013 Share Posted June 18, 2013 Hi! So here's a weird thing... In April, I ran a non-correcting parity test, and it found 5 errors. After doing some reading up, I then ran some SMART tests, those didn't find anything unusual, so I closed my eyes and hit the button to correct the errors. A follow up test ran and found zero errors. Fast forward to this week, I ran the non-correcting parity test, and it found 5 errors. At the exact same locations as the problems from April (I log everything) Jun 16 03:28:40 Tower kernel: md: parity incorrect: 1565565768 Jun 16 03:28:40 Tower kernel: md: parity incorrect: 1565565776 Jun 16 03:28:40 Tower kernel: md: parity incorrect: 1565565784 Jun 16 03:28:40 Tower kernel: md: parity incorrect: 1565565792 Jun 16 03:28:40 Tower kernel: md: parity incorrect: 1565565800 Ran MORE smart tests today, and everything is just as happy as can be. Out of 10 drives, 7 have 0 reallocated sectors, a 1tb has 9 reallocated sectors, another 1tb drive has 45 reallocated sectors, and a 1.5tb drive has 153 reallocated sectors, BUT... those have been steady and unchanged for over a year. That's the number of bad sectors they had after preclearing when I initially pulled them out of external cases I had from my pre-unraid days. I have a new drive I want to expand the array with (swap out a low cap drive) But i don't want to do this if I'm going to get parity rebuild errors. What to do, what to do... Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.