October 18, 20241 yr Background - Previous Parity Check (non-correcting) came back with 0 errors - Upgraded Parity Drive to a larger size (pre-cleared with no issues) - Repurposed the previous Parity Drive into a new Data Drive to expand the Array - The new Data Drive is empty and ready for future use - Parity Rebuild came back with 0 errors Issue - A scheduled Parity Check (non-correcting) kicks off and within 15 minutes I get 5 errors Oct 7 01:00:07 server kernel: mdcmd (47): check NOCORRECT Oct 7 01:00:07 server kernel: Oct 7 01:00:07 server kernel: md: recovery thread: check P ... Oct 7 01:14:42 server kernel: md: recovery thread: P incorrect, sector=408944536 Oct 7 01:14:42 server kernel: md: recovery thread: P incorrect, sector=408944544 Oct 7 01:14:42 server kernel: md: recovery thread: P incorrect, sector=408944552 Oct 7 01:14:42 server kernel: md: recovery thread: P incorrect, sector=408944560 Oct 7 01:14:42 server kernel: md: recovery thread: P incorrect, sector=408944568 - The Parity Check (non-correcting) just finished with no additional errors reported - No SMART alerts Next Steps - I'm confident the data on the Data Drives is valid and good. - Outside of updating a few files with newer versions occasionally and adding additional new files, the data doesn't have a high degree of utilization. What should I do next? Thanks in advance for any assistance / insight provided <3
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.