Hello, long time user of snapraid here. Thank you, Andrea, for creating this great piece of software! My home server's system drive recently broke down, so I had to do a fresh OS install. I installed the latest version of snapraid (9.3) and copied my old snapraid configuration file into place. To ensure that the data and parity drives were intact I ran a "snapraid check", which reported this:
msg:status: 3753208 errors
msg:status: 0 unrecoverable errors
msg:fatal: WARNING! There are errors!
summary:error:3753208
summary:error_unrecoverable:0
summary:exit:recoverable
"snapraid status" reported "no error detected" and "snapraid diff" showed:
Snapraid wouldn't find any errors to fix. Tried running a full scrub - "snapraid scrub -p 100":
msg:progress: Scrubbing...
msg:status: Everything OK
summary:error_file:0
summary:error_io:0
summary:error_data:0
summary:exit:ok
For some reason "check" finds errors while "scrub" doesn't. Tried running "snapraid -e fix" again in case the scrub had made some difference. Still nothing fixed. As a final test I re-ran "snapraid check" to verify that the errors were still being reported:
msg:status: 3753208 errors
msg:status: 0 unrecoverable errors
msg:fatal: WARNING! There are errors!
summary:error:3753208
summary:error_unrecoverable:0
summary:exit:recoverable
What else can I try to get rid of the errors reported by "snapraid check"? Could it be an issue that the content and parity files were created by an older version of snapraid than the one I'm currently using?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Almost a month later and no response... these forums don't seem very helpful.
But anyways, I was having the same issue. I upgraded from SnapRAID 9.1 to 10.0 and then ran the "check" command and got 16 thousand something errors. Then I ran "sync" and it didn't find any new files. Then I ran "check" again and get the same errors. Then I did "scrub" and it didn't find any errors either.
Finally I just wiped my parity drives and then did a sync with "--force-full". Then I ran a "check" again and this time it came back with 0 errors.
I'm guessing maybe each time we upgrade SnapRAID versions, then we have to rebuild our parity? Maybe Andrea can chime in on this...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I haven't had this exact problem, however I've run into upgrades where it produced errors and it wasn't until I was watching the console and saw what the error was that I was able to resolve it.
Did either of you watch the console for the error or see it in the logs somewhere? What are they?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried looking through the logs to see what the errors were or which files were giving the errors, but I did not see any errors except at the end when SnapRAID finishes and prints the summary.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have gone through seven or so different versions of snapraid and never had to rebuild my parity drives, so I dont think the version has anything to do with this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, long time user of snapraid here. Thank you, Andrea, for creating this great piece of software! My home server's system drive recently broke down, so I had to do a fresh OS install. I installed the latest version of snapraid (9.3) and copied my old snapraid configuration file into place. To ensure that the data and parity drives were intact I ran a "snapraid check", which reported this:
"snapraid status" reported "no error detected" and "snapraid diff" showed:
I tried fixing the errors by running "snapraid -e fix":
Snapraid wouldn't find any errors to fix. Tried running a full scrub - "snapraid scrub -p 100":
For some reason "check" finds errors while "scrub" doesn't. Tried running "snapraid -e fix" again in case the scrub had made some difference. Still nothing fixed. As a final test I re-ran "snapraid check" to verify that the errors were still being reported:
What else can I try to get rid of the errors reported by "snapraid check"? Could it be an issue that the content and parity files were created by an older version of snapraid than the one I'm currently using?
Almost a month later and no response... these forums don't seem very helpful.
But anyways, I was having the same issue. I upgraded from SnapRAID 9.1 to 10.0 and then ran the "check" command and got 16 thousand something errors. Then I ran "sync" and it didn't find any new files. Then I ran "check" again and get the same errors. Then I did "scrub" and it didn't find any errors either.
Finally I just wiped my parity drives and then did a sync with "--force-full". Then I ran a "check" again and this time it came back with 0 errors.
I'm guessing maybe each time we upgrade SnapRAID versions, then we have to rebuild our parity? Maybe Andrea can chime in on this...
I haven't had this exact problem, however I've run into upgrades where it produced errors and it wasn't until I was watching the console and saw what the error was that I was able to resolve it.
Did either of you watch the console for the error or see it in the logs somewhere? What are they?
I tried looking through the logs to see what the errors were or which files were giving the errors, but I did not see any errors except at the end when SnapRAID finishes and prints the summary.
I have gone through seven or so different versions of snapraid and never had to rebuild my parity drives, so I dont think the version has anything to do with this.