blackice85

I'm on Windows myself, but even then I don't use any scripts. Don't really need to if you've got a good habit of remembering to run it.

It's the latter, you'll be missing some files but not everything, as noted here. http://www.snapraid.it/faq#delandbreak With disks as large as they are nowadays, you'd have to have A LOT of changed/deleted files to completely ruin your recovery, but you never know which file(s) will be affected. More parity disks will reduce the changes of this happening. Yes 'check' is a paranoid check as stated.

That's exactly why, yes. Some people schedule scripts to run it, and they just work through a chunk every day/week or whatever. Excessive scrubbing is just needless wear and tear on your disks, but what's considered excessive is going to vary from one person to another. Too often and it's just busy work, and too seldom and you may not catch failing disks as early as you might like.

Hi, I have a question regarding using NTFS mounts with parity drives. I have SnapRAID configured and working with drive letters, but I'd rather not see the parity drives listed with my data drives in Windows Explorer. So I tried to use NTFS mounts to folders within the SnapRAID directory in order to hide them, and I altered the snapraid.conf appropriately. When I run a sync however, I'm met with the following error: Parity 'C:/SnapRAID/Parity01/snapraid.parity' and 'C:/SnapRAID/Parity01/snapraid.2-parity'...

Hi, I have a question regarding using NTFS mounts with parity drives. I have SnapRAID configured and working with drive letters, but I'd rather not see the parity drives listed with my data drives in Windows Explorer. So I tried to use NTFS mounts to folders within the SnapRAID directory in order to hide them, and I altered the snapraid.conf appropriately. When I run a sync however, I'm met with the following error: Parity 'C:/SnapRAID/Parity01/snapraid.parity' and 'C:/SnapRAID/Parity01/snapraid.2-parity'...