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

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

book

Article ID: 313052

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • When the virtual machine in ESXi is powered on, you see the error:

    msg.hbacommon.corruptredo:The redolog of server1-000001.vmdk has been detected to be corrupt. The virtual machine needs to be powered off. If the problem still persists, you need to discard the redolog.

    msg.hbacommon.corruptredo:The redo log of Server2-000001.vmdk is corrupted. If the problem persists, discard the redo log

    Note: This prompt is an endless loop. The error will display repeatedly if you click OK.
  • Powering off the virtual machine, you see an error:

    The attempted operation cannot be performed in the current state


Environment

VMware vSphere ESXi 6.5
VMware vSphere ESXi 8.0
VMware vSphere ESXi 7.0

Cause

File corruption is random in nature.
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.

Resolution

To resolve this issue, use one of the options based on the symptom you are experiencing:
  • Create enough free space on the datastore where the snapshot disks are located:
     
    1. Extend the particular VMFS datastore.
    2. Migrate other virtual machines' files out of this datastore.
       
  • Commit the virtual machine snapshots:
    1. Verify that you have enough free space before proceeding.
    2. If the snapshot configuration files are corrupt and do not display in Snapshot Manager, consolidate the snapshot disks manually by taking a consolidator snapshot or cloning the snapshot disks. For more information, see Committing snapshots when there are no snapshot entries in the snapshot manager (1002310).
      • If the clone operation fails with a device or resource busy error message, the virtual machine is not powered off completely. You might see the error:

        msg.hbacommon.corruptredo
      • Click OK to power off the virtual machine and continue.
      • If the virtual machine is unable to proceed past this error, the virtual machine world must be terminated manually.
        Note: Manually terminating the virtual machine world terminates the virtual machine's processes. For more information, see Powering off an unresponsive virtual machine on an ESX host (1004340). Go to step 2 or power on the virtual machine according to the current status.
 
Note: If you are unable to consolidate the snapshots, you may need to restore the virtual machine from backup. Otherwise, you may file a technical support request with VMware Technical Support. For more information, see Filing a Support Request in Customer Connect (2006985).


Additional Information

 

Committing snapshots when there are no snapshot entries in the Snapshot Manager
Powering off an unresponsive virtual machine on an ESX host
Troubleshooting an out of storage space condition in VMware vCenter Lab Manager
How to file a Support Request in Customer Connect
パワーオン中の仮想マシン内での破損した REDO ログによるエラー
打开 ESXi 的电源时损坏重做日志导致虚拟机中出现错误

Powered by Wolken Software