Description of problem (please be detailed as possible and provide log
snippests):
Noobaa-db is in Pending state. Found fsck error for the rbd device:
Internal desc = 'fsck' found errors on device /dev/rbd0 but could not correct them: fsck from util-linux 2.32.1
Version of all relevant components (if applicable):
OCS 4.8
Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, unable to use MCG
Is there any workaround available to the best of your knowledge?
Run fsck to repair fs
Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2
Can this issue reproducible?
in customer's environment
Can this issue reproduce from the UI?
No
If this is a regression, please provide more details to justify this:
No
Actual results:
noobaa-db pvc fails to mount
Expected results:
Noobaa-db pod should be in running state
Additional info:
In next private comment
Comment 15Scott Ostapovicz
2022-02-03 14:16:29 UTC
Ilya, I guess the outstanding question is how do they repair the volume that has been corrupted.