January 21, 201115 yr Couldn't find an answer searching the forum, hopefully someone can help me out. I just put together my box and ran the preclear script on my first 2 drives. I assigned one to Disk1 and one to Parity. Do I need to wait for the parity rebuilding to finish now before I can copy data over? I'm thinking I should have done that before assigning the parity... anything I can do at this point? If I stop the parity, copy data over, then restart the parity building will it cause problems? Parity rebuild is estimated to take 576 hours so I didn't want to wait to get all my data over. I'm holding off on touching anything until I get some advice from someone much more advanced than myself. Thanks!
January 21, 201115 yr Couldn't find an answer searching the forum, hopefully someone can help me out. I just put together my box and ran the preclear script on my first 2 drives. I assigned one to Disk1 and one to Parity. Do I need to wait for the parity rebuilding to finish now before I can copy data over? I'm thinking I should have done that before assigning the parity... anything I can do at this point? If I stop the parity, copy data over, then restart the parity building will it cause problems? Parity rebuild is estimated to take 576 hours so I didn't want to wait to get all my data over. I'm holding off on touching anything until I get some advice from someone much more advanced than myself. Thanks! You can start copying your data now. Or wait until the parity calc is complete. It would work either way. Or, cancel the parity calc, un-assign the parity drive perform the initial data migration AND verification, then assign parity. It will be faster that way for most people, but you MUST do the data verification since you are writing to a disk and there is no way to know the writes are successful until you go to read it. At least with a parity disk initially assigned you can perform a parity check. Assigning parity after loading data just builds parity with the data read from the data disk, even if the data written wad bad. It is why the verification is so important. Joe L.
January 21, 201115 yr 576 hours is a rediculously long time and if that is true you have a problem. Did you hit the refresh button on the web interface a few times? Each refresh will show new numbers. The speed should typically be in the 50,000k to 90,000k range. Peter
January 21, 201115 yr 576 hours is a rediculously long time and if that is true you have a problem. Did you hit the refresh button on the web interface a few times? Each refresh will show new numbers. The speed should typically be in the 50,000k to 90,000k range. Peter Wow... I must have my second cup of coffee... I mis-read that as minutes... thinking 576 minutes sounds OK Going to poor another cup now... Joe L
January 21, 201115 yr Author Oops, sorry guys! 576 minutes, indeed... misread it myself also! I knew hours sounded extremely long. Thanks for the suggestions. I'll probably leave the parity as it is and simply start moving data.
Archived
This topic is now archived and is closed to further replies.