January 6, 20179 yr Hi there, I have recently made a lot of changes to my system, including going to dual parity. Since my case is full, I now have one less data disk, and the one I took out was my last 2TB green which was disk 6 - right in the middle. On single parity, I know you could just stop the array, move the drive to a new slot and start it back up again. I suspect this is no longer the case with dual parity, but I can't seem to find any details on this - other then a single comment from garycase this morning here: https://lime-technology.com/forum/index.php?topic=55042.msg527662#msg527662 What is the procedure for moving a disk in dual parity land? Is there one? should i just ignore the fact that my array is missing one consecutive disk number?
January 6, 20179 yr Community Expert Leave it as is or move it, if you move it and do a new config parity will stay valid, parity2 will need to be re-synced.
January 6, 20179 yr Leave it as is or move it, if you move it and do a new config parity will stay valid, parity2 will need to be re-synced. I don't have a dual parity system, so I was wondering... Is there a way to force parity valid that differentiates between parity1 and parity2? Or when you set a new config do you leave parity2 unassigned, set parity as valid, start the array, stop the array, assign parity2, let it build? Or assign both, set parity as valid, and start a correcting check to rebuild parity2? If you use the last option, is there a huge speed penalty like there is when you use a correcting check to build parity1? Inquiring minds want to know.
January 6, 20179 yr Community Expert Or when you set a new config do you leave parity2 unassigned, set parity as valid, start the array, stop the array, assign parity2, let it build? This would be the best way, there's no way to trust parity independently and correcting the errors would take much longer.
Archived
This topic is now archived and is closed to further replies.