February 27, 20179 yr hi all.. i had a failed drive.. 3tb, and a parity that was 3tb also.. replacement drives i bought are all 6tbs.. so i followed the complete steps from https://lime-technology.com/wiki/index.php/The_parity_swap_procedure all went fine on the parity swap piece.. im all greens now and the data rebuild step went fine.. etcetc..i thought i was "done" so i did the final "note" step of run a parity check after its all over just to be safe etcetc... well it was going well like 80-90mb/s for many hours.. until overnight.. but at this point its CRAWLING at 4-5mb/s and im racking up millions of sync errors... note, i had zero issues on the parity copy and then the data rebuild phases.. and now all balls are green.. arrays is "up" etcetc... so is there a major issue here?.. do i let it just chug along and correct itself.. it now will take 7days to finish! but id rather be safe than sorry.. need some gurus to weigh in here... heres a current screen cap top of screen: https://www.dropbox.com/s/07adbjj0rciy2zd/unraidstatus-part1.jpg?dl=0 bottom: https://www.dropbox.com/s/s0k3pj9hp13zbwy/unraidstatus-part2.jpg?dl=0 thanks in advance for those able to offer some advice! -Matt
February 27, 20179 yr Author as per the sticky "rules" and in order to assist those who im requesting their assistance.. complete diagnostic zip is at this link https://www.dropbox.com/s/b4igpqnktbt1qso/beast-diagnostics-20170227-1046.zip?dl=0 as well... if its not obvious from the screen shots/rw stats above.. disk 8 (was the bad data drive.. that was replaced by old parity drive..) new parity is the only 6tb in the array so far. thanks again
February 27, 20179 yr Community Expert I looked at your screen shots and a very quick glance at the syslog. (I am no real expert in interpreting syslogs!) Did you preclear that 6TB drive? I suspect not. That is the reason that it is correcting parity. It is now by the 3TB point and it should only be reading (and writing) to the new parity drive. Are you sitting there watching or have the GUI screen open on your browser? The GUI can consume a lot of CPU cycles and will slow down Parity check process. I personally would close the GUI and let it run for a few hours before I checked again to see if it has sped up. (Note the Current position and Percentage so you can compare later.)
February 27, 20179 yr Author really appreciate the reply.. your assumptions are correct in all cases i think i have the gui open always and im a bit OCD about refreshing it.. ill TRUST and let it roll on its own and close all my watchings i did not preclear the 6tb before i did the swapdisableparity process,,, i was not being smart and didnt want the disabled/full state (as you can see all drives are very packed so i had this upgrade coming anyway) ok so ill let it stir on its own and no gui for a bit.. overall, this is OK.. and given the rest of how this swap worked..and that i didnt preclear prior (this was a brand new ootb drive as parity now).. this all "is correct" and my array, once finally completed, should be ok in theory?
February 27, 20179 yr Community Expert Another thought, if you are writing to the array, that will also slow down the Parity Build. After the rebuild is done, I would first check the smart report on that new parity drive. (You can quickly do this by going to the 'Main' page, click on 'Parity' under the 'Device column, then on 'Attributes'.) You are hoping to find that # 5, 196, 197, 198 are all zero. If you tend toward paranoid, you can run a non-correcting parity check and then recheck the Attributes again.
Archived
This topic is now archived and is closed to further replies.