December 3, 201510 yr Version 5.0-rc11 Are there any procedures for swapping parity drives? Going from a 4TB to a 6TB. Thanks
December 4, 201510 yr Assuming a very recent clean parity check, stop the array, take a backup of the flash drive, do a proper power down and remove / replace the drive, then start up, assign the new drive in the missing parity slot and rebuild parity. Make sure all your drives have clean smart reports, it would suck to be in the middle of a drive replacement and have another drive fail on you. BTW, you really ought to investigate upgrading to the current v6, running such an old non-final version is bound to bite you at some point.
December 4, 201510 yr You're better off upgrading FIRST ... and then doing the parity upgrade. Reason: v6.1.5 fixes the "trust parity" option, so a New Config with "trust parity" doesn't start a parity check. This means that if a drive was to fail during the rebuild of the larger parity disk, you could recover the data from it by doing a New Config using the OLD parity disk with the "Trust Parity" option and then rebuild the failed drive. Before this was fixed, the immediate parity check could result in some "corrections" that actually corrupted the parity data -- and would not result in a successful rebuild of a disk in this situation.
December 4, 201510 yr Author You're better off upgrading FIRST ... and then doing the parity upgrade. Reason: v6.1.5 fixes the "trust parity" option, so a New Config with "trust parity" doesn't start a parity check. This means that if a drive was to fail during the rebuild of the larger parity disk, you could recover the data from it by doing a New Config using the OLD parity disk with the "Trust Parity" option and then rebuild the failed drive. Before this was fixed, the immediate parity check could result in some "corrections" that actually corrupted the parity data -- and would not result in a successful rebuild of a disk in this situation. OK makes sense to me. I will do the upgrade first. Thanks for the info. Darryl
Archived
This topic is now archived and is closed to further replies.