Thanks. So this means 60 hours is expected for a new parity drive on a 60TB array ? What is the logical reason it doesn't just copy the parity file from the Parity 1 drive ? Obviously there must be a logical reason but as a layman I am not sure what.
I just added a second parity disk to my array (after using just 1 parity for the last year or so) adding the below in config........ 2-parity C:\Mounts\PARITY2\snapraid.2-parity Then I ran a full force sync (using Elucidate) as mentioned in the FAQ, and it says it will take 66 hours to complete. Why doesn't it just duplicate the large file from the 1st parity which would copy across much quicker ?? I am not using split parity. It looks like it is going to go through every file on all 11 hard disks,...
I just installed a new 8TB drive and my parity drive is 8TB. I am being warned the new drive is a few MB larger than the parity drive. I use DrivePool so I limit my data drives to 90% of total. Does this mean I should be okay ? If so could I even push it up to 95% and still be okay because the data on it is less than the parity drive ? Or does it matter even if the drive itself is larger even if data stored isn't ? Thanks.
I normally use Elucidate for SnapRaid but there is no documentation on how to use that for repairing a drive. I saw the SnapRaid info on how to repair but I am still confused. A 6tb drive failed on me and I need to repair it asap. I have removed the broken drive and replaced it with a new one. But because I use DrivePool I don't use drive letters, I have mounted folder. If I post my config page below can anyone help me ? It is D2 that has failed. Do I need to change the drive letter of the new drive...
Thanks again. I have read a lot about "overheads" for the parity drive on forums. One of my data drives is 8TB and is 99.4% full up with 28,000 files on it. Will my 8TB parity drive cope okay ? My sync is taking forever, dropped from 380MB/S on the first day to 90MB now on day 2. I am just worried it will get to near the end and then tell me the parity drive is not big enough. I have 34TB of data so I guess I can expect this first sync to be loooong.
Thanks !! I am now just about to run my first sync, fingers crossed. I have put a content file on every disk drive bar the parity drive, some say this is overkill but many seem to do this, yes ? Just a hypothetical question in case this happens. If I want to upgrade one of my HDDs to a bigger one, lets say D3 for example, how would I go about that given I use both DrivePool and SnapRAID ? Below is my config file if it helps explain the answer. Thanks again for you excellent help, it has been really...
Thanks !! I am now just about to run my first sync, fingers crossed. I have put a content file on every disk drive bar the parity drive, some say this is overkill but many seem to do this, yes ? Just a hypothetical question in case this happens. If I want to upgrade one of my HDDs to a bigger one, lets say D3 for example, how would I go about that given I use both DrivePool and SnapRAID ? Below is my config file if it helps explain the answer. Thanks again for you excellent help, it has been really...
Thanks !! I am now just about to run my first sync, fingers crossed. I have put a content file on every disc bar the parity drive, some say this is overkill but many seem to do this, yes ? Just a hypothetical question in case this happens. If I want to upgrade one of my HDDs to a bigger one, lets say D3 for example, how would I go about that given I use both DrivePool and SnapRAID ? Below is my config file if it helps explain the answer. Thanks again for you excellent help, it has been really helpful...