# Restore snapshot checksum problem (Troubleshooting corruption)

**URL:** <https://discuss.elastic.co/t/restore-snapshot-checksum-problem-troubleshooting-corruption/369764>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [October 29, 2024, 7:10pm UTC](https://discuss.elastic.co/t/restore-snapshot-checksum-problem-troubleshooting-corruption/369764 "2024-10-29T19:10:42Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![IgorSim](https://avatars.discourse-cdn.com/v4/letter/i/3d9bf3/32.png) [@IgorSim](https://discuss.elastic.co/u/IgorSim)\
**Post date:** [April 1, 2025, 12:16pm UTC](https://discuss.elastic.co/t/restore-snapshot-checksum-problem-troubleshooting-corruption/369764/21 "2025-04-01T12:16:17Z")

</div>

Unfortunately it's not that easy (at least not in next quarter) to upgrade to 8.17 for various reasons but we'll definitely consider upgrading to more recent versions of ES.

Here is the error.

```auto
{
  "error": {
    "root_cause": [
      {
        "type": "repository_verification_exception",
        "reason": "[transaction-log] register [test-register-9UxQpoW3T4CnILP7csWraw] should have value [10] but instead had value [OptionalBytesReference[MISSING]]",
        "suppressed": [
          {
            "type": "repository_verification_exception",
            "reason": "[transaction-log] failure processing [blob analysis [transaction-log: temp-analysis-r190NeMWQh-3xSzWrTdkJg/test-blob-20-XYRw2e1nSSepBrqBojm7ZQ, length=32768, seed=7696665789984602171, readEarly=false, writeAndOverwrite=false, abortWrite=false]]"
          },
          {
            "type": "repository_verification_exception",
            "reason": "[transaction-log] failure processing [blob analysis [transaction-log: temp-analysis-r190NeMWQh-3xSzWrTdkJg/test-blob-17-WNV_jknSTkyskYpb3f3xpw, length=262144, seed=5055718760755192637, readEarly=false, writeAndOverwrite=false, abortWrite=false]]"
          },
          {
            "type": "repository_verification_exception",
            "reason": "[transaction-log] failure processing [blob analysis [transaction-log: temp-analysis-r190NeMWQh-3xSzWrTdkJg/test-blob-14-IcUPELNyQriW8GwieptCVA, length=1048576, seed=-5087821163508988974, readEarly=false, writeAndOverwrite=false, abortWrite=false]]"
          },
          {
            "type": "repository_verification_exception",
            "reason": "[transaction-log] failure processing [blob analysis [transaction-log: temp-analysis-r190NeMWQh-3xSzWrTdkJg/test-blob-18-ITETVXF1Qta7mbSt9dnPEg, length=256, seed=225571677622846146, readEarly=false, writeAndOverwrite=false, abortWrite=false]]"
          },
          {
            "type": "repository_verification_exception",
            "reason": "[transaction-log] failure processing [blob analysis [transaction-log: temp-analysis-r190NeMWQh-3xSzWrTdkJg/test-blob-12-8nAYwSvDS2qMg9RY4xh2Ug, length=4194304, seed=-8174703883422034556, readEarly=false, writeAndOverwrite=false, abortWrite=false]]"
          }
        ]
      }
    ],
    "type": "repository_verification_exception",
    "reason": "[transaction-log] analysis failed, you may need to manually remove [temp-analysis-r190NeMWQh-3xSzWrTdkJg]",
    "caused_by": {
      "type": "repository_verification_exception",
      "reason": "[transaction-log] register [test-register-9UxQpoW3T4CnILP7csWraw] should have value [10] but instead had value [OptionalBytesReference[MISSING]]",
      "suppressed": [
        {
          "type": "repository_verification_exception",
          "reason": "[transaction-log] failure processing [blob analysis [transaction-log: temp-analysis-r190NeMWQh-3xSzWrTdkJg/test-blob-20-XYRw2e1nSSepBrqBojm7ZQ, length=32768, seed=7696665789984602171, readEarly=false, writeAndOverwrite=false, abortWrite=false]]",
          "caused_by": {
            "type": "execution_cancelled_exception",
            "reason": "operation was cancelled reason [task failed]",
            "suppressed": [
              {
                "type": "repository_verification_exception",
                "reason": "[transaction-log] blob upload cancelled at position [0+32768/32768]"
              }
            ]
          }
        }
      ]
    }
  },
  "status": 500
}

```

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 1, 2025, 1:15pm UTC](https://discuss.elastic.co/t/restore-snapshot-checksum-problem-troubleshooting-corruption/369764/22 "2025-04-01T13:15:30Z")

</div>

Definitely suggests anomalous behaviour yes.

You don't necessarily need to upgrade your production cluster to 8.17, but it would be good if you could try the same tests using a standalone 8.17 node.

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [April 1, 2025, 3:32pm UTC](https://discuss.elastic.co/t/restore-snapshot-checksum-problem-troubleshooting-corruption/369764/23 "2025-04-01T15:32:18Z")

</div>

> [@IgorSim](#):
>
> Just for clarification, restore never worked (i've tried restoring several different snapshots, even the first one), also i removed the NFS mounts and recreated them all over again, that didn't help either. I was aware that restoration doesn't work but this issue wasn't top priority back then and i didn't investigate in more details. Now, it's back on the table and it's time to find resolution 🙂

Ok, this is an Elastic forum, so we concentrate on elements relating to Elastic products/code/usage/etc. And your issue certainly lies in the interesting puzzle category, I’m curious what resolves the mystery.

BUT, if you are making un-restorable snapshots, and you have no other way to recover, IMO you need fix that first. Somehow. Be that using S3, or other cloud service, or use a different NFS appliance, or whatever, NOT having tested restorable backups of some sort is … suboptimal.

---

<div class="post-metadata">

**Author:** ![IgorSim](https://avatars.discourse-cdn.com/v4/letter/i/3d9bf3/32.png) [@IgorSim](https://discuss.elastic.co/u/IgorSim)\
**Post date:** [April 1, 2025, 5:05pm UTC](https://discuss.elastic.co/t/restore-snapshot-checksum-problem-troubleshooting-corruption/369764/24 "2025-04-01T17:05:55Z")

</div>

Couldn't agree more, tnx for your input though.

I'll keep you posted if there is new information.

[Previous page](https://discuss.elastic.co/t/restore-snapshot-checksum-problem-troubleshooting-corruption/369764.md?page=1)