troubleshooting Question

corrupt redo log. VMware ESXi

Avatar of Andrew Davis
Andrew DavisFlag for Australia asked on
Server SoftwareVMwareVirtualization
31 Comments1 Solution11391 ViewsLast Modified:
Host: VMware ESXi, 5.0.0, 469512
Client shows error while booting up:
The redo log of {Servername}-000002.vmdk is corrupted. Power off the virtual machine, if the problem still persists, discard the redo log.

Just about every article i have found regarding this says to consolidate the snapshots, so i deleted the snapshots (vSphere Client - Snapshot manager), which then told me that it wanted to consolidate the drives. When i tell it to consolidate i get
Consolidate virtual machine disk files
A general system error occurred: Input/output error

Following i susspect there may b e locked files. The server reports that it is powered Off, but did come up with an error during the Power Off task.

 The article above leads me to
if i look at the  vmware.log file i am not seeing anything unexpected at the end of the file.
however if i try to use vmkfstools i get the following

login as: itsupport
Using keyboard-interactive authentication.
The time and date of this login have been sent to the system logs.

VMware offers supported, powerful system administration tools.  Please
see for details.

The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
~ $ su
~ # vmkfstools
sh: vmkfstools: not found
~ #

So not really sure where to go from here ;)

Additional notes:
If this helps at all (Vmid 2 is the one in question)

~ # vim-cmd vmsvc/getallvms
Vmid      Name                     File                        Guest OS          Version   Annotation
1      SBS2011      [datastore1] SBS2011/SBS2011.vmx     windows7Server64Guest   vmx-08
2      2008Leap     [datastore2] 2008Leap/2008Leap.vmx   windows7Server64Guest   vmx-08
3      2008Leap-2   [NAS01] 2008Leap-2/2008Leap-2.vmx    windows7Server64Guest   vmx-08
~ # vim-cmd vmsvc/power.getstate 2
Retrieved runtime info
Powered off
~ #
There is only the one host, so no other host could possibly have a lock.
Have rebooted the host:- no change.

Join our community to see this answer!
Unlock 1 Answer and 31 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 31 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros