luca Posted July 30, 2010 Share Posted July 30, 2010 It's pretty much all in the subject. I've just replaced a 1.5GB drive with a WD20EARS. Booted up no problem, and the system is currently "upgrading parity". I admit I had forgot all about setting the jumper on the new drive to force the sector size. Does this 512 sector requirement apply to the parity drive? IOW, should I shut everything down and set the jumper, or can I leave it? I am using unRAID pro 4.5.3. thanks, Luca Link to comment
Joe L. Posted July 30, 2010 Share Posted July 30, 2010 It's pretty much all in the subject. I've just replaced a 1.5GB drive with a WD20EARS. Booted up no problem, and the system is currently "upgrading parity". I admit I had forgot all about setting the jumper on the new drive to force the sector size. Does this 512 sector requirement apply to the parity drive? IOW, should I shut everything down and set the jumper, or can I leave it? I am using unRAID pro 4.5.3. thanks, Luca The jumper does not force sector size. It simply changes sector alignment. Yes, set the jumper on the parity drive. You can leave it but your performance will be slower. Best bet is to Stop the array un-assign the parity drive Start the array with out it assigned (This will cause it to forget the old parity drive model/serial number) Stop the array power down Set the jumper Power up Assign the parity drive once more (It will think it is a new parity drive because it forgot the model/serial number in the prior step) Let it do a full parity calc. Joe L. Link to comment
luca Posted July 31, 2010 Author Share Posted July 31, 2010 The jumper does not force sector size. It simply changes sector alignment. Yes, set the jumper on the parity drive. You can leave it but your performance will be slower. Best bet is to Stop the array un-assign the parity drive Start the array with out it assigned (This will cause it to forget the old parity drive model/serial number) Stop the array power down Set the jumper Power up Assign the parity drive once more (It will think it is a new parity drive because it forgot the model/serial number in the prior step) Let it do a full parity calc. Thanks Joe, I'm following your advice. Do you have any estimates about how much this re-alignment issue hinders performance? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.