-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Sync wont start when there sync diff is zero but sync incompleted #109
Comments
I'm trying to recap because I'm not sure I've understood correctly what you mean.
What is your ask? |
I run the snapraid sync but did not complete due to system crashed However when checked found Problem is the script only rely on snapraid diff to decided if it need to run snapraid sync |
Got it. To resolve this problem, the script should also run a I'll look into this and update this issue accordingly. |
Hey! The feature is now in the dev branch. The script runs the snapraid status in the pre-check stage and stops if there are issues. Let me know if you need more information. |
Testing it .. will revert if found there is issue.. thanks for the patch.. appreciate it |
I had same error and when trying the new version the sync won't start saying: "[WARNING] - Previous SnapRAID sync did not complete correctly." setting the script config to always force the sync wont fix it |
At the moment that's intentional: I haven't included a remediation for this case. The script is not interactive so I don't think there is a nice way to override this problem. Let me know what you think. To proceed, run |
The system crashed last sync this the sync did not completed
Sync scrub runs fine here
SnapRAID Status
Yes. i know the version is abit old but i check your latest code and its not fix
SnapRAID AIO Script version 3.2
When running snapsync status, error below should give some warning or start sync
"WARNING! The array is NOT fully synced."
When the sync is really completed. This is the logs
"SYNC - Everything OK"
The text was updated successfully, but these errors were encountered: