Leifi Plomeros

I can't see anything wrong and sync is doing progress. So I guess you should simply run sync again to let it finish and then pay extra attention on diff and status for the next few syncs.

Something definitely went wrong. I would recommend to press CTRL + C to stop current sync and pay close attention to what happens. Expected output: bla bla interrupted bla bla Saving state to content files bla bla bla verifying content files bla bla bla Everything OK Verify that above happened as expected. Then run snapraid status to confirm that progress % is around what would be expected for the amount of time it has been running. run snapraid diff to confirm that, from snapraids perspective, nothing...

Something definitely went wrong. I would recommend to press CTRL + C to stop current sync and pay close attention to what happens. Expected output: bla bla interrupted bla bla Saving state to content files bla bla bla verifying content files bla bla bla Everything OK Verify that above happened as expected. Then run snapraid status to confirm that progress % is around what would be expected for the amount of time it has been running. run snapraid diff to confirm that, from snapraids perspective, nothing...

Something definitely went wrong. I would recommend to press CTRL + C to stop current sync and pay close attention what happens. Expected output: bla bla interrupted bla bla Saving state to content files bla bla bla verifying content files bla bla bla Everything OK Verify that above happened as expected. Then run snapraid status to confirm that progress % is around what would be expected for the amount of time it has been running. run snapraid diff to confirm that, from snapraids perspective, nothing...

using sudo snapraid --conf /etc/snapraidNA2.conf list does not show me what disk # the files are on You can add this parameter to see full path in list: --test-fmt path

Yes, fix is supposed to be slower than sync and scrub. I guess the good part about that, is that my new server works fine :) during such operations you are more interested in reliability than in performance I can't imagine anyone disagreeing with that. pushing the system to its limit is likely not a good idea I think that this is starting to become a bit less true, here in the future. More specificially, it turns out that my ~1.5 days recovery time was only to recover about 6-7 TB. My largest disk...

Yes, fix is supposed to be slower than sync and scrub. I guess the good part about that, is that my new server works fine :) during such operations you are more interested in reliability than in performance I can't imagine anyone disagreeing with that. pushing the system to its limit is likely not a good idea I think that this is starting to become a bit less true, here in the future. More specificially, it turns out that my ~1.5 days recovery time was only to recover about 6-7 TB. My largest disk...

Yes, fix is supposed to be slower than sync and scrub. I guess the good part about that, is that my new server works fine :) during such operations you are more interested in reliability than in performance I can't imagine anyone disagreeing with that. pushing the system to its limit is likely not a good idea I think that is starting to become a bit less true, here in the future. More specificially, it turns out that my ~1.5 days recovery time was only to recover about 6-7 TB. My largest disk is...