July 30, 200619 yr Just wondering how often people do this? I have been adding a bunch of drives over the weekend and copying over lots of gigs. Also, I don't see the speed problems people speak of when copying files... things seem to run very fast and smooth for me. Thank you, Mike
July 31, 200619 yr The speed thing is because normally you're moving large files from a Windows box over to the UnRaid which does take a long time. A single 5GB DVD folder can take around 15 minutes on a 100GB network where moving the same folder from one disk to the another on the UnRaid using native LINUX commands from a Telnet session takes maybe 5 minutes or less. Running a manual Parity check is in theory NEVER really required because as data is written to and removed from the array Parity is always updated and is always accurate. The only reason I run a manual Parity is to give all the drive a little exercise as they sit spun down most of the time. It also may (or may not) help to identify a drive that is getting flaky on you that otherwise you may not know. I generally run on once a week, kick it off before bed and it's done when I get up in the morning.
July 31, 200619 yr Author Thank you so much for the information. I was never sure if I should run it, how often.. etc You summed it all up and makes complete sense. I am definitely loving my UnRaid server so far. I have sent 5 hard drives in for warranty so I can't wait to expand the array with 5 more
July 31, 200619 yr To all, I believe that a while back Tom recommended running a parity check at least once a month. I telnet to the server I plan to run the parity check on and then initiate the parity check. I check the telnet window about once an hour to see how things are going. So far I have never had a parity check hang. Regards, TCIII
September 1, 200619 yr Once a month here and most certainly after a Fsck. (lol) I've only ever had an issue once or twice and that after a reboot that wasn't planned nor gentle. The Fsck was run with the drives offline and it made a bunch of fixes to the drive structure so parity most certainly had to be run to update things. Barring all those kinds of oddball situations I can go a month or more without running it and have zero errors.
Archived
This topic is now archived and is closed to further replies.