Get segment range: segments are not sequential

Hi Team ,

In our Cloud Production environment, we are frequently getting following logs

-05-25T22:27:38.121Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1670905814378 maxt=1672617600000 ulid=01GNRDM1ERBHWW1SA85FX24Y89

level=info ts=2023-05-25T22:27:38.121Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1672617614381 maxt=1674367200000 ulid=01GQCJ4YXZG757CESD5WJ7RDQZ

level=info ts=2023-05-25T22:27:38.121Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1674367200000 maxt=1676116800000 ulid=01GS0FTSS8B3FWESEYZJF98ER8

level=info ts=2023-05-25T22:27:38.121Z caller=tls_config.go:191 component=web msg=“TLS is disabled.” http2=false

level=info ts=2023-05-25T22:27:38.121Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1676116800000 maxt=1677866400000 ulid=01GTMMEX0D48QC04QEKS2A92XJ

level=info ts=2023-05-25T22:27:38.122Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1677866400000 maxt=1678060800000 ulid=01GTTDVGDKHJNAQ2RMCDXVQ1EK

level=info ts=2023-05-25T22:27:38.122Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1678060800000 maxt=1678255200000 ulid=01GV07848ATWYAPWG0VRP27CDS

level=info ts=2023-05-25T22:27:38.122Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1678276801000 maxt=1678284000000 ulid=01GV0VSD6ZHRBAWGA513RACFAK

level=info ts=2023-05-25T22:27:38.122Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1678284000000 maxt=1678291200000 ulid=01GV12N4EZZ8BPSMEN22RPWDPT

level=info ts=2023-05-25T22:27:38.122Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1678255201000 maxt=1678276800000 ulid=01GV12Q12K5H2K9DX9JH8H4KX6

level=info ts=2023-05-25T22:27:38.122Z caller=repair.go:57 component=tsdb msg=“Found healthy block” mint=1678291200000 maxt=1678298400000 ulid=01GV19GVQ09TPB6P5G1SZHA55H

level=info ts=2023-05-25T22:27:38.122Z caller=main.go:668 msg=“Stopping scrape discovery manager…”

level=info ts=2023-05-25T22:27:38.122Z caller=main.go:682 msg=“Stopping notify discovery manager…”

level=info ts=2023-05-25T22:27:38.122Z caller=main.go:704 msg=“Stopping scrape manager…”

level=info ts=2023-05-25T22:27:38.122Z caller=main.go:678 msg=“Notify discovery manager stopped”

level=info ts=2023-05-25T22:27:38.122Z caller=main.go:664 msg=“Scrape discovery manager stopped”

level=info ts=2023-05-25T22:27:38.122Z caller=main.go:698 msg=“Scrape manager stopped”

level=info ts=2023-05-25T22:27:38.122Z caller=manager.go:934 component=“rule manager” msg=“Stopping rule manager…”

level=info ts=2023-05-25T22:27:38.122Z caller=manager.go:944 component=“rule manager” msg=“Rule manager stopped”

level=info ts=2023-05-25T22:27:38.122Z caller=notifier.go:601 component=notifier msg=“Stopping notification manager…”

level=info ts=2023-05-25T22:27:38.122Z caller=main.go:872 msg=“Notifier manager stopped”

level=error ts=2023-05-25T22:27:38.122Z caller=main.go:881 err=“opening storage failed: get segment range: segments are not sequential”

Due to this prometheus is not starting.

What could be possible reasons for the same and is there any way to recover the lost data .