Description of problem (please be detailed as possible and provide log
snippests):

I'm looking for assistance on noobaa-db corruption and if we can do anything to preserve some data (or is this a full rebuild?)... Noobaa-db logs are reporting:

ERROR error: index "idx_btree_objectparts_chunk" contains unexpected zero page at block 525520

Which indicated the index idx_btree_objectparts_chunk is corrupt. We tried to reindex the index (REINDEX index idx_btree_objectparts_chunk) but this didn't help. We also noticed some of the transactions never completed fully:

ERROR: could not access status of transaction 577634449
DETAIL: Could not read from file "pg_xact/0026" at offset 229376: read too few bytes

This all occurred after the customer ran an fsck. I don't have the results of this run as this was done by following the KCS [1] on their own. I'm assuming, the fsck on the noobaa-db pvc 'fixed' things it was not supposed to be fixing.

[1] https://access.redhat.com/solutions/6998986

Version of all relevant components (if applicable):
4.13

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, noobaa-db is critical to run anything with mcg

Is there any workaround available to the best of your knowledge?
Rebuild the DB