Hi Team

We are running a single node EVMOS chain on AWS. We are currently on 26 million+ blocks and the chain has been running for around 10 months. Recently, our server running the chain went out of storage after which, the storage on the server was expanded. Post storage expansion, we downloaded the evmosd client and binaries from our backup servers and used evmosd start command to start the chain again. After running the start command we now see the client trying to access unavailable files such as attached screenshot.

The approximate size of backup is similar to the binary file size generated during block minting before the chain halted.

Could you please help us by suggesting a method that can be used to recover the missing files or start the chain from a rolled back state where the last state finality can be determined from the available .ldb files.

This is a very high priority issue for us, therefore we request a quick response from the team.