Error: Failed to Power on the VM " The Redo Log of 'examplevm-000001.vmdk' is Corrupted. If the problem persists, discard the redo log"

Products

• VMware vSphere ESXi

Issue/Introduction

• When taking a snapshot of a VM placed on a QNAP datastore the error message "The redo log of <VM Name> is corrupted" appears and consolidation doesn't work.
• The same VM works perfectly fine after migrating the VM to another datastore.
• The VMFS datastore on which the VM is hosted is NOT a replica of a different VMFS datastore.
• The VM is NOT restored from a storage based snapshot of a VMFS datastore or of an NFS share, before powering on.
• No corruption found on this datastore or any other issues.
• ESXi - /var/log/vmkernel.log

YYYY-MM-DDTHH:MM:SS cpu##:######)SESparse: ####: Corrupt GTE GTE [valid: # gCluster: ################# gResource: #### unused: #] ;

• VM's vmware.log after the snapshot creation:

YYYY-MM-DDTHH:MM:SS In(05) vmx - VigorTransport_ServerSendResponse opID=########-######-####-####-##:########-##-##-#### seq=#### : Completed Snapshot request.

YYYY-MM-DDTHH:MM:SS In(05) vmx - GuestInfo: HostinfoDetailedDataHeader version: #

YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting guestInfo.detailed.data = <not printed>

YYYY-MM-DDTHH:MM:SS In(05) vmx - VigorTransportProcessClientPayload: opID=########-######-####-####-##:########-##-##-#### seq=####: Receiving GuestStats.SetNotificationTime request.

YYYY-MM-DDTHH:MM:SSIn(05) vmx ########-######-####-####-##:########-##-##-##-##-#### VigorTransport_ServerSendResponse opID=########-######-####-####-##:########-##-##-#### seq=####: Completed GuestStats request.

YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - Msg_Question:

YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - [msg.hbacommon.corruptredo] The redo log of 'VM_NAME-000001.vmdk' is corrupted. If the problem persists, discard the redo log.

YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - ----------------------------------------

YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - VigorTransportProcessClientPayload: opID=########-##-#### seq=####: Receiving Bootstrap.MessageReply request.

YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 ########-##-#### VigorTransport_ServerSendResponse opID=########-##-#### seq=####: Completed Bootstrap request.

YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - MsgQuestion: msg.hbacommon.corruptredo reply=0

YYYY-MM-DDTHH:MM:SS Cr(01) vcpu-0 - PANIC: Exiting because of failed disk operation.

YYYY-MM-DDTHH:MM:SS Wa(03) vcpu-0 - A core file is available in "/vmfs/volumes/########-########-####-##########/VM_Name/vmx-zdump.000"

YYYY-MM-DDTHH:MM:SS Wa(03) mks - Panic in progress... ungrabbing

YYYY-MM-DDTHH:MM:SS In(05) mks - MKS: Release starting (Panic)

YYYY-MM-DDTHH:MM:SS In(05) mks - MKS: Release finished (Panic)

Environment

VMware vSphere ESXi 7.0

Resolution

To resolve this issue, install the following firmware on the QNAP - h5.1.0.2453 Build 20230708 RC2.

Additional Information

Corrupt redo log causes errors within the virtual machine while powering on ESXi

REDO log corruption is reported after restoring the virtual machine