ERROR node.atxBuilder failed to generate initial proof: {"error": "post execution: error generating proof: status:GEN_PROOF_STATUS_ERROR"}

[Pheal22]

Environment

• Smapp version: 1.6.4 | develop
• Node version: v0.x.xx
• OS: Windows 10 | macOS High Sierra (10.13) | Ubuntu 20.04

Describe the bug

Power outage caused issues with node (JS errors on startup) so decided to reinstall Smapp and relink to the POStT data Dir. All seemed ok, Startup OK, Node sync OK, Smesh working and finally network working. In the background I can see that there is POST proof generation process going and can see this process incrementing through each of the postdata files. Once this reaches the last file I get the following:
2024-07-23T23:38:37.952+0100 INFO node [2024-07-23T22:38:37Z ERROR post_service::client] failed proof verification: verifying proof {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100 INFO node {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100 INFO node Caused by: {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100 INFO node MSB value for index: 558055458 (id: 0) doesn't satisfy difficulty: 65 > 0 (label: [102, 222, 93, 42, 5, 119, 69, 231, 117, 92, 108, 230, 216, 97, 14, 125]) {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100 INFO node {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100 INFO node Location: {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100 INFO node service\src\service.rs:208:14 (verification took: 0.6584143s) {"smesherID": "d2119a"}
2024-07-23T23:38:37.952+0100 ERROR node.atxBuilder failed to generate initial proof: {"error": "post execution: error generating proof: status:GEN_PROOF_STATUS_ERROR"}

The process then loops through restarts and fails over and over. I cannot find and references to lookup regarding node.atxBuilder so am at a loss what to attempt. Any ideas please as not want to go through another 2 month postdata build again!
Running on windows 10 with latest version.

Steps to reproduce

app-log.1.6.6.txt
spacemesh-log-7c8cef2b.txt

Try to narrow down your scenario to a minimal working/failing example. That is, if you have a big program causing a problem, start with deleting parts not relevant to the issue and observing the result: is the problem still there? Repeat until you get the most straightforward sequence of steps to reproduce the problem without any noise surrounding it.

1. Open this
2. Press that
3. Click here and there

Expected behavior

What should happen?

Actual behavior

What’s happening now?

Attach screenshots or GIF’s of what’s going on if it makes the issue more illustrative.

Logs

Attach app-logs.txt and spacemesh-log.txt

If you can find out the part of the logs that relates to the problem, attach them or paste in code-block.

How to fix

If you have an idea of how the bug can be fixed, provide a short description.

[mayur-s-ops]

Have you been able to resolve this @Pheal22? I am in the same boat as you and don't really know how to resolve the issue.

[Pheal22]

No luck i'm afraid. Tried running postcli to check the postdata files for errors and it seemed that all had an issue which to me implies that there was a mismatch between keys (post crash system vs new system). Tried to ensure all keys matched the old system but unable to resolve so undergoing a month(+) re-generation of post data. So annoying!!