Frasier Crane

What can I do wrong here: snapraid diff snapraid sync snapraid status snapraid -p new scrub How can this order of commands cause errors to appear out of nowhere, where the files and harddisks obviously are ok? Also, it's not "everytime" as you cited incorrectly, but often!

No, I'm not the only one when I'm reading through this forum. On the contrary - there are quite many reports of "strange" behavior and errors of this program. I initially thought these might come from wrong usage or hardware issues, but my test (over many days) showed that there's something wrong with SR... Maybe it's only for certain configurations (like 4 data + 1 parity, huge files of tens of GB, etc.) or people simply do not add new files often, test after adding, etc. Again: perfectly fine files...

No, I'm not the only one when I'm reading through this forum. On the contrary - there are quite many reports of "strange" behavior and errors of this program. I initially thought these might come from wrong usage or hardware issues, but my test (over many days) showed that there's something wrong with SR... Maybe it's only for certain configurations (like 4 data + 1 parity) or people simply do not add new files often, test after adding, etc. Again: perfectly fine files (with correct checksums when...

I've now tested SnapRAID thoroughly with many hard disks, several computers and the result is disappointing! It's completely erratic, unreliable and faulty! Initial sync of 4 data to 1 parity runs fine, but when I change a few files (movie collection) and sync again, often there are data errors! Most of then are "unrecoverable". Content files have been reported as faulty (CRC errors), scrubbing all (14 hours) runs fine but status immediately after lists several errors, etc. Sync runs fine, but then...

I'm currently testing SnapRaid with 4x 1,5 TB data disks and one 1,5 TB parity disk. The data disks are 95% full. The disks are all connected via USB3 and they are able to read and write at about 75 MB/s. The Sync ran with approc 50 MB/s and took about 6 hours, which seems ok. I then formatted one of the data drives and I'm running Fix now - however, this is abysmally slow! The parity disk shows 100% activity in Task Manager (Windows) and reads between 0 and 1 MB/ s only! ETA is a few days (changing...

I'm currently testing SnapRaid with 4x 1,5 TB data disks and one 1,5 TB parity disk. The data disks are 95% full. The disks are all connected via USB3 and they are able to read and write at about 75 MB/s. The Sync ran with approc 50 MB/s and took about 6 hours, which seems ok. I then formatted one of the data drives and I'm running Fix now - however, this is abysmally slow! The parity disk shows 100% activity in Task Manager (Windows) and reads between 0 and 1 MB/ s only! ETA is a few days (changing...

I'm currently testing SnapRaid with 4x 1,5 TB data disks and one 1,5 TB parity disk. The data disks are 95% full. The disks are all connected via USB3 and they are able to read and write at about 75 MB/s. The Sync ran with approc 50 MB/s and took about 6 hours, which seems ok. I then formatted one of the data drives and I'm running Fix now - however, this is abysmally slow! The parity disk shows 100% activity in Task Manager (Windows) and reads between 0 and 1 MB/ s only! ETA is a few days (changing...

Why MountPoints? Seems to be (mount)pointless... Try understanding my post: I have several sets of 3 data disks, that are connected to the PC maybe once a week for backup purposes (hot-plug). No matter which set I use, they will always be drives E., F. G: and H: )for parity). This way, I do not need to change the conf file, all set-dependent data is stored in the contents files on the respective discs. This is easy and elegant. However, the serious FLAW of SnapRaid makes it dangerous, because it...