March 3, 20179 yr On my monthly parity check error and got a ton of errors: Last check completed on Wed 01 Mar 2017 10:22:42 AM AST (two days ago), finding 7244649 errors. I have four disks one 3TB parity with 3x2TB storage. None of the disks have any errors logged and pass the extended SMART tests. Syslog shows no disk errors but on the MD recovery I can find below. Mar 1 01:00:01 caspar kernel: md: using 1536k window, over a total of 2930266532 blocks. Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=128 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=256 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=288 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=312 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=320 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=328 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=336 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=352 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=384 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=408 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=416 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=432 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=448 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=456 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=464 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=472 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=544 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=568 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=576 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=584 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=592 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=600 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=24704 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=24752 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=24760 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=25040 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=25048 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=25056 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=25088 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26008 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26016 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26024 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26032 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26448 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26456 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26624 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26632 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26640 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26648 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26656 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26664 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26672 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26680 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26688 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26696 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26704 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26712 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26720 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26728 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26736 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26744 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26752 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26760 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26768 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26816 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26824 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26832 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26840 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26848 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26864 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26872 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26880 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26888 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26896 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26904 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26912 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26920 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26928 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26936 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26944 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26952 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26960 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=26968 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=27176 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=27376 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=27688 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=27888 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=27896 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=27904 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28200 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28400 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28408 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28416 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28424 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28432 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28440 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28448 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28456 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28464 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28472 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28480 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28488 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28496 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28504 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28512 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28520 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28528 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28536 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28544 Mar 1 01:00:23 caspar kernel: md: recovery thread: P corrected, sector=28552 Mar 1 01:00:23 caspar kernel: md: recovery thread: stopped logging Edited March 3, 20179 yr by binfuser added diagnostics
March 3, 20179 yr Author There's some personal information in the syslog from the mover I don't really care to share on a public forum.
March 4, 20179 yr Community Expert 6 minutes ago, binfuser said: There's some personal information in the syslog from the mover I don't really care to share on a public forum. You can turn off mover logging for future diagnostics, Settings - Scheduler - Mover Settings. You can also edit the syslog yourself and put it back into the zip and post it. That is a lot of parity errors. Enough to make me think parity wasn't really ever valid. Had you changed the array configuration without rebuilding parity?
March 4, 20179 yr Author Just now, trurl said: You can turn off mover logging for future diagnostics, Settings - Scheduler - Mover Settings. You can also edit the syslog yourself and put it back into the zip and post it. That is a lot of parity errors. Enough to make me think parity wasn't really ever valid. Had you changed the array configuration without rebuilding parity? Thanks! I turned that off. I replaced the parity with the 3TB disk in Dec 2016. I switched the server motherboard and CPU within the last month. One thing to mention I formatted the data disks as Btrfs so I'm scrubbing those now. I intend to rebuild without that format in the next couple of weeks (new 3tb disk on the way). Edited the file and reattaching caspar-diagnostics-20170303-1828.zip
March 4, 20179 yr Community Expert I still think you somehow didn't have valid parity but I would need a lot more specific details about exactly what you did with your array. If you formatted the disks in unRAID when they were part of an array that already had valid parity, then that should have been OK since parity would have been updated during the format. Did you set a New Config at some point and tell it parity was valid? Do you know how parity works?
March 4, 20179 yr Author Followed the swap procedure here https://lime-technology.com/wiki/index.php/The_parity_swap_procedure last december. I also setup with Btrfs on initial setup of my 6.2 server a while ago. If I look at the history of the checks it was fine the prior months: Duration Speed Status Errors 2017-03-01, 10:22:42 9 hr, 22 min, 41 sec 88.9 MB/s OK 7244649 2017-02-04, 05:17:40 9 hr, 8 min, 35 sec 91.2 MB/s OK 2017-02-01, 10:12:41 9 hr, 12 min, 40 sec 90.5 MB/s OK
Archived
This topic is now archived and is closed to further replies.