When the VM recovers from a failure, the recovery might need manual disk repair
SSPI 5.0
Unexpected VM failure could have left the disk in corrupted state. This occasionally requires manual recovery via tools like fsck
In the event of filesystem corruption after a vm recovers.
(1) Run fsck repair on the filesystem via SSH to the SSPI VM via root creds :
fsck -A -y
(2) Restart all the failed pods in your k8s environment