StandaloneSealCommit: Invalid vanilla proof generated

[xiaoyuaiheshui]

My worker encountered opencl errer in the tree r last part of the p2 stage. When the rust error log failed to add final leaves, the sealed file was damaged. At this time, my p2 was already on the chain. When I started to do it again, c2 The verification fails. How do I save my sector?
error
computing seal proof failed(1): storage call error 0: StandaloneSealCommit: Invalid vanilla proof generated

[maweis1981]

Have you fixed this problem?

[mkfoyw]

you can remove filecoin-parent and filecoin-proof-parameters and download them agian 。

[mslovy]

I have a similar issue like this:

2021-06-03T02:26:31.475 INFO filcrypto::proofs::api > seal_commit_phase1: start
2021-06-03T02:26:31.475 INFO filecoin_proofs::api > validate_cache_for_precommit:start
2021-06-03T02:26:31.475 INFO filecoin_proofs::api > validate_cache_for_precommit:finish
2021-06-03T02:26:31.475 INFO filecoin_proofs::api::seal > seal_commit_phase1:start: SectorId(1924)
2021-06-03T02:26:31.475 INFO filecoin_proofs::pieces > verifying 1 pieces
2021-06-03T02:26:31.535 INFO filcrypto::proofs::api > seal_commit_phase1: finish
2021-06-03T02:26:31.536Z WARN ffiwrapper ffiwrapper/sealer_cgo.go:558 StandaloneSealCommit error: Invalid vanilla proof generated
2021-06-03T02:26:31.536Z WARN ffiwrapper ffiwrapper/sealer_cgo.go:559 num:1924 tkt:[4 217 107 208 169 163 163 159 220 67 236 81 79 1 190 240 73 74 238 26 77 153 143 217 56 154 81 193 22 22 128 30] seed:[54 17 254 210 247 227 43 200 117 205 18 153 81 104 145 112 28 128 53 8 38 203 70 65 142 107 97 65 150 41 131 24], pi:[{68719476736 baga6ea4seaqomqafu276g53zko4k23xzh4h4uecjwicbmvhsuqi7o4bhthhm4aq}] sealedCID:bagboea4b5abca6uc2tscwfknuua7g7g6jefwyihow4kttv3azz77lchbqmpsl6jy, unsealedCID:baga6ea4seaqomqafu276g53zko4k23xzh4h4uecjwicbmvhsuqi7o4bhthhm4aq

And this occurs in C1 step， and already remove filecoin-parent and retry. But it seems does not work

[mkfoyw]

export FIL_PROOFS_VERIFY_CACHE=1 when you run lotus-worker.

[Shekelme]

Is this envar described anywhere?

[LexLuthr]

@mslovy @xiaoyuaiheshui Hey, were you able to resolve this problem? How was it fixed? Do you still need help with it?

[centny]

@LexLuthr same error, already remove filecoin-parent, filecoin-paramenter, But it seems does not work
worker.log

[LexLuthr]

@centny Was this a CC sector or deal sector? We might to seal a replacement sector if the sector file has been damaged. As you can see from the logs that unsealed CID is not same as the sealed one(from the chain). So, it basically says that sector has changed since it went on the chain. Could there have been any change to the sealed sector files?
Also, does this happen during the first wdpost or is it happening for older sealed sectors?

[LexLuthr]

A new PR has been merged to double check the proofs to avoid corruption during PC1 and PC2.
#7710
Please check if this resolves your problem or not. You might have to terminate the current sector if they are not recoverable.