July 29, 20169 yr Currently running a parity check, so far 12.8% completed in 3h42m. At this speed it's going to take almost 30hrs... Parity speed jumps between 300KB/sec and +70MB/sec. No dockers, no VMs, only 2 data drives with no cache and all 3 drives are WD Red 3TB. Attached is dianostic zip file. Thanx! gaia-diagnostics-20160729-2015.zip
July 29, 20169 yr Community Expert The more sync errors the longer it will take, are theses errors expected? Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993312 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993320 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993328 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993336 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993344 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993352 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993360 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993368 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993376 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993384 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993392 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993400 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993408 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993416 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993424 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993432 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993440 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993448 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993456 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993464 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993472 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993480 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993488 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993496 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993504 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993512 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993520 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993528 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993536 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993544 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993552 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993560 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993568 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993576 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993584 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993592 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993600 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993608 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993616 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993624 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993632 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993640 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993648 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993656 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993664 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993672 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993680 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993688 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993696 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993704 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993712 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993720 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993728 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993736 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993744 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993752 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993760 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993768 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993776 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993784 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993792 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993800 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993808 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993816 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993824 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993832 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993840 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993848 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993856 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993864 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993872 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993880 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993888 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993896 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993904 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993912 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993920 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993928 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993936 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993944 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993952 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993960 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993968 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993976 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993984 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18993992 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994000 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994008 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994016 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994024 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994032 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994040 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994048 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994056 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994064 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994072 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994080 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994088 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994096 Jul 29 07:32:37 gaia kernel: md: correcting parity, sector=18994104 Jul 29 07:32:37 gaia kernel: md: correcting parity, stopped logging
July 29, 20169 yr Community Expert Looks like you assigned all your disks then started a parity check instead of a parity sync. Maybe you could tell us a little more about how you got to this point. As johnnie mentioned correcting a lot of parity errors will take a long time. If you had done a parity sync it would have just written parity, but with a parity check it has to read, check, then write parity.
July 29, 20169 yr Author This is what I did: [*] Installed 3 drives, one parity, two data drives. No cache drive. [*] Created two shares, movies and tvshows, and fill the shares from another server. [*] Run a parity check
July 29, 20169 yr Community Expert This is what I did: [*] Installed 3 drives, one parity, two data drives. No cache drive. [*] Created two shares, movies and tvshows, and fill the shares from another server. [*] Run a parity check Did you start the array and let it build parity after installing the drives?
July 29, 20169 yr Author I believe I didn't.... Since drives were empty I assumed I didn't have to. And now that I think about it, I don't think the parity drive was empty I guess I'll have to wait, right?
July 29, 20169 yr Community Expert I believe I didn't.... Since drives were empty I assumed I didn't have to. Drives are never empty unless they have just been pre-cleared - they just do not have useful data on them And now that I think about it, I don't think the parity drive was empty The existing contents of a parity drive are irrelevant - but you do need to do a parity sync the first time to create a valid parity.
Archived
This topic is now archived and is closed to further replies.