Craig Hogan

Thanks for the info. So keep fixing and re-scrubbing? It's version 10.0. Here's the status output: root@area51:~# snapraid status Self test... Loading state from /var/snapraid/snapraid.content... Using 292 MiB of memory for the FileSystem. SnapRAID status report: Files Fragmented Excess Wasted Used Free Use Name Files Fragments GB GB GB 41999 20 26 6.4 1368 1625 45% d1 48004 253 354 10.3 2148 841 71% d2 90003 273 380 16.7 3517 2466 58% 6%| | | | | | | * 3%| * * * | * * * * * * * * * * | * * * * *...

Thanks for the info. So keep re-scrubbing? It's version 10.0. Here's the status output: root@area51:~# snapraid status Self test... Loading state from /var/snapraid/snapraid.content... Using 292 MiB of memory for the FileSystem. SnapRAID status report: Files Fragmented Excess Wasted Used Free Use Name Files Fragments GB GB GB 41999 20 26 6.4 1368 1625 45% d1 48004 253 354 10.3 2148 841 71% d2 90003 273 380 16.7 3517 2466 58% 6%| | | | | | | * 3%| * * * | * * * * * * * * * * | * * * * * * * * * *...

I recently lost a parity disk. I generated a new parity file which is on an external USB 3.0 drive mounted in Ubuntu server 18.04. Each time I do a scrub it reports thousands of data errors. Then I run fix, and fix reports that it fixed all of those errors. But when I run scrub again, it finds thousands of new errors. Rinse and repeat 10+ times and it never goes away. The check command thinks everything is fine. It's only scrub telling me there are errors. What is the best course of action here?...

I recently lost a parity disk. I generated a new parity file which is on an external USB 3.0 drive mounted in Ubuntu server 18.04. Each time I do a scrub it reports thousands of data errors. Then I run fix, and fix reports that it fixed all of those errors. But when I run scrub again, it finds thousands of new errors. Rinse and repeat 10+ times and it never goes away. What is the best course of action here? Should I keep doing this over and over? Start fresh with a new parity disk and file? Here's...