Currently I am facing to an annoying trouble which a VMDK file is corrupted. This troublem was occured because of the shortage of the storage and my ESX 3.5 tells "msg.hbacommon.outofspace: Retry? or Abourt?" message. I chose "Abourt" and then the guest OS has never turned on since the VMDK is corrupted.
I have been looking for command or 3rd party tools to fix VMDK, but unfortunatelly could not find such a magical tool.
Are there any one who had the same problem and some solution to fix VMDK file?
Thank you very much in advance.
VMware ESX 3.5.0 / Build 110268
GuestOS: Windows NT 4.0
The VMDK itself may not be corrupt, but the Guest OS filesystem within the VMDK could be corrupt. So you will want to run a tool to verify and check the filesystem within the VMDK first. Most likely run from a LiveCD of sometype.
Edward L. Haletky
VMware Communities User Moderator
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Thanks for the reply Texiwill.
I have tried LiveCD, but ESX keeps showing the following message.
Virtual Machine Message msg.hbacommon.corruptredo: The RedoLog of Production_3-000006.vmdk has been detected to be corrupt. The virtual machine needs to be powered on. If the problem sill persists, you need to discard the redolog.
This message appears while the gust os is booting up, and so even the LiveCD cannot be started.
The error message tells "discard the redolog". I guess the gues OS will lose data (or snapshot data), if I delete the vmdk file.
Are there anyone who faced on the same problem, and fix the problem?
Thanks in advance.
It seems like one of your snapshots is corrupt. How many do you have currently running? How much free space is their on the VMFS they are running? Can you do an "ls -lah" in the VM folder and post it here? Please also do a "vdf -h" and post it here.
If you find this information useful, please award points for "correct" or "helpful".
Thanks for the reply depping.
I'm gonna attach the result of "ls -lah" and "vdf -h".
This vmware files are stroed in ATA1-8MB. As one can see, ATA1-8MB has enough space now, but when the file was corrupted it had only few kbytes. After the trouble I moved other VM files to the other data storage.
I have copied the VMdisk from ESX 3.5.0 to VMWare Workstation, and found the following errors.
Oct 19 21:33:30.718: vmx| DISKLIB-SPARSE: "E:\Copy of 3P\3Production_3-000006-delta.vmdk" : failed to open (14): Disk needs repair.
Oct 19 21:33:30.750: vmx| DISKLIB-LINK : "E:\Copy of 3P\3Production_3-000006.vmdk" : failed to open (The specified virtual disk needs repair).
Oct 19 21:33:30.750: vmx| DISKLIB-CHAIN : "E:\Copy of 3P\3Production_3-000006.vmdk" : failed to open (The specified virtual disk needs repair).
Oct 19 21:33:30.750: vmx| DISKLIB-LIB : Failed to open 'E:\Copy of 3P\3Production_3-000006.vmdk' with flags 0xa (The specified virtual disk needs repair).
I have been looking for the way to fix VMdisk, but there are no tools or commands to fix VMdisks.
There is a tool to mount VMdisks even if the VMdisk has few corruptions. http://chitchat.at.infoseek.co.jp/vmware/vdk.html#top
But unfortunatelly, this tool supports only upto version 4.x, and my VMDisk is version 5.x...