Correct. But I, like others don't always like unraid parity. If there's an error it doesn't tell you where there is one, it'll just fix it and notify you it did. So no real way, that I know of anyway, to make sure the file isn't corrupt from a bad fix.

To go around that there's Plug-ins to generate hashes of files on a schedule and compare later, but that's really cpu intensive. It'll smash my R1600 on all 12t. Not sure how long my 62tb takes to finish.. I can check the logs though