I just upgraded my parity drive.  That appeared to run just fine.  It rebuilt fine.  No visible errors.

 

So I stopped the array and started it again in full mode. (it was in maintenance mode for the rebuild)

Disk 1 came up red balled.  No I think it was just a fluke.  I ran smart on it and it seemed fine.

 

So I did the new config, reassigned all the drives and did the 'my parity is valid" and the array came up fine.

 

So I started a parity check (non correcting) to be sure.  I got 20 errors right off the bat.

I restarted the check again and I got 20 errors again.  It was right away.

 

The parity check is chugging along with no more errors - just the initial 20

 

What should I do??

 

Thanks,

 

Jim

I would not worry about the 20 early parity errors. This is somewhat to be expected if a drive red balls and you reinsert it into the array. The data on the drive takes precedence and parity is updated to match.

 

One question - when you added the new disk - did you open the case and physically install it or do you have drive cages and able to add drives without opening the case?

I would not worry about the 20 early parity errors. This is somewhat to be expected if a drive red balls and you reinsert it into the array. The data on the drive takes precedence and parity is updated to match.

 

One question - when you added the new disk - did you open the case and physically install it or do you have drive cages and able to add drives without opening the case?

Ok..  so I can go ahead and not check the "do not correct parity" and re run the parity check? (so it will update the parity drive)

 

and yes I have drive cages...  Best money I spent!!

And it's currently at 300G with no more errors.

 

Jim

You didn't copy any files to that drive since it red balled, correct?

 

If not, I think I'd let it finish. Probably it won't find any more.

 

Then run a correcting check. If there were no more mismatches you'd only have to run it a few seconds.

 

Alternatively you could stop the non-correcting check and start a correcting check and let it run all the way through.

You didn't copy any files to that drive since it red balled, correct?

 

If not, I think I'd let it finish. Probably it won't find any more.

 

Then run a correcting check. If there were no more mismatches you'd only have to run it a few seconds.

 

Alternatively you could stop the non-correcting check and start a correcting check and let it run all the way through.

No write to the drive.  I just stopped the check and started the correcting one.

 

I dying to preclear my old parity disk so I can add it in to the system to increase space!

I guess the pre-clear will wait one more day!  At least the array is back on line...

 

Thanks,

 

jim