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
Sector (No.) , running PreCommit2 error: sealed cid mismatching!!! #16
Comments
Interesting. never saw this before. @FroghubMan can you help here. |
I am trying to do a re-recovery for such sectors, but it does not help in all cases. |
@Shekelme Can you provide your miner id and sector number? maybe we can try one recovery test. |
The numbers are all in OP ) |
Looks great. |
If a small number of sectors cannot be recovered after repeated attempts, it is recommended to terminate as soon as possible. |
I am very curious, what kind of zfs failure caused sector data loss? |
In recent days, my worker machines have been very busy. There may be no way to help you. |
And a fresh one: 6028 |
I found that the probability of being unable to recover is greater than 1%. I have tested many sectors and it seems that they are basically unable to recover. Now I still can't find the reason. I even modified the code myself, cancelled nodeapi and manually passed in ticket. In either case, the recovered CID is incorrect |
@s1mple1122 you should check your chain data source if you have a larger portion of sectors that can't recover. maybe try to use a full node |
The following error occurs on some recovered sectors:
What causes it and how to fix it?
The text was updated successfully, but these errors were encountered: