Hello Mohmaly,
This appears to be an issue with the snapshot that is present on the VM. Redo log corruptions indicate corruptions on the snapshot and we will have no other option but to revert back to the previous snapshot if any.
Redo log corruptions may occur due to ( but not limited to) :
-- This issue might occur by various circumstances that include but are not limited to:
-- Hardware issues with the storage controller or storage device.
-- Connectivity issues between the ESX host and the storage device.
-- When the datastore containing the snapshot disks runs out of free disk space.
You could try performing a snapshot consolidation or clone operation, but do this make sure you terminate the VM, by clicking cancel in the task entry.
Clone from the command line can be performed using the below steps : VMware Knowledge Base
VMware Knowledge Base
If the clone does not work, then we may have to restore the VM from backup.
The clear understanding of why this may occur is scarce however,
The delta disk metadata in-memory of vSphere host includes the delta disk header. Updates to the header of the delta disks happen in memory as required and the changes are written to disk only upon certain events such as snapshot consolidation or when the delta disk is closed. The corruption of these delta disks due to the reasons mentioned above can cause this redo log corruption issues.
How can we prevent this ?
Tbh, there is no hard and fast rule, but if we are having this issue very often then we may want to check if there are any backend storage disconnections or storage array tasks, backup events occuring. That is eher analysisng logs would be required to get to the root of this.
Mike.