November 12, 201411 yr Author In what PCIe is the Perc200? X4 or x8 or x1 perhaps? Perferably an x8. Why don't you use the M1015? It seems you have a severe bandwidth problem. x8 slot.
November 12, 201411 yr That Perc H200 doesn't seem terrific. http://community.spiceworks.com/topic/342020-perc-h200-performance-issues Read the replies further down too.
November 15, 201411 yr Author ok, so finally my parity of the new drive is valid. No parity-check yet. should i continue with replacing one of the existing drives with a new drive, or do a parity-check first? no errors at all.
November 15, 201411 yr ok, so finally my parity of the new drive is valid. No parity-check yet. should i continue with replacing one of the existing drives with a new drive, or do a parity-check first? no errors at all. Do the parity check. In all probability, it will be fine. However if it isn't, you will have an opportunity to fix that problem. If you simply replace the existing drive and the rebuilt fails, you now have two problems to address.
November 15, 201411 yr the parity check will take time as much as building the parity, right? Well. the parity check on my 3Tb array takes a bit over 7 plus hours. So (on my system), the time would be about 15 hours. I presume you will be doing a non-correcting parity check and, if you get really impatient, you could terminate it without any harm. Remember, that once the parity check has verified that parity is good for the largest data drive(s) in the system, the only thing you are doing after that point is verifying that you can read the parity drive--- So you could stop the check at that point.
November 16, 201411 yr Remember, that once the parity check has verified that parity is good for the largest data drive(s) in the system, the only thing you are doing after that point is verifying that you can read the parity drive--- So you could stop the check at that point. At this point you are also verifying the fact that the data on the parity drive is correct for the case when you later add a new drive of similar size to parity. I agree that aborting a parity check at the point it has passed the size of the largest data drive is OK in the short term, but I would not make a habit of doing it.
November 16, 201411 yr ... I agree that aborting a parity check at the point it has passed the size of the largest data drive is OK in the short term ... While it's "okay" in the sense that it won't impact any of your current data if it's wrong in the unchecked area, it's NOT "okay" in the sense that it tells you anything about the status of parity for the unchecked area. If a bit was, in fact, wrong, then if you later added a drive; had a problem with the new drive; and did a rebuild, the data would be WRONG, since the parity drive would have never been corrected. I'd simply NOT abort the check => it's a good idea to KNOW that your initial parity sync worked perfectly. ... but I would not make a habit of doing it. Obviously I agree ... in fact I've NEVER do it
Archived
This topic is now archived and is closed to further replies.