June 27, 201610 yr I have run parity check quite regularly on my array and other than the odd failure I have never run into an issue or had any errors. However the last two parity checks have reported a couple of errors. Jun 21 22:05:48 Tower kernel: md: recovery thread checking parity... Jun 21 22:05:48 Tower kernel: md: using 1536k window, over a total of 5860522532 blocks. Jun 22 05:10:41 Tower kernel: md: correcting parity, sector=5156564912 Jun 22 05:11:21 Tower kernel: md: correcting parity, sector=5163641336 Jun 22 05:36:24 Tower kernel: md: correcting parity, sector=5345702432 Jun 26 07:30:01 Tower kernel: md: recovery thread checking parity... Jun 26 07:30:01 Tower kernel: md: using 1536k window, over a total of 5860522532 blocks. Jun 26 13:22:21 Tower kernel: md: correcting parity, sector=5156560048 Jun 26 13:36:32 Tower kernel: md: correcting parity, sector=5342882616 Jun 26 13:36:58 Tower kernel: md: correcting parity, sector=5348390872 Jun 26 15:30:00 Tower kernel: md: correcting parity, sector=6696269280 What should my next steps be?
June 27, 201610 yr Any recent hardware upgrades? Recent upgrade from v5 to v6? You should also look at your SMART reports or post the diagnostics and run a few passes of memtest.
June 27, 201610 yr Author smart status is good for all drives; recently replaced 2tb with 6tb and prior to that had a few drive issues (5tb toshiba failed replaced with 6tb hgst as parity) otherwise no errors until recently. ill try to run memtest next time I can reboot.
Archived
This topic is now archived and is closed to further replies.